tcl-mac — Q&A for Tcl on the Macintosh platform

Re: [MACTCL] latest build

[Jim I. <ji...@ap...>]

Done, I made a new "release" in the SourceForge parlance.  I called it 
(for lack of a better name) 8.4a4-2...  Anyway, it is what shows up in 
the file releases page on the Tcl SourceForge page.

Jim


On Friday, February 1, 2002, at 03:46  AM, Mads Linden wrote:

> does anyone of you with "compiling knowledges" feel like updating the
> snabshot on sourceforge
> with a more recent build of the osx branch.
>
> it's a bit hard to take joy in mactcl since all of you have c++/c
> backgrounds, but remember many
> tcl programmers only know tcl!
>
> Thanks
>
> Mads
>
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] latest build

[Mads L. <ma...@el...>]

does anyone of you with "compiling knowledges" feel like updating the
snabshot on sourceforge
with a more recent build of the osx branch.

it's a bit hard to take joy in mactcl since all of you have c++/c
backgrounds, but remember many
tcl programmers only know tcl!

Thanks

Mads

Re: [MACTCL] Ponderings of an open source developer...

[James B. <jk...@mr...>]

On Thu, Jan 31, 2002 at 09:29:46AM -0800, Jim Ingham wrote:
> When gcc3 is all the way done for MacOS X the default compiler will 
> include g77.  For now, you can check out gcc3 from the Darwin sources 
> and build it (I don't know if it is built in Fink or not).  There have 

Thanks for the hints. However I took a rather simplistic route and just
compiled f2c from netlib. We're moving away from Fortran and so only have the
one "legacy.f" fortran file left, which f2c can cope with amiably. The libI77
and libF77 libraries I merged into one and tweaked a bit. To build them as a
dynamic library it seems that you need to change many of the global variables
to be definitions rather than just declarations.

Eg: "int l_eof;" becomes "int l_eof = 0;". (This is only needed for the global
variables. And only when building with -dynamiclib.)

I've also got itcl and itk to compile, so I'll be posting instructions to the
tcl newsgroup (I saw a query about this there). At present I haven't fixed the 
configure script though; my changes were out and out hackery :-)

James

-- 
James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/

Re: [MACTCL] Ponderings of an open source developer...

[Lizardo H. C. M. N. <li...@ur...>]

On Thursday, January 31, 2002, at 03:29  PM, Jim Ingham wrote:

There have been a number of notes from the Darwin list telling of 
success in getting Fortran code to compile with g77.  This is not going 
to be the super-optimizing Fortran compiler that you are used to from, 
say, the SGI or VAX environments...  For that, you will probably have to 
wait for the AbSoft compiler.  But it gets the job done.
-----

I built g77( version 0.5.25 ) with Fink. The  output  of my own code 
matches with that of an Athlon 700 MHZ running Linux (I can't say what 
is the g77 version) ---Funny is that the Athlon  seems to have a similar 
performance when compared to my Cube 450 Mhz, but I can't garantee. I 
don't see the relevance of testing it since I couldn't get great 
discrepancies... )

Alternatively, for g77 check :
http://dryden.biol.yorku.ca/g77
or post a message on dar...@op... and you'll get 
pointers.

People say that Absoft Fortran is twice as fast as Fink's g77, but if 
you have a G4 you can also look at
http://www.psrv.com.
for instant vectorization of loops.

That's it
Lizardo H. C. M. Nunes

...But we preach Christ crucified, to the Jews a stumbling block, and to 
the
Greeks foolishness;(...)but God has chosen the foolish things of the 
world
to confound the wise, and God has chosen the weak things of the world to
confound the things which are strong;(I Cor.1:23&27)

P.S.:

On Thursday, January 31, 2002, at 03:29  PM, Jim Ingham wrote:
> James,
>
> I am glad this is going well!
>
>
>> If you have more demanding X uses when the XonX project can provide a 
>> full
>> Xfree86 (currently v4.2) for MacOS X for free. Also the Fink and 
>> Gnu-Darwin
>> projects (also free) can provide the rest of the GNU experience 
>> (although at
>> present I haven't needed any of this as the standard development 
>> environment
>> seems to contain all I need except for Fortran, but I think f2c will 
>> solve
>> that).
>>

You if are connected to a Linux LAN you can use  XDarwin and " ssh -X " 
to work on any application remotely too.

Re: [MACTCL] Ponderings of an open source developer...

[George S. <gbj...@at...>]

Thanks Jim, for reminding me that I had ordered and received the
$20 developers tools on CD-ROM from December 2001 but forgot to
install them and had forgot where I put the CD-ROM.  Well, to make
a long story short, I found the CD-ROM, installed them on my
PowerBook Pismo, and was astounded by the impressively huge
array of development tools sitting on my little laptop!!!  All the stuff
in the Developers folder was amazing - I'm going to have to get a
book on developing on MacOS X and dive in - it looks like a lot of fun!

