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

Re: [MACTCL] Aqua TK script problems

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

This was a bug in how the output channels are set up when using the Tk 
console...  It is fixed in the current sources on the macosx branch.  
You can work around it by just using "puts" rather than "puts stdout", 
or get the new sources and build them.  I will do another build sometime 
soon, but I want to figure out extension building issues, and I haven't 
had much time to work on this for the past couple of weeks...

Jim


On Saturday, November 10, 2001, at 11:27  PM, Tim Lahey wrote:

> Hi,
>
> I've installed the Aqua TK snapshot from sourceforge, and I'm
> trying to get the tkbibtex script to work. When I source the
> script file, I get the following error on the console.
>
> bgerror failed to handle background error.
>     Original error: can not find channel named "stdout"
>     Error in bgerror: invalid command name "sting"
>
> tkbibtex can be found at:
>
> http://www.cat.csiro.au/cmst/staff/pic/tkbibtex.html
>
> Any thoughts or suggestions ?
>
> Thanks,
>
> Tim Lahey
>
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham                                                           
ji...@ap...
Developer Tools - gdb

[MACTCL] Aqua TK script problems

[Tim L. <tj...@cg...>]

Hi,

I've installed the Aqua TK snapshot from sourceforge, and I'm
trying to get the tkbibtex script to work. When I source the
script file, I get the following error on the console.

bgerror failed to handle background error.
     Original error: can not find channel named "stdout"
     Error in bgerror: invalid command name "sting"

tkbibtex can be found at:

http://www.cat.csiro.au/cmst/staff/pic/tkbibtex.html

Any thoughts or suggestions ?

Thanks,

Tim Lahey

Re: [MACTCL] HINTS PLS -- tcl on MacOX X

[Franc B. <br...@cb...>]

Many thanks Jim,

I may also give Tk build a try as per your suggestion and will let you know ...

My experience is not at the level of "resource" commands but I may pitch-in
to test something if I can follow the instructions ...


Thanks again ... Franc


At 9:18 AM -0800 09/11/2001, Jim Ingham wrote:
>Franc,
>
>First off, if you have plain Tcl scripts that will run in Tcl 8.3, then
>the simplest route is to just use the installed Tcl.  The standard user
>install of MacOS X has a version of the Unix Tcl, and pretty much
>everything that will work on any other Tcl will work here.  Just fire up
>Terminal.app, run tclsh, and you are all set...
>
>If you want to run Tk scripts, or need Tcl 8.4, then probably the
>simplest thing to do is get the MacOSX Tk binaries that I put up on the
>tcl.sourceforge.net site.  If you cd to your home directory and untar
>the gzipped tar file there, you will get the Tcl & Tk libraries in
>~/Library/Frameworks, and the Wish Shell.app in ~/Applications.
>Double-click on Wish Shell.app, and you will get a console window just
>like on Classic MacTk, and you can type commands at that, or use the
>Source menu item to source them in.
>
>The other option is to get XFree86, and XDarwin, and then either get or
>build the X11 version of Tcl/Tk.  This is a lot more work, and unless
>you have some other need for X11 stuff, or if you need the "send"
>command, probably not worth the effort.  Also, I would rather people
>whack on the native port, since in the long run this is a better way to
>run Tcl/Tk apps on X, and I would appreciate some help finding bugs,
>performance issues, etc of the native version.
>
>If you need the "resource" commands, or any of the other Mac specific
>Tcl/Tk commands, then you might consider pitching in.  I haven't gotten
>these ported to X yet, but there is a macosx folder in the tcl directory
>on sourceforge, and anyone who wants to help getting missing stuff moved
>from MacTcl to MacOSX Tcl will earn my gratitude.  Daniel & I talked
>about taking some of the very Mac specific stuff and putting it in a
>library that gets loaded into Tcl by default, rather than built straight
>in.  But this is a later concern.
>
>Hope this helps,
>
>Jim
>
>On Friday, November 9, 2001, at 06:07  AM, Franc Brglez wrote:
>
>> I'll be installing MacOX X on my Titanium Powerbook this weekend and
>> would
>> like to give at  least my own tcl scripts a dry run ...
>>
>> Any hints and suggestions on "installing tcl (which one)" if not entire
>> tcl
>> tcltk under MacOX X will be most timely and appreciated.
>>
>> Many thansk ... Franc Brglez
>>
>> _______________________________________________
>> Tcl-mac mailing list
>> Tc...@li...
>> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>>
>_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
>Jim Ingham
>ji...@ap...
>Developer Tools - gdb
>
>
>_______________________________________________
>Tcl-mac mailing list
>Tc...@li...
>https://lists.sourceforge.net/lists/listinfo/tcl-mac

Re: [MACTCL] Anybody home?

[Chris S. <ka...@ma...>]

Thanks Jim and everybody else that reassured there are in fact other people
out there working on this stuff:) I appreciate the help!

- Chris

on 11/9/01 12:33 PM, Jim Ingham at ji...@ap... wrote:

> Chris,
> 
> The responses on this list go up and down based on how busy people are.
> Usually you get a faster response, but this must be a 'triple down'
> period - for those old enough to remember biorhythms...  You should ask
> Mac specific questions here, you will usually get a faster response on
> these, but you might also want to ask generic Tcl/Tk questions on
> comp.lang.tcl.  There is a much larger audience there, and for general
> questions you will get helpful answers there from a broader range of
> folks.
> 
> Anyway, if you are developing a Tcl script the best way to run it is to
> fire up the Wish Shell application, and use the File->Source menu item,
> navigate to your script, and select it.  Wish has two windows
> originally, one is the console window, and one the Tk main (".")
> window.  You can type tcl/tk commands straight at the console as well,
> which is useful both when you are playing around and for debugging your
> scripts.
> 
> Drag & Drop of scripts can be made to work, but it is not turned on by
> default because it is not clear what should happen when a second script
> is dropped on the same running Tcl application.
> 
> On resources: there are a bunch of good books on Tcl, some of them
> discuss the Mac.  Brent Welch's book Practical Programming in Tcl/Tk is
> very good, as is the Harrison/McLennan book Effective Tcl.  There are a
> few more recent ones as well, but I haven't really looked at them.
> There is a FAQ on Mac specific Tcl stuff which should be at:
> 
> http://tcl.activestate.com:8002/software/mac/macFAQ.html
> 
> but it seems to have gotten lost in the move to ActiveState.  I
> submitted a bug to their webmaster about this.  It hasn't been worked on
> in a while, but everything there is pretty much correct.
> 
> Enjoy,
> 
> Jim
> 
> 
> On Friday, November 9, 2001, at 06:09  AM, Chris Scott wrote:
> 
>> Anybody else on this list? I previously posted a question about running
>> scripts, and where to start with tcl/tk and got not a single response.
>> If no
>> one responds to posts, I'll stop posting. But can anyone recommend a
>> list
>> where I can ask questions and get some help if I need it? Thanks.
>> 
>> - Chris
>> 
>> 
>> _______________________________________________
>> Tcl-mac mailing list
>> Tc...@li...
>> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>> 
> _-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
> Jim Ingham       
> ji...@ap...
> Developer Tools - gdb
> 
> 
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac

