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

Re: [MACTCL] tkConfig.sh

[Marc-Antoine P. <map...@ac...>]

>> Well, I also had to adjust that application to use the #include 
>> <Tk/tk.h> notation...
>> Do you think we could push for the include notation to be specified in 
>> the t_Config.sh-es ?
>> Actually, the best would be to add a flag saying : This is a (Darwin) 
>> framework. That flag could then impact both the compilation/linkage 
>> flags and the import notation. I also see the import of this since 
>> darwin can accommodate Tcl and Tk as either shared libraries or as 
>> frameworks; and Tk as either a X11 or Aqua library. Both are valid 
>> choices to different users, and the configuration files should not 
>> infer either from the platform alone.
>> Hence the importance of a 'framework' flag...
>
> I am not sure whether is is best to work this into configure or do it 
> as a post-processing step.  I was planning tenatively to do the 
> "#include <Tcl.h>" -> "#include <Tcl/Tcl.h>" when  I moved the headers 
> into the framework, I see no reason to load down the configure for all 
> the other platforms with this detail, and it would be very easy to do 
> this as a shell script build phase in PB.  However, I did add a 
> framework macro to the tcl.m4 in tcl/unix, and use the defines in a few 
> places in configure.in.  So there is some structure in place on the tcl 
> build side to do this.  I tend to the PB solution myself, 'cause I like 
> working in PB.  Again, if some ambitious person wants to get together 
> the configure/make for Tk, I would at least use the configure part to 
> generate the tkConfig.sh in my PB project...
>
> On Darwin & frameworks...  Wilfredo was moving away from using 
> Frameworks for all the Darwin stuff.  He thought it was a bad idea to 
> add all this work to EVERY Unix project.  I don't know what Jordan's 
> feeling on this is, however.  In my case, the Tcl build will be 
> different for Mac OS X and Darwin, since I want to build in the 
> Resource handling stuff, some understanding of aliases, and the 
> AppleScript and maybe TclAE, and have all this be a standard part of 
> the Tcl distro...  So I don't think that Darwin & Mac OS X Tcl need to 
> have the same distribution mechanism.

I agree with you that the Darwin and MacOSX Tcl/Tk are different beasts, 
and do not need to use the same mechanisms.
This is precisely why I believe we need to "burden" the unix build 
mechanisms, such as  TkConfig.sh, with the dylib vs framework 
distinction. Indeed, the problem goes beyond building the Tcl/Tk 
frameworks from the command line or ProjectBuilder; all unix clients of 
the Tcl/Tk code (like Mozart, and Python, and...) need to change, not 
only their compile and link flags (handled by tkConfig.sh) but also 
their #include directives to adjust to an (optionally) framework-based 
Tcl/Tk... We cannot expect all these to use PB. That means that the 
Tcl/Tk framework must expose its frameworkness to the unix world. This 
is why I made the half-joke, half daydream that the notion of framework, 
and what it entails for the build process, will eventually have to make 
it all the way to autoconf! (I understand why Wilfredo Sanchez was 
reluctant. But I think that frameworks are a Good Idea in terms of what 
they allow for linking, and the *n*x community at large can benefit.)

So, formally, my short-term proposal is to add 
"TK_DARWIN_FRAMEWORK=true" to the tkConfig.sh (idem for tcl, of course) 
so that we can test for this flag in the mozart codebase, and choose the 
#include directive accordingly.

Enjoy!

Marc-Antoine Parent

[MACTCL] Re: Tcl/Tk 8.3.4 candidate archives ready

[Daniel A. S. <st...@ic...>]

[[ This message was both posted and mailed: see
   the "To," "Cc," and "Newsgroups" headers for details. ]]

In article <3BC...@Ac...>, Jeff Hobbs
<Je...@Ac...> wrote:

> You can get the candidate release at:
> 
>     http://sourceforge.net/project/showfiles.php?group_id=10894
> 
> in the 8.3.4 Release Candidate section.

I have added installers for the mac binary build to the 8.3.4 Release
Candidate section on sourceforge.

report problems with those to me <mailto:da...@us...> and
not Jeff...

Cheers,

Daniel

Re: [MACTCL] tkConfig.sh

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

Marc-Antoine,

On Thursday, October 18, 2001, at 09:22  PM, Marc-Antoine Parent wrote:

> Thank you, Jim, for a prompt answer.
>
> Yes, I got confused between tclConfig.sh and tkConfig.sh
> I took a simplistic stab at the latter by taking the former and 
> applying s/tcl/tk/g; through it (more or less ;-)
> I also added the X11 header locations.

Thanks, I will have a look.

>
> Finally, I had to put some headers into Headers as opposed to 
> PrivateHeaders (as suggested by Tony Lownds) and I could actually 
> compile my application.
> (Wow!)

Great!  I have to ask one of the compiler fellows what is the magic that 
gets the Private Headers to be seen.  It is possible, but maybe there is 
some  compiler flag needed or something.

>
> Well, I also had to adjust that application to use the #include 
> <Tk/tk.h> notation...
> Do you think we could push for the include notation to be specified in 
> the t_Config.sh-es ?
> Actually, the best would be to add a flag saying : This is a (Darwin) 
> framework. That flag could then impact both the compilation/linkage 
> flags and the import notation. I also see the import of this since 
> darwin can accommodate Tcl and Tk as either shared libraries or as 
> frameworks; and Tk as either a X11 or Aqua library. Both are valid 
> choices to different users, and the configuration files should not 
> infer either from the platform alone.
> Hence the importance of a 'framework' flag...