As an illustration, here is good ol' gcc (called cc on MacOS X, like
the good ol' days of UNIX) as shown in a Terminal window:

[localhost:~] gbs% uname -a
Darwin localhost 5.2 Darwin Kernel Version 5.2: Fri Dec  7 21:39:35 PST 
2001; root:xnu/xnu-201.14.obj~1/RELEASE_PPC  Power Macintosh powerpc
[localhost:~] gbs% cc -v
Reading specs from /usr/libexec/gcc/darwin/ppc/2.95.2/specs
Apple Computer, Inc. version gcc-934.3, based on gcc version 2.95.2 
19991024 (release)
[localhost:~] gbs%


gbs

On Wednesday, January 30, 2002, at 10:48 AM, Jim Ingham wrote:

> Larry,
>
> The boxed version of MacOS X has always included the full developer 
> tools suite: gcc, gdb, etc, as well as Tcl (8.3.2 currently) but no Tk 
> yet, and Perl, emacs, vi, and lots of other goodies...  It also comes 
> with a GUI Development Environment Suite (Project Builder/Interface 
> Builder) which are pretty nice, if not as mature as something like VC++ 
> or CodeWarrior.  That's what I used for the Tcl & Tk projects.
>
> The lowest level of the Apple Developer Connection subscription (~$100) 
> will get you quarterly updates to the developer CD, plus lots of other 
> sample code, and SDK type goodies.  Most of these are available for 
> download as well, but the CD's are convenient...
>
> For a while, the machines that were shipping with X on them didn't 
> include the Developer Tools CD in the box (supposedly 'cause it would 
> scare consumer Mac customers), so you would have to send $20 to Apple 
> to get them to ship you the CD, or download the whole CD from Apple's 
> web site (somewhat of a trial unless you have a fast connection).  But 
> the newest G4's have a disk image of the Developer Tools on the hard 
> drive, and also on the restore CD.  I don't know whether this is true 
> of the new iMac's as well.
>
> Have fun...
>
> Jim
>
>
> On Wednesday, January 30, 2002, at 10:24  AM, Larry W. Virden wrote:
>
>> Okay, if I were to be so foolish as to break terribly the family 
>> budget and
>> buy a mac that runs mac os x, putting me into the dog house for the 
>> next
>> 10 or more years, am i even going to be able to do any software 
>> development
>> on the thing?  Or am I still faced with the fact that, as far as I can 
>> tell,
>> one has to sink a large amount of cash into buying a c compiler?
>>
>> I really don't care to rewrite all tcl extensions into java...
>> --
>> Never apply a Star Trek solution to a Babylon 5 problem.
>> Larry W. Virden <mailto:lv...@ca...> <URL: 
>> http://www.purl.org/NET/lvirden/>
>> Even if explicitly stated to the contrary, nothing in this posting 
>> should
>> be construed as representing my employer's opinions.
>> -><-
>>
>> _______________________________________________
>> Tcl-mac mailing list
>> Tc...@li...
>> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>>
> --
> Jim Ingham                                   ji...@ap...
> Developer Tools - gdb
> Apple Computer
>
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>

Re: [MACTCL] Ponderings of an open source developer...

[Jim I. <ji...@ap...>]

James,

I am glad this is going well!


> If you have more demanding X uses when the XonX project can provide a 
> full
> Xfree86 (currently v4.2) for MacOS X for free. Also the Fink and 
> Gnu-Darwin
> projects (also free) can provide the rest of the GNU experience 
> (although at
> present I haven't needed any of this as the standard development 
> environment
> seems to contain all I need except for Fortran, but I think f2c will 
> solve
> that).
>

Yes, we got pretty much all the standard TclPro Tcl suite, BLT, TkTable, 
etc, built and running with XonX with very little trouble.  The X Server 
seems pretty fast, too, though the Motif look of Tk is pretty odd next 
to the Aqua desktop...

When gcc3 is all the way done for MacOS X the default compiler will 
include g77.  For now, you can check out gcc3 from the Darwin sources 
and build it (I don't know if it is built in Fink or not).  There have 
been a number of notes from the Darwin list telling of success in 
getting Fortran code to compile with g77.  This is not going to be the 
super-optimizing Fortran compiler that you are used to from, say, the 
SGI or VAX environments...  For that, you will probably have to wait for 
the AbSoft compiler.  But it gets the job done.

Jim
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

Re: [MACTCL] Ponderings of an open source developer...

[James B. <jk...@mr...>]

On Wed, Jan 30, 2002 at 01:24:49PM -0500, Larry W. Virden wrote:
> Okay, if I were to be so foolish as to break terribly the family budget and
> buy a mac that runs mac os x, putting me into the dog house for the next
> 10 or more years, am i even going to be able to do any software development
> on the thing?  Or am I still faced with the fact that, as far as I can tell,
> one has to sink a large amount of cash into buying a c compiler?

In addition to the previous comments, I can add testimont to the fact that
MacOS X really is just like Unix underneath.

We received our Mac on Tuesday lunchtime. I'd never really used a Mac at all,
except once or twice (and hated every minute). Since Tuesday though I've
already got one of our tools ported to the Mac. Indeed part of it, which used
GNU autoconf, worked with nothing more than "./configure; make". Just like
Unix :-)