Re: [MACTCL] Anybody home?

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

Chris,

The responses on this list go up and down based on how busy people are.  
Usually you get a faster response, but this must be a 'triple down' 
period - for those old enough to remember biorhythms...  You should ask 
Mac specific questions here, you will usually get a faster response on 
these, but you might also want to ask generic Tcl/Tk questions on 
comp.lang.tcl.  There is a much larger audience there, and for general 
questions you will get helpful answers there from a broader range of 
folks.

Anyway, if you are developing a Tcl script the best way to run it is to 
fire up the Wish Shell application, and use the File->Source menu item, 
navigate to your script, and select it.  Wish has two windows 
originally, one is the console window, and one the Tk main (".") 
window.  You can type tcl/tk commands straight at the console as well, 
which is useful both when you are playing around and for debugging your 
scripts.

Drag & Drop of scripts can be made to work, but it is not turned on by 
default because it is not clear what should happen when a second script 
is dropped on the same running Tcl application.

On resources: there are a bunch of good books on Tcl, some of them 
discuss the Mac.  Brent Welch's book Practical Programming in Tcl/Tk is 
very good, as is the Harrison/McLennan book Effective Tcl.  There are a 
few more recent ones as well, but I haven't really looked at them.  
There is a FAQ on Mac specific Tcl stuff which should be at:

http://tcl.activestate.com:8002/software/mac/macFAQ.html

but it seems to have gotten lost in the move to ActiveState.  I 
submitted a bug to their webmaster about this.  It hasn't been worked on 
in a while, but everything there is pretty much correct.

Enjoy,

Jim


On Friday, November 9, 2001, at 06:09  AM, Chris Scott wrote:

> Anybody else on this list? I previously posted a question about running
> scripts, and where to start with tcl/tk and got not a single response. 
> If no
> one responds to posts, I'll stop posting. But can anyone recommend a 
> list
> where I can ask questions and get some help if I need it? Thanks.
>
> - Chris
>
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham                                                           
ji...@ap...
Developer Tools - gdb

Re: [MACTCL] HINTS PLS -- tcl on MacOX X

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

Franc,

First off, if you have plain Tcl scripts that will run in Tcl 8.3, then 
the simplest route is to just use the installed Tcl.  The standard user 
install of MacOS X has a version of the Unix Tcl, and pretty much 
everything that will work on any other Tcl will work here.  Just fire up 
Terminal.app, run tclsh, and you are all set...

If you want to run Tk scripts, or need Tcl 8.4, then probably the 
simplest thing to do is get the MacOSX Tk binaries that I put up on the 
tcl.sourceforge.net site.  If you cd to your home directory and untar 
the gzipped tar file there, you will get the Tcl & Tk libraries in 
~/Library/Frameworks, and the Wish Shell.app in ~/Applications.  
Double-click on Wish Shell.app, and you will get a console window just 
like on Classic MacTk, and you can type commands at that, or use the 
Source menu item to source them in.

The other option is to get XFree86, and XDarwin, and then either get or 
build the X11 version of Tcl/Tk.  This is a lot more work, and unless 
you have some other need for X11 stuff, or if you need the "send" 
command, probably not worth the effort.  Also, I would rather people 
whack on the native port, since in the long run this is a better way to 
run Tcl/Tk apps on X, and I would appreciate some help finding bugs, 
performance issues, etc of the native version.

If you need the "resource" commands, or any of the other Mac specific 
Tcl/Tk commands, then you might consider pitching in.  I haven't gotten 
these ported to X yet, but there is a macosx folder in the tcl directory 
on sourceforge, and anyone who wants to help getting missing stuff moved 
from MacTcl to MacOSX Tcl will earn my gratitude.  Daniel & I talked 
about taking some of the very Mac specific stuff and putting it in a 
library that gets loaded into Tcl by default, rather than built straight 
in.  But this is a later concern.

Hope this helps,

Jim

On Friday, November 9, 2001, at 06:07  AM, Franc Brglez wrote:

> I'll be installing MacOX X on my Titanium Powerbook this weekend and 
> would
> like to give at  least my own tcl scripts a dry run ...
>
> Any hints and suggestions on "installing tcl (which one)" if not entire 
> tcl
> tcltk under MacOX X will be most timely and appreciated.
>
> Many thansk ... Franc Brglez
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham                                                           
ji...@ap...
Developer Tools - gdb

[MACTCL] Anybody home?

[Chris S. <ka...@ma...>]

Anybody else on this list? I previously posted a question about running
scripts, and where to start with tcl/tk and got not a single response. If no
one responds to posts, I'll stop posting. But can anyone recommend a list
where I can ask questions and get some help if I need it? Thanks.

- Chris

[MACTCL] HINTS PLS -- tcl on MacOX X

[Franc B. <br...@cb...>]

I'll be installing MacOX X on my Titanium Powerbook this weekend and would
like to give at  least my own tcl scripts a dry run ...

Any hints and suggestions on "installing tcl (which one)" if not entire tcl
tcltk under MacOX X will be most timely and appreciated.

Many thansk ... Franc Brglez

Re: [MACTCL] RE: Problems with Mac TCL?

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

Benjamin,

On Thursday, November 8, 2001, at 04:48  AM, Schollnick, Benjamin wrote:

> Jim,
>
> 	Thanks for the quick reply....
>
> 	This does explain the behavior... I'll have to point this
> 	out to Jack....

Okay.

>
> 	One small point.... It appears on the PC, that the TK library
> 	can be loaded multiple times (at least via python).... So if your
> 	trying to feature match the PC version, this is a small
> difference...

If you mean loaded & unloaded & loaded again, this should work, and 
could be made to work.  My guess, however, is if you need it you will 
have to make it work yourself, since the resources to work on MacTk are 
limited, and this is a pretty esoteric requirement...

>
> 	Now, I also didn't check the Documentation for the library, but
> 	is this limitation documented anywhere....

I doubt the finalization stuff is well documented outside the code.  But 
the rest of the Tk docs usually get shipped in HTML form with the 
binaries.  If not, they are also available on the tcl.sourceforge.net 
site.


>
> 	Either way, thanks for the assist....
>

No prob...

Jim