I am not sure whether is is best to work this into configure or do it as 
a post-processing step.  I was planning tenatively to do the "#include 
<Tcl.h>" -> "#include <Tcl/Tcl.h>" when  I moved the headers into the 
framework, I see no reason to load down the configure for all the other 
platforms with this detail, and it would be very easy to do this as a 
shell script build phase in PB.  However, I did add a framework macro to 
the tcl.m4 in tcl/unix, and use the defines in a few places in 
configure.in.  So there is some structure in place on the tcl build side 
to do this.  I tend to the PB solution myself, 'cause I like working in 
PB.  Again, if some ambitious person wants to get together the 
configure/make for Tk, I would at least use the configure part to 
generate the tkConfig.sh in my PB project...

On Darwin & frameworks...  Wilfredo was moving away from using 
Frameworks for all the Darwin stuff.  He thought it was a bad idea to 
add all this work to EVERY Unix project.  I don't know what Jordan's 
feeling on this is, however.  In my case, the Tcl build will be 
different for Mac OS X and Darwin, since I want to build in the Resource 
handling stuff, some understanding of aliases, and the AppleScript and 
maybe TclAE, and have all this be a standard part of the Tcl distro...  
So I don't think that Darwin & Mac OS X Tcl need to have the same 
distribution mechanism.