A Tk widget we wrote forms part of a DNA sequencing chromatogram viewer
(http://www.mrc-lmb.cam.ac.uk/pubseq/manual/trev_unix_1.html) which requires
rapid scrolling and scaling. For this we use some basic X11 functions, but
thanks to the xlib code in Tk and Jim's work on the native Mac port the new
widget works nearly 100% correctly.

If you have more demanding X uses when the XonX project can provide a full
Xfree86 (currently v4.2) for MacOS X for free. Also the Fink and Gnu-Darwin
projects (also free) can provide the rest of the GNU experience (although at
present I haven't needed any of this as the standard development environment
seems to contain all I need except for Fortran, but I think f2c will solve
that).

I'm not trying to convert you from Linux on a PC to Mac - with 2 days
experience I wouldn't want to - but I am really quite astonished as to how
easy my porting work is going!

James

-- 
James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/

RE: [MACTCL] Ponderings of an open source developer...

[Schollnick, B. <Ben...@us...>]

Mac OS X comes with the full developer's software....

Which includes a C, C++, ObjectiveC compiler....

And all of the tools necessary.... 

		- Benjamin

-----Original Message-----
From: Larry W. Virden [mailto:lv...@ca...]
Sent: Wednesday, January 30, 2002 1:25 PM
To: tc...@li...
Subject: [MACTCL] Ponderings of an open source developer...


Okay, if I were to be so foolish as to break terribly the family budget and
buy a mac that runs mac os x, putting me into the dog house for the next
10 or more years, am i even going to be able to do any software development
on the thing?  Or am I still faced with the fact that, as far as I can tell,
one has to sink a large amount of cash into buying a c compiler?

I really don't care to rewrite all tcl extensions into java...
-- 
Never apply a Star Trek solution to a Babylon 5 problem.
Larry W. Virden <mailto:lv...@ca...> <URL:
http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

_______________________________________________
Tcl-mac mailing list
Tc...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

Re: [MACTCL] Ponderings of an open source developer...

[Jim I. <ji...@ap...>]

Larry,

The boxed version of MacOS X has always included the full developer 
tools suite: gcc, gdb, etc, as well as Tcl (8.3.2 currently) but no Tk 
yet, and Perl, emacs, vi, and lots of other goodies...  It also comes 
with a GUI Development Environment Suite (Project Builder/Interface 
Builder) which are pretty nice, if not as mature as something like VC++ 
or CodeWarrior.  That's what I used for the Tcl & Tk projects.

The lowest level of the Apple Developer Connection subscription (~$100) 
will get you quarterly updates to the developer CD, plus lots of other 
sample code, and SDK type goodies.  Most of these are available for 
download as well, but the CD's are convenient...

For a while, the machines that were shipping with X on them didn't 
include the Developer Tools CD in the box (supposedly 'cause it would 
scare consumer Mac customers), so you would have to send $20 to Apple to 
get them to ship you the CD, or download the whole CD from Apple's web 
site (somewhat of a trial unless you have a fast connection).  But the 
newest G4's have a disk image of the Developer Tools on the hard drive, 
and also on the restore CD.  I don't know whether this is true of the 
new iMac's as well.

Have fun...

Jim


On Wednesday, January 30, 2002, at 10:24  AM, Larry W. Virden wrote:

> Okay, if I were to be so foolish as to break terribly the family budget 
> and
> buy a mac that runs mac os x, putting me into the dog house for the next
> 10 or more years, am i even going to be able to do any software 
> development
> on the thing?  Or am I still faced with the fact that, as far as I can 
> tell,
> one has to sink a large amount of cash into buying a c compiler?
>
> I really don't care to rewrite all tcl extensions into java...
> --
> Never apply a Star Trek solution to a Babylon 5 problem.
> Larry W. Virden <mailto:lv...@ca...> <URL: 
> http://www.purl.org/NET/lvirden/>
> Even if explicitly stated to the contrary, nothing in this posting 
> should
> be construed as representing my employer's opinions.
> -><-
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] Ponderings of an open source developer...

[Larry W. V. <lv...@ca...>]