> 		- Benjamin
>
> -----Original Message-----
> From: Jim Ingham [mailto:ji...@ap...]
> Sent: Wednesday, November 07, 2001 2:39 PM
> To: Schollnick, Benjamin
> Cc: 'tc...@li...'
> Subject: Re: [MACTCL] RE: Problems with Mac TCL?
>
>
> Benjamin,
>
> First off, Tcl/Tk is not designed to allow you to load two independent
> copies of Tk into an application.  There is global state in the
> libraries that will cause conflicts.  So you have to make sure that you
> unload the first copy completely before you try to load the second
> copy.  You can create two tcl interpreters, both running Tk, but the way
> you are supposed to do that is to create one interpreter, and then load
> Tk into the second interpreter by running "package require Tk" in the
> second interpreter.  This is, for example, how the console window in
> MacTk works.  But we never intended you to be able to actually load the
> Tk library twice.
>
> Theoretically, you could load Tk, then unload it. However, I never
> worked very hard to make sure that you could unload Tcl/Tk from an app,
> and then reload it again cleanly.  There are finalization routines for
> all the subsystems, but I would have no problem believing they don't
> clean up everything.  The only things I really cared about was
> non-shared state, and resources that the system would not reap when the
> process exited.  You could probably fix this - since the mechanism to
> handle finalization is present.
>
> Hope this helps.
>
> Jim
>
> On Wednesday, November 7, 2001, at 08:28  AM, Schollnick, Benjamin 
> wrote:
>
>> Slight apologies...
>>
>> 	As soon as I posted that previous message, I almost figured the
>> issue out.
>> 	Instead, I realized I had fallen for a Red Herring (Tm).
>>
>> 	Is there any reason that two Tcl/Tk initializations would be a
>> problem
>> 	on the Macintosh?
>>
>> 	The core of the issue is that I had initialized Tk/Tcl, and then
>> 	the Wizard package attempted to Initialize Tk/Tcl  again...
>> 	Which caused the panic message...
>>
>> 	So, I have a better definition of the issue, but still suspect it's
>> a
>> 	Tcl Library issue?  Can anyone confirm this?
>>
>> 			- Benjamin
>>
>> 	 -----Original Message-----
>> 	From: 	Schollnick, Benjamin
>> 	Sent:	Wednesday, November 07, 2001 11:16 AM
>> 	To:	'tc...@li...'
>> 	Subject:	Problems with Mac TCL?
>>
>> 	Folks,
>>
>> 		Even though I'm using Tcl via Python, it appears this maybe
>> 		an implementation issue from Tcl...
>>
>> 		Now, please keep in mind that by no means am I huge
>> Tkinter/Tcl guru,
>> 		I'm not....
>>
>> 		But never the less, here's what I'm seeing...
>>
>> 			"Menu ID 256 is already in use!  Fatal Python Error:
>> Tcl/Tk Panic"
>>
>> 		Which from my investigation, means that Tcl/TK has
>> panicked...The Menu ID
>> 		appears also to be hardcoded somewhere?  Presumably from
>> Tcl/Tk?
>>
>> 		The pseudo code is as follows:
>>
>> 		* Initialize Tk
>> 		* Create RootWindow object
>> 		* Withdraw the Tk TopWindow
>> 		* Display AskYesNo dialog
>> 			(If Yes) * display FileOpen Dialog
>>
>> 		* Start "Wizard"	(Which also appears to Withdraw the
>> Tk TopWindow)
>>
>> 		Wizard is a python based MS Windows look-alike Wizard GUI
>> package...
>>
>> 		If I don't withdraw the Tk Top Window, everything appears to
>> work fine...
>>
>> 		If I do withdraw the Tk Top Window, I get the panic
>> message....
>> 		I'm stumped, I've spoken to people in the Python groups
>> (lists & usenet),
>> 		with little luck... As I mentioned it appears to potentially
>> be a Tk/Tcl issue...
>>
>> 		Any suggestions for investigation?
>>
>> 		My first guess is that the dual TopWindow Withdraws maybe a
>> issue but
>> 		I'm not sure....
>>
>> 				- Benjamin
>>
>> _______________________________________________
>> 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] RE: Problems with Mac TCL?

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

Jim,

	Thanks for the quick reply....

	This does explain the behavior... I'll have to point this
	out to Jack.... 

	One small point.... It appears on the PC, that the TK library
	can be loaded multiple times (at least via python).... So if your
	trying to feature match the PC version, this is a small
difference...

	Now, I also didn't check the Documentation for the library, but
	is this limitation documented anywhere....

	Either way, thanks for the assist.... 

		- Benjamin

-----Original Message-----
From: Jim Ingham [mailto:ji...@ap...]
Sent: Wednesday, November 07, 2001 2:39 PM
To: Schollnick, Benjamin
Cc: 'tc...@li...'
Subject: Re: [MACTCL] RE: Problems with Mac TCL?


Benjamin,

First off, Tcl/Tk is not designed to allow you to load two independent 
copies of Tk into an application.  There is global state in the 
libraries that will cause conflicts.  So you have to make sure that you 
unload the first copy completely before you try to load the second 
copy.  You can create two tcl interpreters, both running Tk, but the way 
you are supposed to do that is to create one interpreter, and then load 
Tk into the second interpreter by running "package require Tk" in the 
second interpreter.  This is, for example, how the console window in 
MacTk works.  But we never intended you to be able to actually load the 
Tk library twice.

Theoretically, you could load Tk, then unload it. However, I never 
worked very hard to make sure that you could unload Tcl/Tk from an app, 
and then reload it again cleanly.  There are finalization routines for 
all the subsystems, but I would have no problem believing they don't 
clean up everything.  The only things I really cared about was 
non-shared state, and resources that the system would not reap when the 
process exited.  You could probably fix this - since the mechanism to 
handle finalization is present.

Hope this helps.

Jim

On Wednesday, November 7, 2001, at 08:28  AM, Schollnick, Benjamin wrote:

> Slight apologies...
>
> 	As soon as I posted that previous message, I almost figured the
> issue out.
> 	Instead, I realized I had fallen for a Red Herring (Tm).
>
> 	Is there any reason that two Tcl/Tk initializations would be a
> problem
> 	on the Macintosh?
>
> 	The core of the issue is that I had initialized Tk/Tcl, and then
> 	the Wizard package attempted to Initialize Tk/Tcl  again...
> 	Which caused the panic message...
>
> 	So, I have a better definition of the issue, but still suspect it's
> a
> 	Tcl Library issue?  Can anyone confirm this?
>
> 			- Benjamin
>
> 	 -----Original Message-----
> 	From: 	Schollnick, Benjamin
> 	Sent:	Wednesday, November 07, 2001 11:16 AM
> 	To:	'tc...@li...'
> 	Subject:	Problems with Mac TCL?
>
> 	Folks,
>
> 		Even though I'm using Tcl via Python, it appears this maybe
> 		an implementation issue from Tcl...
>
> 		Now, please keep in mind that by no means am I huge
> Tkinter/Tcl guru,
> 		I'm not....
>
> 		But never the less, here's what I'm seeing...
>
> 			"Menu ID 256 is already in use!  Fatal Python Error:
> Tcl/Tk Panic"
>
> 		Which from my investigation, means that Tcl/TK has
> panicked...The Menu ID
> 		appears also to be hardcoded somewhere?  Presumably from
> Tcl/Tk?
>
> 		The pseudo code is as follows:
>
> 		* Initialize Tk
> 		* Create RootWindow object
> 		* Withdraw the Tk TopWindow
> 		* Display AskYesNo dialog
> 			(If Yes) * display FileOpen Dialog
>
> 		* Start "Wizard"	(Which also appears to Withdraw the
> Tk TopWindow)
>
> 		Wizard is a python based MS Windows look-alike Wizard GUI
> package...
>
> 		If I don't withdraw the Tk Top Window, everything appears to
> work fine...
>
> 		If I do withdraw the Tk Top Window, I get the panic
> message....
> 		I'm stumped, I've spoken to people in the Python groups
> (lists & usenet),
> 		with little luck... As I mentioned it appears to potentially
> be a Tk/Tcl issue...
>
> 		Any suggestions for investigation?
>
> 		My first guess is that the dual TopWindow Withdraws maybe a
> issue but
> 		I'm not sure....
>
> 				- Benjamin
>
> _______________________________________________
> 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] RE: Problems with Mac TCL?

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

Benjamin,

First off, Tcl/Tk is not designed to allow you to load two independent 
copies of Tk into an application.  There is global state in the 
libraries that will cause conflicts.  So you have to make sure that you 
unload the first copy completely before you try to load the second 
copy.  You can create two tcl interpreters, both running Tk, but the way 
you are supposed to do that is to create one interpreter, and then load 
Tk into the second interpreter by running "package require Tk" in the 
second interpreter.  This is, for example, how the console window in 
MacTk works.  But we never intended you to be able to actually load the 
Tk library twice.

Theoretically, you could load Tk, then unload it. However, I never 
worked very hard to make sure that you could unload Tcl/Tk from an app, 
and then reload it again cleanly.  There are finalization routines for 
all the subsystems, but I would have no problem believing they don't 
clean up everything.  The only things I really cared about was 
non-shared state, and resources that the system would not reap when the 
process exited.  You could probably fix this - since the mechanism to 
handle finalization is present.

Hope this helps.

Jim

On Wednesday, November 7, 2001, at 08:28  AM, Schollnick, Benjamin wrote:

> Slight apologies...
>
> 	As soon as I posted that previous message, I almost figured the
> issue out.
> 	Instead, I realized I had fallen for a Red Herring (Tm).
>
> 	Is there any reason that two Tcl/Tk initializations would be a
> problem
> 	on the Macintosh?
>
> 	The core of the issue is that I had initialized Tk/Tcl, and then
> 	the Wizard package attempted to Initialize Tk/Tcl  again...
> 	Which caused the panic message...
>
> 	So, I have a better definition of the issue, but still suspect it's
> a
> 	Tcl Library issue?  Can anyone confirm this?
>
> 			- Benjamin
>
> 	 -----Original Message-----
> 	From: 	Schollnick, Benjamin
> 	Sent:	Wednesday, November 07, 2001 11:16 AM
> 	To:	'tc...@li...'
> 	Subject:	Problems with Mac TCL?
>
> 	Folks,
>
> 		Even though I'm using Tcl via Python, it appears this maybe
> 		an implementation issue from Tcl...
>
> 		Now, please keep in mind that by no means am I huge
> Tkinter/Tcl guru,
> 		I'm not....
>
> 		But never the less, here's what I'm seeing...
>
> 			"Menu ID 256 is already in use!  Fatal Python Error:
> Tcl/Tk Panic"
>
> 		Which from my investigation, means that Tcl/TK has
> panicked...The Menu ID
> 		appears also to be hardcoded somewhere?  Presumably from
> Tcl/Tk?
>
> 		The pseudo code is as follows:
>
> 		* Initialize Tk
> 		* Create RootWindow object
> 		* Withdraw the Tk TopWindow
> 		* Display AskYesNo dialog
> 			(If Yes) * display FileOpen Dialog
>
> 		* Start "Wizard"	(Which also appears to Withdraw the
> Tk TopWindow)
>
> 		Wizard is a python based MS Windows look-alike Wizard GUI
> package...
>
> 		If I don't withdraw the Tk Top Window, everything appears to
> work fine...
>
> 		If I do withdraw the Tk Top Window, I get the panic
> message....
> 		I'm stumped, I've spoken to people in the Python groups
> (lists & usenet),
> 		with little luck... As I mentioned it appears to potentially
> be a Tk/Tcl issue...
>
> 		Any suggestions for investigation?
>
> 		My first guess is that the dual TopWindow Withdraws maybe a
> issue but
> 		I'm not sure....
>
> 				- Benjamin
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] Running scripts on a mac

[Chris S. <ka...@ma...>]

Complete newbie question, please bear with me. Once I've written a tcl
script in a word processor (using BBEdit) how do I go about executing it? I
tried dragging it over the tcl shell icon, but that doesn't work.

And as long as I'm revealing the depth of my ignorance, any suggestions on a
good way to get started learning tcl/tk? Tutorials, books, on-line
references - anything is appreciated. Thanks, all.

- Chris

[MACTCL] RE: Problems with Mac TCL?

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

Slight apologies...

	As soon as I posted that previous message, I almost figured the
issue out.
	Instead, I realized I had fallen for a Red Herring (Tm).

	Is there any reason that two Tcl/Tk initializations would be a
problem 
	on the Macintosh?

	The core of the issue is that I had initialized Tk/Tcl, and then
	the Wizard package attempted to Initialize Tk/Tcl  again...
	Which caused the panic message...

	So, I have a better definition of the issue, but still suspect it's
a
	Tcl Library issue?  Can anyone confirm this?

			- Benjamin

	 -----Original Message-----
	From: 	Schollnick, Benjamin  
	Sent:	Wednesday, November 07, 2001 11:16 AM
	To:	'tc...@li...'
	Subject:	Problems with Mac TCL?

	Folks,

		Even though I'm using Tcl via Python, it appears this maybe
		an implementation issue from Tcl...

		Now, please keep in mind that by no means am I huge
Tkinter/Tcl guru,
		I'm not....

		But never the less, here's what I'm seeing...

			"Menu ID 256 is already in use!  Fatal Python Error:
Tcl/Tk Panic"

		Which from my investigation, means that Tcl/TK has
panicked...The Menu ID
		appears also to be hardcoded somewhere?  Presumably from
Tcl/Tk?

		The pseudo code is as follows:

		* Initialize Tk
		* Create RootWindow object
		* Withdraw the Tk TopWindow
		* Display AskYesNo dialog
			(If Yes) * display FileOpen Dialog

		* Start "Wizard"	(Which also appears to Withdraw the
Tk TopWindow)

		Wizard is a python based MS Windows look-alike Wizard GUI
package...

		If I don't withdraw the Tk Top Window, everything appears to
work fine...

		If I do withdraw the Tk Top Window, I get the panic
message....
		I'm stumped, I've spoken to people in the Python groups
(lists & usenet),
		with little luck... As I mentioned it appears to potentially
be a Tk/Tcl issue...

		Any suggestions for investigation?

		My first guess is that the dual TopWindow Withdraws maybe a
issue but
		I'm not sure....

				- Benjamin

[MACTCL] Problems with Mac TCL?

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

Folks,

	Even though I'm using Tcl via Python, it appears this maybe
	an implementation issue from Tcl...

	Now, please keep in mind that by no means am I huge Tkinter/Tcl
guru,
	I'm not....

	But never the less, here's what I'm seeing...

		"Menu ID 256 is already in use!  Fatal Python Error: Tcl/Tk
Panic"

	Which from my investigation, means that Tcl/TK has panicked...The
Menu ID
	appears also to be hardcoded somewhere?  Presumably from Tcl/Tk?

	The pseudo code is as follows:

	* Initialize Tk
	* Create RootWindow object
	* Withdraw the Tk TopWindow
	* Display AskYesNo dialog
		(If Yes) * display FileOpen Dialog

	* Start "Wizard"	(Which also appears to Withdraw the Tk
TopWindow)

	Wizard is a python based MS Windows look-alike Wizard GUI package...

	If I don't withdraw the Tk Top Window, everything appears to work
fine...

	If I do withdraw the Tk Top Window, I get the panic message....
	I'm stumped, I've spoken to people in the Python groups (lists &
usenet),
	with little luck... As I mentioned it appears to potentially be a
Tk/Tcl issue...

	Any suggestions for investigation?

	My first guess is that the dual TopWindow Withdraws maybe a issue
but
	I'm not sure....

			- Benjamin

RE: [MACTCL] [MACTCL BUG] 8.3.2 Application Error 25

[Ralph H. <rh...@bm...>]

> If you have access to CW Pro6, compiling your own Tcl/Tk will take 
> care  of the problem, as you will integrate stock MW runtime 
> libraries which don't have the 8.1 problem.

Nope, I don't have CW - my main job is embedded systems, so I don't even have a C compiler for my PC.

> otherwise replacing 'MW_MSL.PPC.Shlb' in 8.3.4 by the copy that comes 
> with 8.3.3 should also fix the problem, note that TclShell, 
> TclBOAShell, Wish, 'Drag & Drop Tclets' and 'Widget Demos' all have 
> this library embedded, so you will need to use a tool like 
> Fragmalyzer, Resorcerer or Apple's free MPW MergeFragment to replace 
> it. (or just use 'Simple Tk (sh-ppc)' instead of Wish etc)

I've tried this experiment in 8.3.3, and as long as I'm not streaming
text to the console, it appears to run forever. This has given
me new hope so I'm back to trying to get my Mindstorms
bootloader working on the Mac again :-)

> Please keep me posted on your progress with this, I'm not sure yet 
> what to do for the next release, yours is the only complaint I've 
> gotten so for, so most people seem to use post 8.1 OS versions.

Since 8.3.3 works, maybe the next release can use those libs again. On
the other hand, I might just upgrade to OS8.6 and avoid the problem
altogether.

For all the harping against Win machines, these Macs are pretty finicky
too - especially now that there are no more serial ports!

> Maybe I'll specify that 8.6 is needed for the distribution in the 
> future (compiling your own will always be an option for pre 8.6 
> users)? what are people's thoughts on this?

Compiling our own is not an option for most users. Most folks won;t
have CW Pro6 lying around :-)

> I find that SIOUX-WASTE is very nice to have in TclShell, esp. when 
> running apps such as tcltest which can produce a lot of output. it 
> also uses temp. mem. for its buffers which reduces memory problems in 
> tcl...

I'll look into this some more. Thanks for all your help so far...

Cheers, Ralph Hempel

RE: [MACTCL] [MACTCL BUG] 8.3.2 Application Error 25

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

At 8:58 -0500 on 2/11/01, Ralph Hempel wrote:

>I can't run 8.3.4 on my MacOS8.1 due to the Font library problem
>I reported earlier :-(

I'm now pretty sure the problem is due to my turning on the use of 
the WASTE library in MSL, this removes the TclShell 32K scrollback 
text buffer limitation but apparently needs library routines that are 
not available on older systems. (you can tell if you are using WASTE 
by looking at the 'About ...' Menu in TclShell)

>I can wait until the next patch release of the binaries....

If you have access to CW Pro6, compiling your own Tcl/Tk will take 
care  of the problem, as you will integrate stock MW runtime 
libraries which don't have the 8.1 problem.

otherwise replacing 'MW_MSL.PPC.Shlb' in 8.3.4 by the copy that comes 
with 8.3.3 should also fix the problem, note that TclShell, 
TclBOAShell, Wish, 'Drag & Drop Tclets' and 'Widget Demos' all have 
this library embedded, so you will need to use a tool like 
Fragmalyzer, Resorcerer or Apple's free MPW MergeFragment to replace 
it. (or just use 'Simple Tk (sh-ppc)' instead of Wish etc)

Please keep me posted on your progress with this, I'm not sure yet 
what to do for the next release, yours is the only complaint I've 
gotten so for, so most people seem to use post 8.1 OS versions.

Maybe I'll specify that 8.6 is needed for the distribution in the 
future (compiling your own will always be an option for pre 8.6 
users)? what are people's thoughts on this?
I find that SIOUX-WASTE is very nice to have in TclShell, esp. when 
running apps such as tcltest which can produce a lot of output. it 
also uses temp. mem. for its buffers which reduces memory problems in 
tcl...

Cheers,

Daniel
-- 
** Daniel A. Steffen          **  "And now to something completely
** Department of Mathematics  **   different"    Monty Python
** Macquarie University       ** <mailto:st...@ma...>
** NSW 2109 Australia         ** <http://www.maths.mq.edu.au/~steffen/>

[MACTCL] ANNOUNCE: New Tcl mailings lists archive at ASPN

[Jeff H. <Je...@Ac...>]

ActiveState has added a section of Tcl mailing lists with back
archives to their ASPN site.  The available lists are noted at:

    http://aspn.activestate.com/ASPN/Tcl/Mail

all ASPN lists are here:

   http://aspn.activestate.com/ASPN/Mail/

and example of the presentation is here (very slick):

   http://aspn.activestate.com/ASPN/Mail/Browse/Threaded/tcl-core

We believe this is especially well timed given the uncertainty
of GeoCrawler (presumably being absorbed by SourceForge directly).
Also, this has nice searching capabilities.  If you are an ASPN
member (ASPN Open is a free subscription), you can have a
customized front page which tracks the latest messages in any
available list without have to be subscribed.

We hope you find this to be a valuable resource.  

Also note that we have recently created an
	ActiveTcl-at-listserv.ActiveState.com
mailing list that you can join for discussions related to
ActiveTcl features and development.

-- 
  Jeff Hobbs                     The Tcl Guy
  Senior Developer               http://www.ActiveState.com/
        Tcl Support and Productivity Solutions

RE: [MACTCL] [MACTCL BUG] 8.3.2 Application Error 25

[Ralph H. <rh...@bm...>]

> >I'm still getting the ApllicationError 25 when I call
> >the AppleScript package many times....this time I've
> >changed the script so it runs on any Mac.

> I've just executed your script in TclTest 8.3.4 and it ran for 3000 
> iterations without a problem, the only increase in memory use I could 
> detect was due to the console window buffer (total memory use of 
> TclTest was 3.1MB after the 3000 iterations)
> 
> maybe this bug was fixed with my memory code improvements in 8.3.3 ?

My Tcl 8.3.2 craps out after about 2500 iterations, and I never thought
of the buffer memory!

I can't run 8.3.4 on my MacOS8.1 due to the Font library problem
I reported earlier :-(

I can wait until the next patch release of the binaries....

Cheers, Ralph Hempel

Re: [MACTCL] [MACTCL BUG] 8.3.2 Application Error 25

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

At 11:37 -0500 on 1/11/01, Ralph Hempel wrote:

>I'm still getting the ApllicationError 25 when I call
>the AppleScript package many times....this time I've
>changed the script so it runs on any Mac.
>
>Even if I compile the AppleScript and run it from the
>handle returned by compile, the problem is the same, so
>I'm suspecting a memory leak in the AppleScript mechanism
>itself.
>
>The minimal script that will duplicate the problem is at the end
>of the message.
>
>It's not meant to be practical, just illustrates a timed procedure firing
>off on a regular basis. If I comment out the call to the AppleScript
>procedure, then the application runs fine. I suspect a memory leak
>somewhere in tclAppleScript....

I've just executed your script in TclTest 8.3.4 and it ran for 3000 
iterations without a problem, the only increase in memory use I could 
detect was due to the console window buffer (total memory use of 
TclTest was 3.1MB after the 3000 iterations)

maybe this bug was fixed with my memory code improvements in 8.3.3 ?

Cheers,

Daniel
-- 
** Daniel A. Steffen          **  "And now to something completely
** Department of Mathematics  **   different"    Monty Python
** Macquarie University       ** <mailto:st...@ma...>
** NSW 2109 Australia         ** <http://www.maths.mq.edu.au/~steffen/>

[MACTCL] [MACTCL BUG] 8.3.2 Application Error 25

[Ralph H. <rh...@bm...>]

I'm still getting the ApllicationError 25 when I call
the AppleScript package many times....this time I've
changed the script so it runs on any Mac.

Even if I compile the AppleScript and run it from the
handle returned by compile, the problem is the same, so
I'm suspecting a memory leak in the AppleScript mechanism
itself.

The minimal script that will duplicate the problem is at the end
of the message.

It's not meant to be practical, just illustrates a timed procedure firing
off on a regular basis. If I comment out the call to the AppleScript
procedure, then the application runs fine. I suspect a memory leak
somewhere in tclAppleScript....

Hope this bug report is useful...

-------------------------------------------------------------------------------
package require Tclapplescript

set rcvHandlerAID ""
set rcvEvent      ""

proc rcvHandler { } {
  global rcvHandlerAID
  global rcvEvent
  
  set inData [AppleScript run silly]

  puts "Reading in handler $rcvHandlerAID $inData"
  
  set rcvEvent RXDONE
}

AppleScript compile -name silly "current date"

set rcvHandlerAID [after 20 {rcvHandler}]

while { 0 == [regexp {TIMEOUT|EOF} $rcvEvent] } {
   vwait rcvEvent
   puts "Got event $rcvEvent"
   set rcvHandlerAID [after 20 {rcvHandler}]
}
-------------------------------------------------------------------------------

RE: [MACTCL] 8.3.4 problem with MacOS 8.1

[Ralph H. <rh...@bm...>]

> If you still have your 8.3.3 install, could you try to run one of the 
> unmerged 8.3.4 binaries - e.g. 'Simple Tcl (sh-ppc)' - in a folder 
> with a copy of the '(Support Libraries)' folder from 8.3.3 present?

Daniel,

I moved a copy the 8.3.4 shell into the folder with my 8.3.2 installation
and launched it from there - it worked fine.

Clearly, there is a difference in the libraries that ship with
8.3.4 vs 8.3.2, but I'm way out of my depth here.

Hope this helps...

Cheers, Ralph

RE: [MACTCL] 8.3.4 problem with MacOS 8.1

[Ralph H. <rh...@bm...>]

> >I just upgraded my MacTcl to the new 8.3.4 binaries
> >and it spits up the following error when I launch
> >wish or the tcl shell under MacOS 8.1:
> >
> >The application "Wish" could not be opened because
> >"InterfaceLib--FetchFontInfo" could not be found
> >
> >The 8.3.3 binaries worked fine....
> 
> Ralph,
> 
> I'm puzzled by this, as the projects have not changed w.r.t libraries 
> since 8.3.3. I have updated the Apple Universal Interfaces to what 
> comes with the latest CarbonLib SDK however so the problem could 
> originate there...

You're puzzled because I misreported something. The last binary that
worked for me was 8.3.2 - not 8.3.3

> I don't have a system that will run 8.1, so I can't test what is 
> causing the problem, maybe somebody else can help diagnose this?

Sorry to be using such an old system, but my application needs to
work in an educational environment, so I figured MacOS 8.1
was a decent baseline.

> If you still have your 8.3.3 install, could you try to run one of the 
> unmerged 8.3.4 binaries - e.g. 'Simple Tcl (sh-ppc)' - in a folder 
> with a copy of the '(Support Libraries)' folder from 8.3.3 present?

I'll try this (except with 8.3.2 Support Libs) sometime today
and report back!

Thanks for the help, Daniel.

Cheers, Ralph Hempel - P.Eng.

Re: [MACTCL] 8.3.4 problem with MacOS 8.1

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

> >The application "Wish" could not be opened because
> >"InterfaceLib--FetchFontInfo" could not be found
> 
> I'm puzzled by this, as the projects have not changed w.r.t libraries 
> since 8.3.3. I have updated the Apple Universal Interfaces to what 
> comes with the latest CarbonLib SDK however so the problem could 
> originate there...

I ran into a similar problem in the past (with another Font Manager routine): 
Apple added new routines in Universal Headers that don't exist on OS8. I 
haven't been able to find out how I should have known that these routines are 
OS9-only.
--
Jack Jansen             | ++++ stop the execution of Mumia Abu-Jamal ++++
Jac...@or... | ++++ if you agree copy these lines to your sig ++++
www.cwi.nl/~jack        | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm 

[MACTCL] ANNOUNCE: Mac Tcl/Tk 8.3.4 Binary Release

[Daniel A. S. <da...@us...>]

Macintosh Tcl/Tk 8.3.4 Binary Release Announcement
Oct 24, 2001

The Tcl maintainers are pleased to announce the availability of 
Macintosh binaries for the 8.3.4 releases of the Tcl scripting 
language and the Tk toolkit. This is the fourth patch release of 
Tcl/Tk 8.3. More details can be found below.

An installer appropriate for most Mac users is available for direct download at
	http://prdownloads.sourceforge.net/tcl/TclTk_8.3.4_RuntimeInstall.bin

For Tcl developers, a more complete installer containing additional binaries,
CodeWarrior projects and complete sources is available at
	http://sourceforge.net/project/showfiles.php?group_id=10894&release_id=57667

For more information, please visit
  * the Tcl Developer Xchange Tcl/Tk 8.3.4 information page
	http://www.tcl-tk.net/software/tcltk/8.3.html
  * the Tcl project page on SourceForge
	http://sourceforge.net/tcl/
  * the SourceForge Tcl Foundry
	http://sourceforge.net/foundry/tcl-foundry/
  * the Tcl Developer Xchange:
	http://www.tcl-tk.net/


Regards,
Daniel A. Steffen
da...@us...

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

--- Mac specific changes for Mac Tcl/Tk 8.3.4, Oct 19, 2001 ---

   - timezone support

   - mac time epoch changed to standard unix epoch

   - glob -dir compatibility mode for unix style relative paths

   - fix to glob -join, it wasn't traversing aliased folders. This notably
     fixes the bug of pkgIndex files not being seen inside aliased folders.

   - when loading shared libraries, comparison of package name to code
     fragment name changed to only match on the length of the package name,
     this allows for fragment names with version numbers appended.

   - crashing bug fix when printing to console at program exit after
     the console has already been closed.

   - correct use of Tcl_JoinPath in tk_library initialization

   - reorganized resources to avoid multiple copies in applications and
     shared libraries, the script libraries & Xcursors etc are now no longer
     duplicated in Wish but are only included in the resources of Tk.shlb.
     Corrected how tk deals with tcl library files present both in
     resources and in $tk_library directory (the $tk_library now always
     takes precedence).

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

--- About Tcl/Tk ---

Tool Command Language (Tcl) is an interpreted language and a very portable
interpreter for that language.  Tcl is embeddable and extensible, and has
been used by companies and organizations world-wide since its creation in
1988 by John Ousterhout.

As a language, it is much like UNIX shell languages.  There is very little
syntax and it is easy to learn.  It is used to glue together building
blocks built in system programming languages like C, C++, and Java.  These
building blocks appear as commands, or verbs, in the script language.  It
is easy to embed Tcl into a legacy program so you can script the behavior
of that program and add in other building blocks like a GUI interface.  The
Tcl interpreter is written in C and has been ported to almost every
computer platform.

Tk is a portable GUI toolkit for Tcl, it allows simple and dynamic creation
of graphical interfaces that run on Mac, Windows, UNIX and other platforms.

Check out the SourceForge Tcl Foundry:
	http://sourceforge.net/foundry/tcl-foundry/
An informal survey shows over 100 Tcl-related SourceForge projects

Please visit the Tcl Developer Xchange web site:
	http://www.tcl-tk.net/		http://tcl.ActiveState.com/

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

Tcl/Tk 8.3.4 Release Announcement
October 22, 2001

The Tcl maintainers are pleased to announce the 8.3.4 releases of the
Tcl scripting language and the Tk toolkit.  This is the fourth patch
release of Tcl/Tk 8.3.  More details can be found below.  We'd like to
thank all those that submit bugs and patches as they are the primary
source of information for us to identify problems in the core.

Where to get the new releases:
------------------------------

Tcl/Tk 8.3.4 sources are freely available from the Tcl Developer Xchange
web site at:

	http://www.tcl-tk.net/software/tcltk/8.3.html
	http://tcl.ActiveState.com/software/tcltk/8.3.html

This web page also contains additional information about the releases,
including new features and notes about installing and compiling the
releases.  The files are directly available from the Tcl SourceForge
project's file distribution area (which includes Mac binaries):

	http://sourceforge.net/project/showfiles.php?group_id=10894

ActiveState also provides Windows, Linux and Solaris binaries that
include numerous popular extensions at:

	http://aspn.activestate.com/ASPN/Downloads/ActiveTcl/
	(should be available by end of day Oct 23)

For additional information:
---------------------------

Please visit the Tcl Developer Xchange web site:

	http://www.tcl-tk.net/
	http://tcl.ActiveState.com/

This site contains a variety of information about Tcl/Tk in general,
the core Tcl and Tk distributions, and much more.

Thank you for your contributions:
---------------------------------

As usual, this release includes contributions from the Tcl community.
Tcl/Tk is maintained by the community, with the source repository and
bug database at SourceForge:

	http://tcl.SourceForge.net/

Everyone is encouraged to participate in making Tcl an even better
language.

Summary of Changes in Tcl/Tk 8.3.4:
--------------------------------------

The following were the main changes in this release.  A complete list
can be found in the ChangeLog file at the root of the source tree.  This
is a patch release, so it primarily included bug fixes and corrections
to erratic behavior.  Below are only the most notable changes.

  * Improved build support for GNU (HURD), QNX and Mac OS X

  * Enabled 64bit compilation on HP-11 via --enable-64bit

  * Updated msgcat and http packages

  * New file I/O flush management for Windows (up to 100x speedup)

  * Plugged a few minor memory leaks in error cases

  * Corrected handling of spaces in pathnames passed to 'exec' on Windows

  * Win64 support using Whistler64 RC 1

  * Native memory allocator now the default on Windows.

  * Corrected thread finalization problems for threaded builds.

  * Updated unicode encodings from http://www.unicode.org/

  * Fixed tk_chooseDirectory crash on Win95

  * Removed 2 second 'raise' delay for some Unix windows managers

  * Updated Mac/Windows wish console

  * Enhanced 'bgerror' dialog

  * Fixed file filtering in Motif file dialogs

The full list can be seen at

     http://sourceforge.net/project/shownotes.php?release_id=57667

-- 
** Daniel A. Steffen                  **
** <mailto:da...@us...> **

[MACTCL] ANNOUNCE: Mac Tcl/Tk 8.3.4 Binary Release

[Daniel A. S. <da...@us...>]

Macintosh Tcl/Tk 8.3.4 Binary Release Announcement
Oct 24, 2001

The Tcl maintainers are pleased to announce the availability of 
Macintosh binaries for the 8.3.4 releases of the Tcl scripting 
language and the Tk toolkit. This is the fourth patch release of 
Tcl/Tk 8.3. More details can be found below.

An installer appropriate for most Mac users is available for direct download at
	http://prdownloads.sourceforge.net/tcl/TclTk_8.3.4_RuntimeInstall.bin

For Tcl developers, a more complete installer containing additional binaries,
CodeWarrior projects and complete sources is available at
	http://sourceforge.net/project/showfiles.php?group_id=10894&release_id=57667

For more information, please visit
  * the Tcl Developer Xchange Tcl/Tk 8.3.4 information page
	http://www.tcl-tk.net/software/tcltk/8.3.html
  * the Tcl project page on SourceForge
	http://sourceforge.net/tcl/
  * the SourceForge Tcl Foundry
	http://sourceforge.net/foundry/tcl-foundry/
  * the Tcl Developer Xchange:
	http://www.tcl-tk.net/


Regards,
Daniel A. Steffen
da...@us...

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

--- Mac specific changes for Mac Tcl/Tk 8.3.4, Oct 19, 2001 ---

   - timezone support

   - mac time epoch changed to standard unix epoch

   - glob -dir compatibility mode for unix style relative paths

   - fix to glob -join, it wasn't traversing aliased folders. This notably
     fixes the bug of pkgIndex files not being seen inside aliased folders.

   - when loading shared libraries, comparison of package name to code
     fragment name changed to only match on the length of the package name,
     this allows for fragment names with version numbers appended.

   - crashing bug fix when printing to console at program exit after
     the console has already been closed.

   - correct use of Tcl_JoinPath in tk_library initialization

   - reorganized resources to avoid multiple copies in applications and
     shared libraries, the script libraries & Xcursors etc are now no longer
     duplicated in Wish but are only included in the resources of Tk.shlb.
     Corrected how tk deals with tcl library files present both in
     resources and in $tk_library directory (the $tk_library now always
     takes precedence).

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

--- About Tcl/Tk ---

Tool Command Language (Tcl) is an interpreted language and a very portable
interpreter for that language.  Tcl is embeddable and extensible, and has
been used by companies and organizations world-wide since its creation in
1988 by John Ousterhout.

As a language, it is much like UNIX shell languages.  There is very little
syntax and it is easy to learn.  It is used to glue together building
blocks built in system programming languages like C, C++, and Java.  These
building blocks appear as commands, or verbs, in the script language.  It
is easy to embed Tcl into a legacy program so you can script the behavior
of that program and add in other building blocks like a GUI interface.  The
Tcl interpreter is written in C and has been ported to almost every
computer platform.

Tk is a portable GUI toolkit for Tcl, it allows simple and dynamic creation
of graphical interfaces that run on Mac, Windows, UNIX and other platforms.

Check out the SourceForge Tcl Foundry:
	http://sourceforge.net/foundry/tcl-foundry/
An informal survey shows over 100 Tcl-related SourceForge projects

Please visit the Tcl Developer Xchange web site:
	http://www.tcl-tk.net/		http://tcl.ActiveState.com/

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

Tcl/Tk 8.3.4 Release Announcement
October 22, 2001

The Tcl maintainers are pleased to announce the 8.3.4 releases of the
Tcl scripting language and the Tk toolkit.  This is the fourth patch
release of Tcl/Tk 8.3.  More details can be found below.  We'd like to
thank all those that submit bugs and patches as they are the primary
source of information for us to identify problems in the core.

Where to get the new releases:
------------------------------

Tcl/Tk 8.3.4 sources are freely available from the Tcl Developer Xchange
web site at:

	http://www.tcl-tk.net/software/tcltk/8.3.html
	http://tcl.ActiveState.com/software/tcltk/8.3.html

This web page also contains additional information about the releases,
including new features and notes about installing and compiling the
releases.  The files are directly available from the Tcl SourceForge
project's file distribution area (which includes Mac binaries):

	http://sourceforge.net/project/showfiles.php?group_id=10894

ActiveState also provides Windows, Linux and Solaris binaries that
include numerous popular extensions at:

	http://aspn.activestate.com/ASPN/Downloads/ActiveTcl/
	(should be available by end of day Oct 23)

For additional information:
---------------------------

Please visit the Tcl Developer Xchange web site:

	http://www.tcl-tk.net/
	http://tcl.ActiveState.com/

This site contains a variety of information about Tcl/Tk in general,
the core Tcl and Tk distributions, and much more.

Thank you for your contributions:
---------------------------------

As usual, this release includes contributions from the Tcl community.
Tcl/Tk is maintained by the community, with the source repository and
bug database at SourceForge:

	http://tcl.SourceForge.net/

Everyone is encouraged to participate in making Tcl an even better
language.

Summary of Changes in Tcl/Tk 8.3.4:
--------------------------------------

The following were the main changes in this release.  A complete list
can be found in the ChangeLog file at the root of the source tree.  This
is a patch release, so it primarily included bug fixes and corrections
to erratic behavior.  Below are only the most notable changes.

  * Improved build support for GNU (HURD), QNX and Mac OS X

  * Enabled 64bit compilation on HP-11 via --enable-64bit

  * Updated msgcat and http packages

  * New file I/O flush management for Windows (up to 100x speedup)

  * Plugged a few minor memory leaks in error cases

  * Corrected handling of spaces in pathnames passed to 'exec' on Windows

  * Win64 support using Whistler64 RC 1

  * Native memory allocator now the default on Windows.

  * Corrected thread finalization problems for threaded builds.

  * Updated unicode encodings from http://www.unicode.org/

  * Fixed tk_chooseDirectory crash on Win95

  * Removed 2 second 'raise' delay for some Unix windows managers

  * Updated Mac/Windows wish console

  * Enhanced 'bgerror' dialog

  * Fixed file filtering in Motif file dialogs

The full list can be seen at

     http://sourceforge.net/project/shownotes.php?release_id=57667

-- 
** Daniel A. Steffen                  **
** <mailto:da...@us...> **