>
> (This idea goes for all Darwin frameworks, and should someday be 
> implemented at the level of autoconf! OK, I'm dreaming aloud.)
>
> On another note:
> Now that I have the resulting Tk wrapper for Mozart, I attempted to use 
> some Mozart sample code that draws on a AquaTk canvas in a window.
> The window was created as an unselected window, and did not respond to 
> any mouse click by becoming selected (frontmost.) I could draw into it 
> with Mozart code, but the image in the Canvas did not refresh unless I 
> passed another window over the AquaTk window.
>

I don't know what you are doing in Mozart.  Do you mean by "AquaTk 
canvas" just the standard canvas widget - for instance are you just 
adding some more canvas item types?  Or are you just getting the window 
of a canvas widget and drawing on top of it?  Or have you written your 
own custom canvas to draw into?  The standard Canvas widget works fine, 
redraws, responds to the mouse, etc.  So you should probably look at 
what you are doing differently from all the canvas widget.

> The mozart code used to do a perfectly selectable window under 
> Tk/XFree86. (But that was under Tk 8.3, not 8.4)
>
> Do you think that our Mozart Tk wrapper is lacking some event trapping 
> code that appeared in Tk 8.4? (Does not feel likely!)
> Or is it rather due to problems with the current state of the Tk 
> implementation? And where do you think I should go looking for those?
>

Describe more what you do, and I can give you some kind of answer.  I 
don't know enough now to speculate usefully.

Jim
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham                                                           
ji...@ap...
Developer Tools - gdb

Re: [MACTCL] tkConfig.sh

[Marc-Antoine P. <map...@ac...>]

Thank you, Jim, for a prompt answer.

Yes, I got confused between tclConfig.sh and tkConfig.sh
I took a simplistic stab at the latter by taking the former and applying=20=

s/tcl/tk/g; through it (more or less ;-)
I also added the X11 header locations.
<Fichier joint : tkConfig.sh>
Finally, I had to put some headers into Headers as opposed to=20
PrivateHeaders (as suggested by Tony Lownds) and I could actually=20
compile my application.
(Wow!)

Well, I also had to adjust that application to use the #include=20
<Tk/tk.h> notation...
Do you think we could push for the include notation to be specified in=20=

the t_Config.sh-es ?
Actually, the best would be to add a flag saying : This is a (Darwin)=20
framework. That flag could then impact both the compilation/linkage=20
flags and the import notation. I also see the import of this since=20
darwin can accommodate Tcl and Tk as either shared libraries or as=20
frameworks; and Tk as either a X11 or Aqua library. Both are valid=20
choices to different users, and the configuration files should not infer=20=

either from the platform alone.
Hence the importance of a 'framework' flag...

(This idea goes for all Darwin frameworks, and should someday be=20
implemented at the level of autoconf! OK, I'm dreaming aloud.)

On another note:
Now that I have the resulting Tk wrapper for Mozart, I attempted to use=20=

some Mozart sample code that draws on a AquaTk canvas in a window.
The window was created as an unselected window, and did not respond to=20=

any mouse click by becoming selected (frontmost.) I could draw into it=20=

with Mozart code, but the image in the Canvas did not refresh unless I=20=

passed another window over the AquaTk window.

The mozart code used to do a perfectly selectable window under=20
Tk/XFree86. (But that was under Tk 8.3, not 8.4)

Do you think that our Mozart Tk wrapper is lacking some event trapping=20=

code that appeared in Tk 8.4? (Does not feel likely!)
Or is it rather due to problems with the current state of the Tk=20
implementation? And where do you think I should go looking for those?

Thank you again,
and enjoy!

Marc-Antoine

Le Jeudi 18 octobre 2001, =E0 01:53 , Jim Ingham a =E9crit :

> Marc-Antoine,
>
> There is a little more work than just providing the tkConfig.sh.  The=20=

> tclConfig.sh file actually is in the framework (in Headers) but it=20
> doesn't work for the Framework structure yet, as opposed to the=20
> standard Unix distro.
>
> I need to figure out what has to be changed both in the *Config.sh=20
> files, and maybe in the Header files (they may have to use framework=20=

> include notation internally) to get this to all work.  I am looking=20
> into this now (I also have to take all my current changes and make=20
> TIP's for them, and try to get them accepted for the 8.4 release,=20
> however, and I have a day job, so any help here would be gladly=20
> accepted)...
>
> So if you want to take a stab at this yourself, that would be fine.  I=20=

> suggest first just hand editing the tclConfig.sh & tkConfig.sh  and=20
> manually inserting them in the headers directory of the framework,=20
> untill they work for you.  There is a tclConfig.sh already which =
almost=20
> works, but I don't use the Unix configure for Tk so there is no=20
> tkConfig.sh.  You will have to edit tkConfig.sh.in from tk/generic in=20=

> the source tree.  Then when you get something that works, look at what=20=

> we need to do to auto-generate that in the build.
>
> Once we know this, then the next step is to do this in a way that will=20=

> be easy for other extension developers to adopt.
>
> This is what I am planning to do, but I for sure won't get to it =
before=20
> the weekend.  So, if someone figures it out before me, I will be very=20=

> happy...
>
> As to what will happen with Tcl/Tk in the MacOS X distribution, I=20
> really can't say anything about that at present, sorry...
>
> Jim

Re: [MACTCL] tkConfig.sh file?

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

Russ,

The pundits guide is "Jim hasn't worked this out yet..."  I think I said 
this in the release notes.

If you want to help, then take the tclConfig.sh in Tcl.framework, and 
take tkConfig.sh.in from the source tree, and mess around with them till 
they work for you, and send me the results.  Then I just need to figure 
out how to auto-gen these in the build process.  If you want to do this 
too, even better!!!

Otherwise, you have to wait till I can get some time to figure out how 
this should work for MacOS X.

Jim

On Thursday, October 18, 2001, at 12:02  PM, Russ McBride wrote:

>
> I'm attempting to configure a PostgreSQL database with pgAccess, which 
> is a tck/tk interface that can be used to control my db. During the 
> configure process I get a complaint that the  tkConfig.sh file can't be 
> found, because of course there is no such file.  I'm sure that I've 
> botched the tcl/tk setup process due to my incredible ignorance of the 
> architecture here (I do however have the general PG install process 
> wired--see http://www.psyex.com/techdocs/pgonx for info on getting PG 
> up and running on OS X).  It also seems like this must be a regular 
> problem--configuring an app that requires the tkConfig.sh file.  What 
> do the pundits do here?
>
> Perhaps I need "Gumby's install guide for tck/tk".  So far, all I've 
> done after downloading the "snapshots" is to stick the frameworks into 
> /Library/Frameworks/   . . . or may be I should have stuck them in 
> /System/Library/Frameworks ?
>
>
> Thanks in advance,
>
> Russ
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] tkConfig.sh file?

[Russ M. <Ru...@ps...>]

I'm attempting to configure a PostgreSQL database with pgAccess, 
which is a tck/tk interface that can be used to control my db. 
During the configure process I get a complaint that the  tkConfig.sh 
file can't be found, because of course there is no such file.  I'm 
sure that I've botched the tcl/tk setup process due to my incredible 
ignorance of the architecture here (I do however have the general PG 
install process wired--see http://www.psyex.com/techdocs/pgonx for 
info on getting PG up and running on OS X).  It also seems like this 
must be a regular problem--configuring an app that requires the 
tkConfig.sh file.  What do the pundits do here?

Perhaps I need "Gumby's install guide for tck/tk".  So far, all I've 
done after downloading the "snapshots" is to stick the frameworks 
into /Library/Frameworks/   . . . or may be I should have stuck them 
in /System/Library/Frameworks ?


Thanks in advance,

Russ

Re: [MACTCL] tkConfig.sh

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

Marc-Antoine,

There is a little more work than just providing the tkConfig.sh.  The 
tclConfig.sh file actually is in the framework (in Headers) but it 
doesn't work for the Framework structure yet, as opposed to the standard 
Unix distro.

I need to figure out what has to be changed both in the *Config.sh 
files, and maybe in the Header files (they may have to use framework 
include notation internally) to get this to all work.  I am looking into 
this now (I also have to take all my current changes and make TIP's for 
them, and try to get them accepted for the 8.4 release, however, and I 
have a day job, so any help here would be gladly accepted)...

So if you want to take a stab at this yourself, that would be fine.  I 
suggest first just hand editing the tclConfig.sh & tkConfig.sh  and 
manually inserting them in the headers directory of the framework, 
untill they work for you.  There is a tclConfig.sh already which almost 
works, but I don't use the Unix configure for Tk so there is no 
tkConfig.sh.  You will have to edit tkConfig.sh.in from tk/generic in 
the source tree.  Then when you get something that works, look at what 
we need to do to auto-generate that in the build.

Once we know this, then the next step is to do this in a way that will 
be easy for other extension developers to adopt.

This is what I am planning to do, but I for sure won't get to it before 
the weekend.  So, if someone figures it out before me, I will be very 
happy...

As to what will happen with Tcl/Tk in the MacOS X distribution, I really 
can't say anything about that at present, sorry...

Jim

On Wednesday, October 17, 2001, at 09:57  PM, Marc-Antoine Parent wrote:

> Good day, all!
> I have been trying to configure a project (Mozart) to link with the new 
> Tk/Aqua framework (Why not codename it AquaTik? ;-)
> (Thanks a lot for fine work, BTW)
> I like the fact that it's a framework and uses the -framework compiler 
> flag, but Mozart's configure script expects to find this information in 
> tclConfig.sh and tkConfig.sh. These files are not (yet) in the 
> framework. Do you agree that they should be added? (perhaps in the 
> Scripts directory of the framework, or one above...)
>
> If you think it should be done and want me to make  first attempt, I 
> may do so, but I do not know the Tcl/Tk codebase at all.
>
> Also, do you expect this to become mainstream in the Mac OS X 
> distribution? And does that mean that the /System/Library/Tcl bundle 
> will be replaced by the framework? (Again, I approve, but I'm trying to 
> see where things are going.)
>
> Enjoy!
>
> Marc-Antoine Parent
>
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] Re: Tcl-mac digest, Vol 1 #73 - 1 msg