Okay, if I were to be so foolish as to break terribly the family budget and
buy a mac that runs mac os x, putting me into the dog house for the next
10 or more years, am i even going to be able to do any software development
on the thing?  Or am I still faced with the fact that, as far as I can tell,
one has to sink a large amount of cash into buying a c compiler?

I really don't care to rewrite all tcl extensions into java...
-- 
Never apply a Star Trek solution to a Babylon 5 problem.
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

Re: [MACTCL] "load" on Darwin wish

[Jim I. <ji...@ap...>]

James,

This is a bug.  It turns out that dyld will abort your program if you 
try to lookup a symbol, and it doesn't exist.  This seems a little 
draconian to me, but...  Fortunately, there is a way to register a 
"symbol not found" handler with dyld, and if you do, it will call that 
instead of aborting.  Somebody sent me a patch for the "library not 
found" version of this a little while ago.  I need to take a look at it 
and check it in.

In the meantime, you will have to add the SafeInit.  You really should 
have one anyway.  Either your extension is NOT safe to load into a safe 
interpreter, in which case to be a good citizen you need one that 
returns TCL_ERROR.  If it is safe, then the safe init can just call the 
unsafe one.

Jim

On Wednesday, January 30, 2002, at 04:07  AM, James Bonfield wrote:

> Hello,
>
> I've built a C Tk extension and I'm trying to load it into the native 
> darwin
> wish. My library is tk_utils held in a file named libtk_utils.dylib. It 
> has a
> Tk_utils_Init() function. However the load command seems to be looking 
> for the
> safe-init function instead:
>
> % load libtk_utils.dylib
> dyld: /Applications/Wish Shell.app/Contents/MacOS/Wish Shell Undefined
> symbols: _Tk_utils_SafeInit
> [mac5031-1:src/lib/mac-binaries] jkb%
>
> Why is this? I know that this function doesn't exist - I don't want it
> to. However on Unix and Windows it simply ignores this. Indeed we even 
> load
> libraries that have neither a _SafeInit or an _Init function simply to 
> load in
> some additional C-only libraries.
>
> Any suggestions most welcome. (In the mean time I'll create a SafeInit
> function to keep it happy...)
>
> Cheers,
>
> James
>
> --
> James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
> Medical Research Council - Laboratory of Molecular Biology,
> Hills Road, Cambridge, CB2 2QH, England.
> Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] "load" on Darwin wish

[James B. <jk...@mr...>]

Hello,

I've built a C Tk extension and I'm trying to load it into the native darwin
wish. My library is tk_utils held in a file named libtk_utils.dylib. It has a
Tk_utils_Init() function. However the load command seems to be looking for the 
safe-init function instead:

% load libtk_utils.dylib
dyld: /Applications/Wish Shell.app/Contents/MacOS/Wish Shell Undefined
symbols: _Tk_utils_SafeInit
[mac5031-1:src/lib/mac-binaries] jkb% 

Why is this? I know that this function doesn't exist - I don't want it
to. However on Unix and Windows it simply ignores this. Indeed we even load
libraries that have neither a _SafeInit or an _Init function simply to load in 
some additional C-only libraries.

Any suggestions most welcome. (In the mean time I'll create a SafeInit
function to keep it happy...)

Cheers,

James

-- 
James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/

Re: [MACTCL] Re: MacTcl community willing to provide support for their own?

[Larry W. V. <lv...@ca...>]

Sounds like your site hasn't picked up the DNS info from Sunday nite.
There's been dozens of people access mini.net in the past 2 days or more.

I've been asking to see if I can find a current copy of the MacTcl FAQ.
the copy I have is pretty old.

Here's a URL of a cached copy of the FAQ - don't know how it
corresponds to the current one:

<URL: http://www.google.com/search?q=cache:lT846hQwzhAC:www.etsimo.uniovi.es/tcl/faq/macFAQ.html+mactcl+faq&hl=en&start=18 >
-- 
Never apply a Star Trek solution to a Babylon 5 problem.
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

[MACTCL] Re: MacTcl community willing to provide support for their own?

[<Ge...@Or...>]

LWV forged a FL prescription with:
#
#    I was wondering whether the various members of this mailing list
#    would be interested in making use of
#
#        <URL: http://purl.org/tcl/wiki/>
#
#    to add pages providing support for various MacTcl related issues.
#     I notice that most of the online web pages to date have grown
#    stale - links out of date, etc. 

That URL isn't working, I've tried over the last 15 minutes. 

Mini.net isn't resolving. 

Not that I can help much, I'm a Mac Adobe user, just starting
to use Tcl/Tk on it (developing under Solaris for a Mac client). 

If anyone knows of a working URL for the MacTcl FAQ, please post. 

Tanks Advance.

[MACTCL] MacTcl community willing to provide support for their own?