[Paul B. <bl...@di...>]

At 12:16 16-10-01 -0700, you wrote:
>Send Tcl-mac mailing list submissions to
>         tc...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/tcl-mac
>or, via email, send a message with subject or body 'help' to
>         tcl...@li...
>
>You can reach the person managing the list at
>         tcl...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Tcl-mac digest..."
>
>
>Today's Topics:
>
>    1. Re: I have tried (Mats Bengtsson)
>
>--__--__--
>
>Message: 1
>Date: Tue, 16 Oct 2001 18:20:47 +0200
>From: Mats Bengtsson <ma...@pr...>
>Reply-To: ma...@pr...
>Organization: home
>To: tc...@li...
>Subject: Re: [MACTCL] I have tried
>
>
>
>Paul Blaga wrote:
> >
> > I have tried to use tkpaint under mac. It works fine, but I cannot save the
> > files. I receive a message complaining about the incorrect use of the
> > option "filetype". Now, I  don't know much about tcl/tk, does anybody know
> > what should I do?
> >
>
>Think this was a bug in 8.3.2 that was fixed (my patch) in 8.3.3
>
>Mats

I tried and it really works !!!!!

Many thanks,

Paul




>--__--__--
>
>_______________________________________________
>Tcl-mac mailing list
>Tc...@li...
>https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
>
>End of Tcl-mac Digest

=====================================================================================
  Dr. Paul A. Blaga
  Universita degli Studi di Ancona
  Dipartimento di Matematica "Vito Volterra"
  Via Brecce Bianche
  60131 Ancona, Italia

[MACTCL] tkConfig.sh

[Marc-Antoine P. <map...@ac...>]

Good day, all!
I have been trying to configure a project (Mozart) to link with the new 
Tk/Aqua framework (Why not codename it AquaTik? ;-)
(Thanks a lot for fine work, BTW)
I like the fact that it's a framework and uses the -framework compiler 
flag, but Mozart's configure script expects to find this information in 
tclConfig.sh and tkConfig.sh. These files are not (yet) in the 
framework. Do you agree that they should be added? (perhaps in the 
Scripts directory of the framework, or one above...)

If you think it should be done and want me to make  first attempt, I may 
do so, but I do not know the Tcl/Tk codebase at all.

Also, do you expect this to become mainstream in the Mac OS X 
distribution? And does that mean that the /System/Library/Tcl bundle 
will be replaced by the framework? (Again, I approve, but I'm trying to 
see where things are going.)

Enjoy!

Marc-Antoine Parent

Re: [MACTCL] Tkinter & Tk/Aqua

[Tony L. <to...@me...>]

>
>The official way to do framework include and linking is to use:
>
>-framework Tcl -framework Tk
>
>and then use <Tcl/Tcl.h>, etc...   The problem is that we are going 
>to have to use the framework notation for ALL the headers.

Ouch. Processing as you copy into the framework seems like a good 
idea. You know, IIRC, Python use a framework and it doesn't run into 
this for header files inside the framework because all header files 
are in one directory. So if you can put tclPlatDefs.h and friends in 
Headers/ instead of PrivateHeaders/ maybe that problem will go away. 
Just a thought.

>
>For now, you could also cheese out and just include from the source 
>tree for now.  I bet once you get it built your troubles will only 
>be beginning, since the Mac OS X event loop and the Mac event loop 
>and the Unix event loops are all totally different...  Jack Jensen 
>and I have discussed this a little bit, but we haven't reached any 
>firm conclusions yet.

Ok, good advice.

Thanks Jim,

-Tony


-- 

Re: [MACTCL] Tkinter & Tk/Aqua

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

Tony,

On Tuesday, October 16, 2001, at 08:20  PM, Tony Lownds wrote:

> Hi Jim,
>
> I'm trying to link Python's Tk interface with the new Tk/Aqua stuff.
>
> I can get everything to compile and link, but I don't like how I have 
> to do it. I'm hoping you have some suggestions.
>
> This is how the compile step looks when it works:
>
> cc  -g -O3 -Wall -Wstrict-prototypes -no-cpp-precomp -fno-common 
> -dynamic
>     -I. -I../Include -DHAVE_CONFIG_H  -DWITH_APPINIT
>     -I/Library/Frameworks/Tcl.framework/Headers/
>     -I/Library/Frameworks/Tcl.framework/Versions/Current/PrivateHeaders/
>     -I/Library/Frameworks/Tk.framework/Headers/
>     -I/Library/Frameworks/Tk.framework/Versions/Current/PrivateHeaders/
>     -c ../Modules/_tkinter.c -o Modules/_tkinter.o
>
> The -I that reaches into the framework seems necessary because when I 
> use a -framework option on the compile step the compiler can't find 
> tclPlatDefs.h, included from tcl.h. Apparently the files in 
> PrivateHeaders aren't being found.
>
> Also, to compile against the frameworks I have to change the 
> _tkinter.c  sources to #include <Tcl/tcl.h> and <Tk/tk.h>, which is OK 
> but not ideal - do you know of any magic compiler options to avoid that?
>

The official way to do framework include and linking is to use:

-framework Tcl -framework Tk

and then use <Tcl/Tcl.h>, etc...   The problem is that we are going to 
have to use the framework notation for ALL the headers.  So for instance 
tcl.h just does:

#include <tclDecls.h>

which has to be:

#include <Tcl/tclDecls.h>

etc...

As I said in the announcement, I haven't really had ANY time to play 
with the details of getting the framework version of Tk to be useful for 
building extensions, of which TkInter is an extreme form.  For now, I 
have been using the source tree instead.  For instance, I need to figure 
out some good way of stuffing the framework style includes into the 
headers, maybe as I copy them over into the framework?  Anyway, I just 
haven't thought about this yet.

For now, you could also cheese out and just include from the source tree 
for now.  I bet once you get it built your troubles will only be 
beginning, since the Mac OS X event loop and the Mac event loop and the 
Unix event loops are all totally different...  Jack Jensen and I have 
discussed this a little bit, but we haven't reached any firm conclusions 
yet.

> Finally, tk.h requires X11/{X,Xlib}.h, which is not included in the 
> snapshot. That also isn't being found when I compile with -framework 
> Tcl and -framework Tk.
>

Oops, I will copy them over in the next snapshot, till then, you can 
just copy them into the framework by hand from the sources.

> FYI, here is the linking command:
>
> cc -Wl,-F. -Wl,-flat_namespace,-U,_environ -bundle -framework Python
>        Modules/_tkinter.o Modules/tkappinit.o
>        -framework Tcl -framework Tk  -o Modules/_tkinter.so
>

Jim
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham                                                           
ji...@ap...
Developer Tools - gdb

[MACTCL] Tkinter & Tk/Aqua

[Tony L. <to...@me...>]

Hi Jim,

I'm trying to link Python's Tk interface with the new Tk/Aqua stuff.

I can get everything to compile and link, but I don't like how I have 
to do it. I'm hoping you have some suggestions.

This is how the compile step looks when it works:

cc  -g -O3 -Wall -Wstrict-prototypes -no-cpp-precomp -fno-common -dynamic
     -I. -I../Include -DHAVE_CONFIG_H  -DWITH_APPINIT
     -I/Library/Frameworks/Tcl.framework/Headers/
     -I/Library/Frameworks/Tcl.framework/Versions/Current/PrivateHeaders/
     -I/Library/Frameworks/Tk.framework/Headers/
     -I/Library/Frameworks/Tk.framework/Versions/Current/PrivateHeaders/
     -c ../Modules/_tkinter.c -o Modules/_tkinter.o

The -I that reaches into the framework seems necessary because when I 
use a -framework option on the compile step the compiler can't find 
tclPlatDefs.h, included from tcl.h. Apparently the files in 
PrivateHeaders aren't being found.

Also, to compile against the frameworks I have to change the 
_tkinter.c  sources to #include <Tcl/tcl.h> and <Tk/tk.h>, which is 
OK but not ideal - do you know of any magic compiler options to avoid 
that?

Finally, tk.h requires X11/{X,Xlib}.h, which is not included in the 
snapshot. That also isn't being found when I compile with -framework 
Tcl and -framework Tk.

FYI, here is the linking command:

cc -Wl,-F. -Wl,-flat_namespace,-U,_environ -bundle -framework Python
        Modules/_tkinter.o Modules/tkappinit.o
        -framework Tcl -framework Tk  -o Modules/_tkinter.so


Thanks,
-Tony
-- 

Re: [MACTCL] I have tried

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

Paul Blaga wrote:
> 
> I have tried to use tkpaint under mac. It works fine, but I cannot save the
> files. I receive a message complaining about the incorrect use of the
> option "filetype". Now, I  don't know much about tcl/tk, does anybody know
> what should I do?
> 

Think this was a bug in 8.3.2 that was fixed (my patch) in 8.3.3

Mats

[MACTCL] ANNOUNCE: Tcl/Tk for MacOS X...

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

I sent this to c.l.t & c.l.t.a yesterday, but it hasn't shown up yet.  
Anyway, enjoy!

Hi, all...

With a lot of support from Apple, I have at long last a fairly
workable port of Tk for Mac OS X.  The sources are currently on a
branch off of the Tcl/Tk 8.4a4 branch, the branch name is:

macosx-8-4-branch

Go to the SourceForge Tcl headquarters for more details, at:

http://tcl.sourceforge.net

I also put a binary snapshot of Wish and the Tcl & Tk Frameworks in
the SourceForge release, under the package name "Mac OS X Tk
Snapshots".  You can get to this by looking at the page:

http://sourceforge.net/projects/tcl/

and look for Latest File Releases.  Probably should have put this in
the Tk site instead, Doh!  I am just getting used to SourceForge.


SO HOW DO I USE THIS STUFF:

========================================
First for the binaries...

The snapshot is just a gzipped tar file, that has the structure:

Applications/Wish Shell.app
    ...