[Larry W. V. <lv...@ca...>]

I was wondering whether the various members of this mailing list would
be interested in making use of <URL: http://purl.org/tcl/wiki/> to
add pages providing support for various MacTcl related issues.  I notice
that most of the online web pages to date have grown stale - links
out of date, etc.

If there is interest, note that you can feel free to surf the above
web site and just add info about mactcl at your leisure.
-- 
Never apply a Star Trek solution to a Babylon 5 problem.
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

[MACTCL] Re: Img port

[Mats B. <ma...@pr...>]

Jack Jansen wrote:
> 
> On Wednesday, January 23, 2002, at 06:20  PM, Mats Bengtsson wrote:
> 
> >
> > Update,
> >
> > Got CW 6 tiff project from Jack, used the archive from his site (3.3?)
> > added #include <fcntl.h> in tiffcomp.h, made it into a shared lib,
> > replaced tiff.shlb, but only blue and black shows correctly.
> > The first one (3.5.7), shows red and white correctly, very funny...
> > This beats me, anyone...
> 
> Note that the I/O component of libtiff is pretty finicky. As the
> library was distributed (I got it about 8 years ago, I think) it
> used raw MacOS File Manager calls. The library as it is in my
> distribution (if I remember correctly) uses the Unix I/O file
> for libtiff and then uses either GUSI for unix-style
> open/close/read/write I/O or whatever MSL gives you. But for
> Python I did a workaround at some point to use stdio for I/O,
> because there were some problems with the other two I/O methods.
> 

In 3.5.7 that I use, and in your version, IO is handled in tif_apple.c,
but in 3.5.7 its Carbonized, and there are some API changes, but its
hard to believ that this has anything to do with it (?).

> So to make a long story short: the first thing I would check is
> I/O. Maybe it's doing text I/O?
> 
> Hmm, thinking a bit further: every time my images show up with
> funny colors on the mac it turns out I haven't set foreground
> and background colors to white and black before doing the
> bitblit(), so that's also worth checking.
> --

There are no CopyBits in tifflib.
Perhaps its made in the Img lib, but there it uses the X emulation
stuff, so its probably ok.

I got suspicious about endian things, so I changed some if the
defines that handles this (HOST_BIGENDIAN, FILLORDER_MSB2LSB) 
but no change as far as I could find.

Mats

[MACTCL] Re: Img port

[Jack J. <Jac...@or...>]

On Wednesday, January 23, 2002, at 06:20  PM, Mats Bengtsson wrote:

>
> Update,
>
> Got CW 6 tiff project from Jack, used the archive from his site (3.3?)
> added #include <fcntl.h> in tiffcomp.h, made it into a shared lib,
> replaced tiff.shlb, but only blue and black shows correctly.
> The first one (3.5.7), shows red and white correctly, very funny...
> This beats me, anyone...

Note that the I/O component of libtiff is pretty finicky. As the 
library was distributed (I got it about 8 years ago, I think) it 
used raw MacOS File Manager calls. The library as it is in my 
distribution (if I remember correctly) uses the Unix I/O file 
for libtiff and then uses either GUSI for unix-style 
open/close/read/write I/O or whatever MSL gives you. But for 
Python I did a workaround at some point to use stdio for I/O, 
because there were some problems with the other two I/O methods.

So to make a long story short: the first thing I would check is 
I/O. Maybe it's doing text I/O?

Hmm, thinking a bit further: every time my images show up with 
funny colors on the mac it turns out I haven't set foreground 
and background colors to white and black before doing the 
bitblit(), so that's also worth checking.
--
- Jack Jansen        <Jac...@or...>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- 
Emma Goldman -

[MACTCL] Re: Img port

[Mats B. <ma...@pr...>]

Update,

Got CW 6 tiff project from Jack, used the archive from his site (3.3?)
added #include <fcntl.h> in tiffcomp.h, made it into a shared lib,
replaced tiff.shlb, but only blue and black shows correctly.
The first one (3.5.7), shows red and white correctly, very funny...
This beats me, anyone...

Anyhow, Img now loads png.shlb, jpeh.shlb, tiff.shlb, and libz.shlb,
from the "Tool Command Language" folder. Felt a bit fragile to put them
in the Extensions folder.

The "test all" suit fails for -data for gif and tiff images.
Perhaps someone can jump in here and explain...