Library/Frameworks/Tcl.framework
    ...
Library/Frameworks/Tk.framework
    ...

So you can either untar this in / - to make an installation that is
available to all users on your machine, or in ~ to make one useable
only to you.  In any case, just double-click on Wish Shell.app to get
started.  You will probably also want to change the files to
make them owned by you...

In fact, you can move things around even more than this.  The
Frameworks just need to be in one of the system paths 
(/Library/Frameworks,
/System/Library/Frameworks, or ~/Library/Frameworks) to be found
automatically by dyld.  Or you can put them somewhere else and set
DYLD_FRAMEWORK_PATH to point to that location.

After that, you can put "Wish Shell.app" pretty much anywhere you
want.

One other little trick about the "Wish Shell.app" that may come in
handy.  If you put a file called "AppMain.tcl" inside the "Wish
Shell.app" package, in the folder:

Wish Shell.app/Contents/Resources/Scripts

then that will be sourced in as if you had given it as the first
argument on the command-line in Unix, or equivalently had made a D&D
Tclet with that file on the Mac.  The Mac OS X version goes one
better, because the Scripts directory is also added to the auto_path,
so you can put your script libraries there, and they will be found as
well.

The "Wish Shell.app" uses the same console that the Windows & Mac
ports use.  However, if you want to use a terminal console for some
reason, then just do:

$ ./Wish Shell.app/Contents/MacOS/Wish Shell"

in Terminal.app, and it will use the Terminal window instead of the Tk
based one.

There is some support for the Custom MDEF that Tk used on MacOS X, but
it is pretty rough right now, so I have turned it off by default.  If
you want to play with this, do:

set ::tk::mac::useCustomMDEF 1

somewhere BEFORE you create your menus, it will only affect
menus made after you change the setting.  The default setting is done
at the end of tk.tcl in the Resources/Scripts folder in the Tk
framework, so you can also just reverse this setting there to make
Wish always use the custom MDEF.

These binaries were built on Mac OS X - 10.1.  There is no obvious reason
why they wouldn't run on 10.0, but I haven't run that in quite a long
time, so I won't guarantee there aren't any little hitches.  10.1 is SO
much nicer than 10.0, however, that I am not inclined to spend much time
supporting it.

========================================
Next the source:

As I said, the sources are on the SourceForge CVS repositories, the
branch name is macosx-8-4-branch.  The projects expect tcl & tk to be
in the same folder, so like:

./source
     source/tcl
     source/tk

If they are not set up like this, you will have to go muck with the
include paths in the project.

Tcl:

On the Tcl side, there aren't many changes.  I added a MacOS X
directory, but all it contains at present is a Project Builder project
that will build Tcl in the way that Wish currently expects it to be
built.  You can also build the Tcl in this distribution with the
standard configure/make.  But I haven't added the ability to
auto-magically build the Framework from the Makefile.  That is what
the PB Project is for.

The one special thing to note is that Wish requires that you build
the --enable-thread version of Tcl.  I haven't put in any checks to
make sure you do this yet, but it will fail pretty much straight off
the bat if you don't, so...  This was required to wait on Tcl "select"
based sources and still keep Carbon waiting on the App Main Thread as
Ed intended.

I also want to migrate the AppleScript and Resource goodies from the
Classic Mac side to MacOS X, and also add an interface to the CFBundle
API's (which I am now using hackily in tclUnixInit.c).  But I haven't
gotten around to that yet.

Tk:

Tk has the majority of the changes, as you would expect.  There are
not any really substantial changes in the generic folder, there are
some in the library code, mostly because a lot of it assumes
tcl_platform(platform) == unix means you are using X11, which is not
the case for MacOS X.

Other that that, the code in the macosx folder is the interesting
bits.  It is a pretty straight Carbonization of the Classic Mac code,
but I also took advantage of the opportunity to toss alot of the cruft
from supporting earlier versions of MacOS, and to rework the code to
be a little more to my liking.

I didn't try to rework the Unix Makefiles to support building Wish on
MacOS X.  In part this was because there weren't many similarities
between the Unix & Mac OS X Makefiles, but mostly because I wanted to
use Project Builder, since I actually like GUI development
environments.  If someone with the opposite bent wants to hack up some
Makefiles, I would be happy to accept the changes.

The only trick to building Tcl & Wish is to set the Product
directories for the Tcl.pbproj and Wish.pbproj to the same directory
(either in the PB Global preferences, or in the super-secret Project
specific preferences that you find by selecting the Project entry in
the File tree, and doing "Show Info".)  Then build the topmost Tcl
agregate target, and then build the Wish Target.

In a couple of days I will get together a list of "current and future
projects" in case anyone is interested in helping.  There is a 
SourceForge
task manager that should be a good venue for this.  There is lots of fun
stuff still to do, by the way, including converting from QuickDraw to
CoreGraphics for the low-level drawing code - so we can get nice looking
line drawing onthe canvas, finally...  And using ATSUI, so we can get the
sweet anti-aliased fonts.

Extensions:

To tell the truth, I only started playing around seriously with
packaging all this stuff up in Frameworks & App Packages in the past
couple of weeks.  I think the structure offers a lot of promise, but I
haven't worked on porting extensions yet, so there will probably be
some refinements to make this easier as time goes on.

If you have a standard Tcl (not Tk) extension, the way Tcl.pbproj
builds things is a pretty good model.  It shows how to build
frameworks from a Makefile based approach without having to hack up
your Makefiles too badly.