Daniel Steffen wrote:
> thanks for doing this, Img has been on my todo list for a while...
> 
> I'd be interested in a copy, if you want I can also host it on my 
> page with the other mac tcl extensions 
> (http://www.maths.mq.edu.au/~steffen/tcltk/)

I'll send you the complete stuff tomorrow. Must coordinate with
the package maintainer (Jan) so we don't fork it unnecessarily.

Mats

Re: [MACTCL] Mac OS X: help with C app which uses Tk?

[Jim I. <ji...@ap...>]

Jack,

I think what he is trying to do is have a structure like:

Application.app
 Contents
   Frameworks
      Tcl.framework
      Tk.framework

And have it work so that the user could drag around Application.app in the
Finder, and put it wherever he/she wanted, and double-clicking would find
all the libraries.  This is what the @executable_path is for.  You set up
the dyld link string for the App to be:

@executable_path/../Frameworks/Tcl.framework

(this is the bit that I don't remember how you do)...  And ditto for
Tk.framework, and then the Application.app will do the right thing.  Among
other things, the ability to do this, so that an app could transparently
ship with its own complete copy of Tcl, Tk and all the support files, if it
wanted to, was a strong argument in my mind for using the Framework
structure in the first place...

I know this works, 'cause I have seen traffic about it on the PB list.  But
I don't think that PB supports it yet (should be another bit in the
Framework dependency  entry for bundled Frameworks, and PB would do all the
requisite magic.  I also know that they intend to support this at some
point, but it is not as high on their list as some other things right now...

Jim


> 
> On Monday, January 21, 2002, at 07:32  PM, Jim Ingham wrote:
> 
>> On 1/21/02 7:54 AM, "Ashley Ward" <ash...@nt...> wrote:
>> 
>>> Any hints would be appreciated!
>> 
>> If you want to package Frameworks in your app, you are supposed
>> to put the
>> cookie: @executable_path in the name of the framework you are
>> linking to,
>> and dyld will resolve the reference relative to where the
>> executable lives
>> in your App bundle.
> 
> Do you mean that your private frameworks aren't on the search
> path by default? I haven't tried this yet, but I was assuming
> that if you link with "-framework Foo" and you then copy this
> Foo framework from /Library/Frameworks/Foo.framework to
> /Applications/MyApp.app/Contents/Frameworks/Foo.framework it
> would find it automatically.
> 
> I know that dyld *does* find frameworks in the current directory
> if you add "-Wl,-F." to your link command line. When I'm
> building Python I link against Python.framework. At build time
> this is simply a subdirectory of the current directory, and the
> resulting executable works fine with that. Later, when
> everything has been installed, the same executable runs just as
> fine with the framework in /Library/Frameworks/Python.framework.
> 
> Hmmm, long paragraph, but what I wanted to suggest is try adding
> "-Wl,-F../FrameWorks" to your link line.
> --
> - Jack Jansen        <Jac...@or...>
> http://www.cwi.nl/~jack -
> - If I can't dance I don't want to be part of your revolution --
> Emma Goldman -
> 
> 
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
> 

-- 
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham                              ji...@ap...
Developer Tools - gdb

Re: [MACTCL] Mac OS X: help with C app which uses Tk?

[Jack J. <Jac...@or...>]

On Monday, January 21, 2002, at 07:32  PM, Jim Ingham wrote:

> On 1/21/02 7:54 AM, "Ashley Ward" <ash...@nt...> wrote:
>
>> Any hints would be appreciated!
>
> If you want to package Frameworks in your app, you are supposed 
> to put the
> cookie: @executable_path in the name of the framework you are 
> linking to,
> and dyld will resolve the reference relative to where the 
> executable lives
> in your App bundle.

Do you mean that your private frameworks aren't on the search 
path by default? I haven't tried this yet, but I was assuming 
that if you link with "-framework Foo" and you then copy this 
Foo framework from /Library/Frameworks/Foo.framework to 
/Applications/MyApp.app/Contents/Frameworks/Foo.framework it 
would find it automatically.

I know that dyld *does* find frameworks in the current directory 
if you add "-Wl,-F." to your link command line. When I'm 
building Python I link against Python.framework. At build time 
this is simply a subdirectory of the current directory, and the 
resulting executable works fine with that. Later, when 
everything has been installed, the same executable runs just as 
fine with the framework in /Library/Frameworks/Python.framework.

Hmmm, long paragraph, but what I wanted to suggest is try adding 
"-Wl,-F../FrameWorks" to your link line.
--
- Jack Jansen        <Jac...@or...>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- 
Emma Goldman -

[MACTCL] Re: Img port

[Jack J. <Jac...@or...>]

On Monday, January 21, 2002, at 08:04  PM, Mats Bengtsson wrote:

>
>
> Jack Jansen wrote:
>>
>> On Saturday, January 19, 2002, at 12:58  PM, Mats Bengtsson wrote:
>>>
>>> 1)    I build the image libs, libjpeg, libtiff, libpng, and zlib, as
>>> separate shared libs (which is how it works on win and unix),
>>> which get loaded at runtime by Img. But the loading is made from
>>> tcl's present folder (Build) which is not what you want.
>>> BTW: Img uses tclMacLoad.c from 8.0p2 to do this, which needed
>>> some patching to work.
>>> Any better solution here? Can't run the test suite because of this,
>>> I think.
>>
>> You should be able to store them in the Extensions folder, I think.
>>
>
> Doesn't work:
> % package require Img
> 1.2.4
> (Build) 2 % image create photo -file [tk_getOpenFile]
> cannot open jpeg.shlb: file not found
>
> It fails when executing:
>     err = FSpLocationFromPath(strlen(path), (char *) path, &fileSpec);
> where path = "jpeg.shlb", and then it does things I don't understand
> including a call GetDiskFragment().

Sorry, misunderstanding on my part. If the img extension had 
been linked against the jpeg library you could have put it in 
the extension folder. But apparently img manually loads 
"jpeg.shlb". I don't know how to solve this, you should ask the 
img author.
>

>> Darn. I have the CW6 projects somewhere still in CVS, but I
>> would need to dig them out. I'll try to do so next week, if you
>> don't hear from me by tuesday drop me another note (because I'll
>> have forgotten;-)
>
> I'd appreciate that. No hurry. Thanks.

It's coming in a separate mail (from a different machine).

--
- Jack Jansen        <Jac...@or...>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- 
Emma Goldman -

Re: [MACTCL] Mac OS X: help with C app which uses Tk?

[Jim I. <ji...@ap...>]

On 1/21/02 11:05 AM, "Jon Guyer" <jg...@hi...> wrote:

> At 10:32 AM -0800 1/21/02, Jim Ingham wrote:
> 
>> There are some tantalizing #defines in the Carbon headers for
>> tearoff menus, but they don't do anything yet...
> 
> ...now only if we had an "in" with somebody at Apple...

The Carbon folks get a little testy when you ask them when your favorite
feature is going to get done.  Apparently they get lots of such requests ;-)

They were actually very helpful when I was trying to get the Notifier to
work (though the result was that we couldn't use Carbon Events - wah...)
But they are a tad busy right now...

Jim
-- 
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham                              ji...@ap...
Developer Tools - gdb

Re: [MACTCL] Mac OS X: help with C app which uses Tk?

[Jon G. <jg...@hi...>]

At 10:32 AM -0800 1/21/02, Jim Ingham wrote:

>There are some tantalizing #defines in the Carbon headers for
>tearoff menus, but they don't do anything yet...

...now only if we had an "in" with somebody at Apple...

-- 

   Jonathan E. Guyer
   <http://www.his.com/jguyer/>

[MACTCL] Re: Img port

[Mats B. <ma...@pr...>]

Jack Jansen wrote:
> 
> On Saturday, January 19, 2002, at 12:58  PM, Mats Bengtsson wrote:
> >
> > 1)    I build the image libs, libjpeg, libtiff, libpng, and zlib, as
> > separate shared libs (which is how it works on win and unix),
> > which get loaded at runtime by Img. But the loading is made from
> > tcl's present folder (Build) which is not what you want.
> > BTW: Img uses tclMacLoad.c from 8.0p2 to do this, which needed
> > some patching to work.
> > Any better solution here? Can't run the test suite because of this,
> > I think.
> 
> You should be able to store them in the Extensions folder, I think.
> 

Doesn't work:
% package require Img
1.2.4
(Build) 2 % image create photo -file [tk_getOpenFile]
cannot open jpeg.shlb: file not found

It fails when executing:
    err = FSpLocationFromPath(strlen(path), (char *) path, &fileSpec);
where path = "jpeg.shlb", and then it does things I don't understand
including a call GetDiskFragment(). 
I guess it's pretty easy to fix, but should
I get the path to the extensions folder, or is there
another strategy, for instance, to have an all-in-one shared lib with
all image libs included?
I'll figure out something.

> > 2)    Tested opening a number of various image formats, and all
> > work except tiff images, where only the red component shows.
> > When searching the net for mac parts I found a later release of
> > tifflib (3.5.7) which I use. Tried Jack Jansen's mac port, but
> > the CW 7 projects wheren't useful with my CW 6 since all essential
> > settings were lost during conversion.
> 
> Darn. I have the CW6 projects somewhere still in CVS, but I
> would need to dig them out. I'll try to do so next week, if you
> don't hear from me by tuesday drop me another note (because I'll
> have forgotten;-)

I'd appreciate that. No hurry. Thanks.