I would like to figure out a way to do this more generally within the
TEA structure, while still getting to use PB, and inflicting the least
pain on other extension writers.  But I've only just started thinking
about this part.

Well, there are probably a lot more little stumbling blocks that I am
forgetting, but it is late, and I am sure you will all remind me of
them in due course.

One thing I can't omit, however, is a big THANKS to Apple, who let me
work with this in spite of my having another day job, to Dave Payne,
my manager, who supported this project even when gdb needed all the
coddling we could give it, to Sergio Mello from Apple DTS who found
the resources to hire Ian Reid to help out with this for the past 6
months, and to Ian, who did all the dog work while I mostly got to say
"Well, I think it should work like..."

Sometimes it even did...

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

Re: [MACTCL] Mac Menubutton - not sticking

[David R. <dr...@sa...>]

I finally tracked this problem down to a issue between Logitech
Mouseware v4.0.2 and Tcl 8.3.3.  While I'm far from an expert, I suspect
the source of the problem is the new release of the Mouseware driver and
not with Tcl 8.3.3.  Sorry to have troubled the group with what is
apparently a non-Tcl issue; thanks to Mats for taking the time to try to
duplicate the problem.  (If someone is successfully using the most
recent release of Mouseware, I would appreciate hearing about it.)

Cheers,

Dave Robinson




David Robinson wrote:
>
> I've dredged the archives for some insight into this problem with no
> luck and even (finally) tracked down the Mac Tcl FAQ.  I was certain I

> had seen something like this before in either this list or
comp.lang.tcl
> but I couldn't locate a reference;  sorry if this has been discussed
> before...
>
> I am having trouble getting my menubutton lists to 'stick'.  They
appear
> and then immediately disappear.  For what  it is worth, I am using
> Tcl/Tk 8.3.3, Mac OS 9.1 on a G4/450 Blue Tower.
>
> I spent a day or so trying to track things down in my code, but then
> when I ran Widget Demos/menubutton  I got the same result.  Any
insight
> into this would be greatly appreciated!
>

--
-------------------------------------------------------------------------------

David G. Robinson, PhD          E: dr...@sa...
Risk and Reliability Analysis   O: 505-844-5883
-------------------------------------------------------------------------------

Re: [MACTCL] How to Compile TCl on Mac

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

At 3:25 PM +0200 10/15/01, Andreas Otto wrote:

>   i download an install "TclTk_8.3.3_FullInstall.bin" and expect to
>   get everything needed to compile/install Tcl on Mac but it seems
>   to be not logic for me how to use it

During the installation, you need to select "Custom" install, and 
there you will find the options to install all of the source code and 
CW projects, etc. Yes, this confused me, too.

-- 

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

[MACTCL] How to Compile TCl on Mac

[<AO...@t-...>]

Hi,

  i download an install "TclTk_8.3.3_FullInstall.bin" and expect to 
  get everything needed to compile/install Tcl on Mac but it seems
  to be not logic for me how to use it


 any help available ?


mfg

  aotto .)

[MACTCL] I have tried

[Paul B. <bl...@di...>]

I have tried to use tkpaint under mac. It works fine, but I cannot save the 
files. I receive a message complaining about the incorrect use of the 
option "filetype". Now, I  don't know much about tcl/tk, does anybody know 
what should I do?

Many thanks,

Paul Blaga

=====================================================================================
  Dr. Paul A. Blaga
  Universita degli Studi di Ancona
  Dipartimento di Matematica "Vito Volterra"
  Via Brecce Bianche
  60131 Ancona, Italia

[MACTCL] ANNOUNCE: QuickTimeTcl 3.0b1

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

ANNOUNCE: QuickTimeTcl version 3.0b1 -----------------------------------

    First beta of QuickTimeTcl for Tcl/Tk for Macintosh and Windows.

    This is an extension package to Tcl/Tk that makes available a lot of
    QuickTime functionality for script programming.  Most of the features are
    collected into a movie widget, which results in an object oriented way of
    programming multimedia.

    Some features:

      * Simple playback of audio and video in a movie widget; for instance, play
	mp3, view VR panoramas, most video and sound formats, streaming live
	content from a broadcaster, shockwave/flash, etc.  Remote (URL) 
	connections can be made asynchronously.

      * A sequence grabber widget that previews and captures video and audio from
	an external source, such as a web camera or a DV video camera, via the 
	serial port, USB, or FireWire.

      * Editing commands, such as cut, copy and paste, both on complete movies 
	and down to individual tracks. Video effects through dialogs.

      * Versatile methods for making movies from individual images, supporting 
	sequence compression, usage of all appropriate QT codecs, compression 
	levels, keyframe rate etc.

      * Exporting to a number of audio/video formats via dialogs.

      * Most still image formats are supported implicitly by QuickTimeTcl but 
	via tk's own image widget.

    This release includes numerous bug fixes as well as many additional
    features compared to previous releases.  See the CHANGES file for a
    detailed list.  The most important additions from 3.0a3 are:

      * Making movies from still images, single or a sequence.  You can specify
      	compressors, bit depth, spatial and temporal compression qualities, and
      	more.  Adding a list of images you may utilize both temporal and spatial
      	compression for codecs that support this, resulting in highly optimized
      	movies.

      * A number of commands and options for QTVR panorama movies.

      * Reworked and extended ways of saving movies to disk.  There are four
      	different ways to save a movie.  Possible to handle the resource fork of
      	movie files.

      * Many options for adding text to a text track, support for text
      	descriptors.

      * Sequence grabber works on Windows now.  Possible to create an audio only
      	grabber.

      * May load movie completely into memory.

    ...and much more, not to mention all the bug fixes.  Mac and Windows 100%
    compatibility (only bugs may be different).

    "BSD style" license.

    Visit "http://hem.fyristorg.com/matben/qt/" for additional
    info and download.


    Enjoy,     Mats
    ma...@pr...