Daniel Steffen wrote:
> I'd be interested in a copy, if you want I can also host it on my 
> page with the other mac tcl extensions 
> (http://www.maths.mq.edu.au/~steffen/tcltk/)

Thanks, that would be nice. Need to discuss this with Jan Nijtmans also.
I'll send you a copy once I've cleaned it up a bit.

> you could try merging the image shared libraries into the Img shlb 
> (set the merge flag in the info window for the libs) and load them 
> from the current fragment file.
> do you really need to load them explicitly or could you just link 
> against them and let the CFM loader do the work for you?

Merging them I know how to do, but loading them from current fragment
I don't know how it works. Perhaps you could give it a try?

> If you like, I can export Pro7 projects to xml for you which Pro6 can 
> import without loosing settings...

See if Jack comes up with something for me...

Mats

Re: [MACTCL] Mac OS X: help with C app which uses Tk?

[Jim I. <ji...@ap...>]

On 1/21/02 7:54 AM, "Ashley Ward" <ash...@nt...> wrote:

> Any hints would be appreciated!

If you want to package Frameworks in your app, you are supposed to put the
cookie: @executable_path in the name of the framework you are linking to,
and dyld will resolve the reference relative to where the executable lives
in your App bundle. I haven't ever done this, so I am not sure exactly how
it works.  I am pretty sure it was discussed both on Apple's ProjectBuilder
mailing list, and on the OmniGroup dev lists.  You can probably find it by
searching the archives for @executable_path.  If you can't find it, ping me
again and I will ask around.

> 
> Also, I have a few bugs in my app which, now I've noticed them, seem to also
> occur in Wish, so I assume they are Tcl/Tk bugs.

For all these, file bugs with SourceForge if you don't mind.  Code snippets
which show the problem would also be helpful.  Also, I am finding myself
really busy lately, so if any of these are crucial to your app, you may need
to take a whack at fixing them yourself.

> 
> - Cut and paste from other applications doesn't work (it seems OK within the
> app).

This should be easy to fix.  We just carried over the Classic MacOS Scrap
Manager code to X.  That is supported in Carbon, so we probably just messed
up the conversion.

> 
> - In the scroll bar, the down button is only slightly visible: it is
> obscured by the window resize widget.

You can usually get around this by packing the scrollbar & the widget it
drives in a containing frame.  The support for the resize widget is a bit of
a hack, but we felt at the time it was better than forcing everyone to have
to manually provide it.

> 
> - When dragging the title bar of a window in order to move it, it seems
> necessary to give it focus first.

Humm... 

> 
> - 'Hide tkeden' (in the left most menu) doesn't work.  Wish seems to die
> unexpectedly when this is chosen.

This should be easy to fix.  These menus are provided in tkMacOSXMenus.c.  I
bet we just sketched this in and didn't get around to finishing it.

> 
> - I have some menus with -tearoff set.  This is implemented as a
> "(Tear-off)" menu option, which creates a torn off menu at the extreme
> top-left of the screen, with the first item behind the Apple menu bar :(

Tearoff menus don't work.  They are not provided by the Aqua menu manager,
so they are just part of the Tk MDEF that we moved over from the Classic
version.  There were other problems with this MDEF (it looked horrible
'cause it used QuickDraw to draw the text, and had a bunch of scrolling &
other problems.)  So I am not supporting it right now.

There was a sample MDEF project for X that Apple DTS posted in the last
developer mailing which looked like it might have clues on how to fix a
bunch of problems I was having with this.  It would be worthwhile to give
this another look later on.  But this was a notoriously buggy part of the
Classic MacOS Tk port, and I would be happier to use the System MDEF if
possible.  There are some tantalizing #defines in the Carbon headers for
tearoff menus, but they don't do anything yet...

> 
> - Maximise (+) button doesn't work.

Say more.

> 
> - The Aqua close / minimise / maximise buttons in the title bar don't show
> their x - + inners when the mouse is moved over them.

Yeah, we probably have to track this by hand.  We were using Carbon Events
for the Window decoration management for a long time - which gave all all
these behaviors for free, and we almost got it to work, but there were just
too many odd times where the Carbon Event manager and Tk's Notifier would
fight over who got events, resulting in much suffering & sadness.  So we
finally had to go back to fielding all events by hand.

This is probably the cause of the title bar dragging problem as well.

> 
> Finally, the other bug which I could do with some help on (I have lots more,
> but I hope I can fix these myself!) is that the About option in the left
> most menu for my app is actually "About Tcl & Tk" and leads to that
> information.  How do I override this to show my own About information?
> 

This works pretty much the same way it works in Classic MacOS.  You create a
menubar for your app, and then add a cascade item to it called "apple", so:

toplevel .t
menu .t.mbar
menu .t.mbar.apple
.t.mbar add cascade .t.mbar.apple
.t.mbar.apple add command -label "About MyApp" -command myAboutDialog

Etc.   The items you add to the "apple" menu (the name is an anachronism on
X, it should really be called the "Application" menu) will go above the
system provided menu items.

Jim
-- 
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham                              ji...@ap...
Developer Tools - gdb