Re: [MACTCL] Mac Menubutton - not sticking

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

David Robinson wrote:
> 
> I've dredged the archives for some insight into this problem with no
> luck and even (finally) tracked down the Mac Tcl FAQ.  I was certain I
> had seen something like this before in either this list or comp.lang.tcl
> but I couldn't locate a reference;  sorry if this has been discussed
> before...
> 
> I am having trouble getting my menubutton lists to 'stick'.  They appear
> and then immediately disappear.  For what  it is worth, I am using
> Tcl/Tk 8.3.3, Mac OS 9.1 on a G4/450 Blue Tower.
> 
> I spent a day or so trying to track things down in my code, but then
> when I ran Widget Demos/menubutton  I got the same result.  Any insight
> into this would be greatly appreciated!
> 

Can't reproduce the problem. Using Tcl/Tk 8.3.3 and Mac OS 8.6 and 9.1.
You could try my native menubutton at 
"http://hem.fyristorg.com/matben/download/MacMenuButton.sit"
but bindings to the actual menu are the same.

/Mats

[MACTCL] Vertical Text on Label

[Mark J. <maj...@ya...>]

This is not  a MAC specific question, but I was hoping
someone on this list could answer my question ...

I want the label to have vertical text NOT horizontal 
on a widget (i.e., either label or button). Is there a
switch (option) to set the text to be vertical instead
of the default being horizontal??? Something like ...
WRAP CHARACTER???

The text widget has a "WORD" option to wrap the text
in it's widget, but I would like to control the wrap
on a label.

example :

instead of a button having the label appear like :    

-----------------
|   CAT      | 
-----------------

I would like the button to have the label appear like
:     

-------
| C | 
| A | 
| T | 
------

Thanks for any help.

Mark


__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com

[MACTCL] Mac Menubutton - not sticking

[David R. <dr...@sa...>]

I've dredged the archives for some insight into this problem with no
luck and even (finally) tracked down the Mac Tcl FAQ.  I was certain I
had seen something like this before in either this list or comp.lang.tcl
but I couldn't locate a reference;  sorry if this has been discussed
before...

I am having trouble getting my menubutton lists to 'stick'.  They appear
and then immediately disappear.  For what  it is worth, I am using
Tcl/Tk 8.3.3, Mac OS 9.1 on a G4/450 Blue Tower.

I spent a day or so trying to track things down in my code, but then
when I ran Widget Demos/menubutton  I got the same result.  Any insight
into this would be greatly appreciated!



Dave Robinson
dr...@sa...

Re: [MACTCL] tk_popup

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

Sebastian Liepe wrote:
> 
> Thank you for your help.
> Basicly it works, but the popup disappers afer one second.
> 
> ma...@pr... schrieb am 02.10.01:
> > Sebastian Liepe wrote:
> > >
> > > The tk_popup command does not work on my mac.
> > > Are there know limitations?
> > > Does anybody have a working example?
> >
> > A code snippet from my app. Just strip it to suit your needs.
> >

It shouldn't. Test my whiteboard at
"http://hem.fyristorg.com/matben/download/Whiteboard-0.93.sit"
draw an item, press button on item, vait for one sec, and popup.

/Mats

Re: [MACTCL] tk_popup

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

Sebastian Liepe wrote:
> 
> The tk_popup command does not work on my mac.
> Are there know limitations?
> Does anybody have a working example?

A code snippet from my app. Just strip it to suit your needs.

/Mats

-----------------------------

		menu $m -tearoff 0
		set mt [menu $m.thick -tearoff 0]
		$m add cascade -label {Thickness} -menu $mt
		foreach lnwidth {1 2 4 6} {
		    $mt add radio -label $lnwidth   \
		      -variable ${ns}::popupVars(-width) \
		      -command [list ::CanvasUtils::ItemConfigure $w current   \
		      -width $lnwidth]
		}
		$m add command -label {Fill Color...} -command   \
		  [list ::CanvasUtils::SetItemColorDialog $w current -fill]
		$m add command -label {Outline Color...} -command   \
		  [list ::CanvasUtils::SetItemColorDialog $w current -outline]
		$m add command -label {Inspect...}  \
		  -command [list ::ItemInspector::ItemInspector $w current]
		
		# This one is needed on the mac so the menu is built before
		# it is posted.
		update idletasks
	    }
	    
	    # Set present values for this particular item.
	    set popupVars(-width) [expr int([$w itemcget $id -width])]
	    
	    # Post popup menu.
	    tk_popup $m [expr int($x) - 10] [expr int($y) - 10]

[MACTCL] tk_popup

[Sebastian L. <Seb...@we...>]

The tk_popup command does not work on my mac.
Are there know limitations?
Does anybody have a working example?
_______________________________________________________________________
1.000.000 DM gewinnen - kostenlos tippen - http://millionenklick.web.de
Ih...@we..., 8MB Speicher, Verschluesselung - http://freemail.web.de