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

Re: [MACTCL] Loading extensions under Tk on Macintosh

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

Mats, et al...

The intention was always that if you wanted to distribute an extension 
the same way on the Mac that you do on Unix, with separate files, etc, 
you could.  The only difference is that /usr/lib <==> Startup 
Disk:Extensions:Tool Command Language.  All the stuff things in the 
resource fork jazz was optional, a bonus for the Mac, not required.

Jim

On Tuesday, April 9, 2002, at 11:04  PM, Mats Bengtsson wrote:

>
> Just made a build of QuickTimeTcl without the TEXT resource,
> and using a separate pkgIndex.tcl file, and that works fine on mac :-)
> Think snack has a bit more complex TEXT resource but its
> windows distro should give a hint there.
>
>
> Mats
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] ANNOUNCE: Compiler 3.3 beta 2

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

Hello everybody,

  "Compiler" 3.3 beta 2 test is out

  What's new:

   http://www.compiler-factory.com/LinComp-CHANGES.html

  Download:

   http://www.compiler-factory.com

   and follow the "Download" link



  Development News:

   this release has 3 goals:

    1: compile the tcl/tk default libraries into native C
       ( lib/tcl8.3/*, lib/tk8.3/* )
    2: correct bugs introduced in the previous edition
    3: improve the MacOs edition to become more standart
       like Windows and Unix.


   Feature 1
   ---------

    this is a customer request based and additional speed
    requirements for a large scale gui application. This
    application uses a "text" widget filled up with a lot
    of data. The speed in traditional tcl was to slow and
    the request was born -> done.
    To get this working the build process need an aditio-
    nal feature called "Full Package Names". The reason for
    this feature was in the tcl library with the 2 packages
    http1.0 and http2.4 which are the same package "http"
    but with different version numbers. The original
    "project.cct" file only allows to define one package
    with one major/minor number. The new feature adds the
    $PACKAGENAME$MAJOR.$MINOR systax to define 2 different
    packages "PACKAGE http1.0 { ... }" and "PACKAGE
    http2.4 { ... }" into one project.cct file. As addi-
    tinal benefit I cleanup the "initScript" tcl-C variable
    to fit better the needs of POWER-Tcl and to be the
    same in Unix, Windows and Mac. To fit all test cases
    a *_SafeInit, which only calles the *_Init,  was added
    to the created C code.


   Feature 2
   ---------

    the last beta introduced a couple of bugs -> fixed.
    A customer reportes problems with MacOs which was
    in fact a traditional tcl bug -> fixed and reported
    to the core team. An additional bug was fixed based
    on the special condition that a tcl "if" command was
    last in a procedure and the body was not called ->
    fixed.


    Right now all traditional tcl code files (*.tcl) are
    gone, the pkgIndex.tcl are still left.


   Feature 3
   ---------

    MacOs is special, but starting with 3.3beta 1 it be-
    comes less special from release to release. The se-
    cond beta uses the same setup "InitScript" as Unix
    and Windows. All special MacOs additions like adding
    the lib/tcl8.3/* and lib/tk8.3/* files into the res-
    ource are gone. Right now the Unix, Windows and Mac
    addition have the same directory structure, using the
    same files and providing the same features. The
    "cct -t ?MyProj? -m mac91ppc export -c" does now work
    proper even the project.cct file and the tcl project
    files are not in the same directory.



mfg

  aotto :)

Re: [MACTCL] Loading extensions under Tk on Macintosh

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

Just made a build of QuickTimeTcl without the TEXT resource,
and using a separate pkgIndex.tcl file, and that works fine on mac :-)
Think snack has a bit more complex TEXT resource but its
windows distro should give a hint there.


Mats

Re: [MACTCL] Setting TkfPW.app

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

Jim,

What I do know for sure is that when I double-click on TkfPW , which is 
the "Whish Shell.app" copy with "Resources/Scripts/AppMain.tcl" added to 
it, I get the message:
....
Before using TkfPW, You need to define the TKPW_HOME environment variable
....

Also, on the plain "Wish Shell.app", choosing from the menu 
"File>Sources" the script "/usr/local/bin/tkfpw", I get the same message.

Finally, on "Terminal.app" typing
$  /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell -f 
/usr/local/bin/tkfpw
I get "TkfPW" running on my desktop.


On Tuesday, April 9, 2002, at 01:46  AM, Jim Ingham wrote:

> Lizardo,
>
> Are you sure HOME is not defined.  When I launch Wish by 
> double-clicking on
> it in the finder, then do
>
> parray env
>
> In the Tk console window, I see HOME, PATH, SHELL, USER &
> __CF_USER_TEXT_ENCODING.
>
> Jim

Lizardo H. C. M. Nunes

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

Re: [MACTCL] Setting TkfPW.app

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

Jim,

What I'm sure is that when I double-click on TkfPW , which is the "Whish 
Shell.app" copy with Resources/Scripts/AppMain.tcl added, I get the 
message:
....
Before using TkfPW, You need to define the TKPW_HOME environment variable
....

Also, on the plain "Wish Shell.app", choosing from the menu 
"File>Sources" the script "/usr/local/bin/tkfpw", I get the same message.

Finally, on "Terminal.app" typing
$  /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell -f 
/usr/local/bin/tkfpw
I get "TkfPW" running on my desktop.


On Tuesday, April 9, 2002, at 01:46  AM, Jim Ingham wrote:

> Lizardo,
>
> Are you sure HOME is not defined.  When I launch Wish by 
> double-clicking on
> it in the finder, then do
>
> parray env
>
> In the Tk console window, I see HOME, PATH, SHELL, USER &
> __CF_USER_TEXT_ENCODING.
>
> Jim

Lizardo H. C. M. Nunes

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

Re: [MACTCL] Loading extensions under Tk on Macintosh

[Jean-Claude W. <jc...@eq...>]

Michael A. Cleverly <mi...@cl...> wrote:

>I'm writing a multimedia Tk application which will be distributed on a
>CD-ROM.  It uses the Snack extension for audio, and for video either
>QuickTimeTcl/TMCI (Windows) or xanim drawing into a Tk frame (Linux;
>probably eventually Solaris & *BSD too).
[...]
>I only have limited experience with the Macintosh.  Can someone clue me in
>on how I can have my app run on a Macintosh without making the end user
>first install Tcl/Tk & then the extensions? Would it be possible to build
>Tcl/Tk with QuickTimeTcl & Snack statically linked, and would this solve
>my problem? (Not that I have a C compiler for the Mac, but I'd be happy to
>PayPal someone who did.)  Or are my problems caused due to the fact that
>the CD doesn't have data/resource fork info? And, without Tcl/Tk being
>installed, could I work around this using the Mac-specific Tcl commands?

Other replies already cover most aspects I think, but allow me to single
out and summarize the issue of "what differs on the Mac" (macos pre-X,
that is):

 - mac applications store code in the data fork for PPC, and in the
   resource fork for 68K, these can be combined to make a "fat" binary
 - but no matter what, you need a resource fork with *some* info in it,
   and that's what makes cd's, file xfers, and vfs "different" on mac
 - for a mac application to run off the cd, it has to be written using
   the HFS(+) format AFAIK, i.e. the mac's filesystem as image on a cd,
   that's the only way to have resource forks without unpacking
 - to use the cd on multiple platform, you create a "hybrid cd", which
   stores files once, but contains multiple catalogs/indexes, so that
   each O/S sees a native fmt (unix: rockridge, mac: hfs, win: joliet)

If you're going for the hybrid, then you have a normal Mac context, and
you can have Mac files with data + resource forks on the CD.  In your
case, you'd have a couple such files: Daniels shared tclkit, and
extensions such as Snack.

If you don't create a hybrid CD, then you will *have* to ask Mac users do
unpack things before use.  This need not be a show stopper, but it's less
of a runs- out-of-the box type experience.  This approach does treat Mac
users as second-class citizens, IMO.  But having said that, it's not
uncommon, many people go through stuffit-expander for network downloads.
 In this scenario, you store Mac files in a packed single-file form, such
as MacBinary (.bin) or BinHex (.hqx), and ask then to unpack before use.
 You'll need to decide on what to unpack, and how to find the different
parts (loading the unpacked Snack shared library).

I'm pondering on a third option, in which tclkit is augmented with at
least MacBinary unpack support.  This would allow Mac shared libs to run
from vfs, and hence scripted documents.  It would not avoid the initial
unpack of tclkit itself (this is unavoidable without HFS on cd), but it'd
make it possible to create multi-platform setups without access to a Mac,
even if shared libraries such as Snack are used.  The end result is a
non-hybrid CD with a "myapp.bin" on it (this is tclkit), plus a few more
mac-specific .bin files and/or one or more scripted documents (i.e. all
normal single-fork datafiles).  To use it on a mac, one stuffit-expands
myapp.bin (once) to the hard disk, and launches it.  Other unpacking
would then happen under control of the application, and on-the-fly.  This
is not perfect, but is as minimal as I can come up with, and one can
still claim that it does not clutter the user's disk - uninstall is a
matter of dragging the expanded "myapp" application file to the trash.

This third option does not exist today.  I'm not sure to what extent the
mac supports launching an app on disk-insertion.  If it doesn't for non-
HFS disks, for example, then this third option will remain an imperfect
solution no matter what.  Then again, if the goal is to produce cd's
which run anywhere - including on the mac, then for some this might be
good enough?

-jcw

Re: [MACTCL] Loading extensions under Tk on Macintosh

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

Jean-Claude,

At 11:48 +0200 on 9/4/02, Jean-Claude Wippler wrote:

>Regarding the TEXT resource for pkgIndex.tcl: I would expect that one can
>also use the *nix/win* approach and store it as normal file?

looking at tcl/library/package.tcl, that appears to be the case 
indeed; tclPkgUnknown first looks for pkgIndex.tcl files and only 
uses tclMacPkgSearch to search for TEXT resources afterwards.

after sending my last message, it occurred to me that the question of 
using a no resource fork filesystem on the mac is moot anyway as the 
mac tclkit _executable_ most definitely needs a resource fork (for 
the 'cfrg' resource).

>FWIW, CD's can be mastered as hybrid on unix, using "mkisofs" - the
>TclBlast! 1999 CD was built that way to work on a dozen platforms,
>including classic MacOS.  It takes some tinkering, but is fully described
>in the documentation (basically you need to tell mkisofs how/where to get
>the resource fork data).

the question is how to setup mac files with a resource fork on a unix 
box, so that mkisofs does the right thing when building HFS+, I 
remember playing with this unsuccessfully a long time ago.

>Daniel, we could use MacBinary for this.  Is there a Tcl script which
>unpacks MacBinary to data/rsrc forks on the Mac?  If not, I'd be happy to
>help make it happen - since this seems indeed to be the one last piece on
>the puzzle to be able to run class MacOS shared libs from vfs.

it's probably not possible to do macbinary from the script level, as 
the resource fork has to be read in a flat file manner for the 
macbinary format, which isn't possible through the tcl [resource] 
command. However, it should be easy to make a tcl extension from the 
public source macbinary code.

BTW, JC, I'm currently working on updating my tclkit patches to the 
vfs, tclkit & Tcl/Tk HEADs, to be able to finally answer your message 
from like a month ago, sorry for the delay... everything builds fine, 
but I've again run into some startup troubles with the init scripts, 
which I'm debugging now. hopefully I'll have a new build of tclkit 
soon, with only small patches to tclkit. (HEAD metakit & mktcl build 
& work flawlessly on the mac now btw, thanks)

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/>

Re: [MACTCL] Loading extensions under Tk on Macintosh

[Jean-Claude W. <jc...@eq...>]

Daniel A. Steffen <st...@ic...> wrote:

>For mac package loading to work off a CD, I suspect you need resource 
>forks on the cd (shared libraries on the mac need a 'cfrg' resource 
>so that they can be loaded, and mac Tcl extensions require a TEXT 
>resource with the pkgIndex).

Regarding the TEXT resource for pkgIndex.tcl: I would expect that one can
also use the *nix/win* approach and store it as normal file?

>AFAIK e.g. Toast for Mac can write hybrid CD's with HFS+, ISO, Joliet 
>and Rockridge filesystems all on one CD; this may allow you to get 
>resource forks onto the cd, as long as you master the cd on the mac.

FWIW, CD's can be mastered as hybrid on unix, using "mkisofs" - the
TclBlast! 1999 CD was built that way to work on a dozen platforms,
including classic MacOS.  It takes some tinkering, but is fully described
in the documentation (basically you need to tell mkisofs how/where to get
the resource fork data).

One can play tricks and master in such a way that some files show up only
in specific formats.  An example for this is a "readme" file, which can
be prepared with the proper LF/CR/CRLF formatting and names (README/Read
Me/readme.txt) and even with type/creator set to SimpleText on the Mac. 
Small details which can make that first experience just a little smoother...

Mastering on MacOS X might give you the best of all world, because you
could presumably mount the image as any of RockRidge/HFS+/Joliet and
check that it works properly before ever burning a single disk.

>there may be a way around the resource fork requirement; IIRC, the 
>code in tclMacLoad.c will try to load the complete datafork of a file 
>as a PPC fragment if no 'cfrg' resource can be found, and a 
>traditional pkgindex.tcl file should work with that (via [load]), but 
>I have never tried this.
>The resource fork obstacle is also the main reason why dynamic 
>library loading from vfs in tclkit doesn't work on the mac currently.

Daniel, we could use MacBinary for this.  Is there a Tcl script which
unpacks MacBinary to data/rsrc forks on the Mac?  If not, I'd be happy to
help make it happen - since this seems indeed to be the one last piece on
the puzzle to be able to run class MacOS shared libs from vfs.

-jcw

Re: [MACTCL] Loading extensions under Tk on Macintosh

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

"Michael A. Cleverly" wrote:
> 
> The main.tcl script figures out where it's running from via [info script]
> and then adds the following directories (using [file join]) to auto_path:
> 

8.3.4 on Mac has a bug in [info script], fixed in 8.4 (and tclkit) I believe.

> 
> On Macintosh, however, it doesn't seem to work--at least, not for the
> compiled extensions (BWidgets doesn't have a problem).
> 

What happens of you do "load fullPath/QuickTimeTcl.shlb" ?

> 
> Only when I specifically installed the Snack .shlb's into the
> "Applications:Tcl/Tk Folder 8.3.4:Tool Command Language" folder (and also
> ran the QuickTimeTcl installer) was I able to load either package.
> 

Have a faint memory of that snack uses a trick to source tcl code
into the resource fork (which fails on a CD), but can't find the sources
right now.

Mats

PS: Any feedback on QuickTimeTcl is welcome...

Re: [MACTCL] Loading extensions under Tk on Macintosh

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

Michael,

the following setup works for me: (on a HFS+ filesystem)

use the _shared_ tclkit build from 
http://www.maths.mq.edu.au/~steffen/tcltk/tclkit/tclkit_shared.sit.bin

and put snack.shlb into e.g. a subdirectory called lib

then execute

	set auto_path [concat [list [file join [pwd] lib]] $auto_path]
	package require snack

You may want to take a look at the mac distribution of Emu 
(http://sourceforge.net/projects/emu/) where I use something similar 
(without tclkit) to load snack and other extensions from a local 
directory. (esp. look at the resources of the executables)

For mac package loading to work off a CD, I suspect you need resource 
forks on the cd (shared libraries on the mac need a 'cfrg' resource 
so that they can be loaded, and mac Tcl extensions require a TEXT 
resource with the pkgIndex).
AFAIK e.g. Toast for Mac can write hybrid CD's with HFS+, ISO, Joliet 
and Rockridge filesystems all on one CD; this may allow you to get 
resource forks onto the cd, as long as you master the cd on the mac.

there may be a way around the resource fork requirement; IIRC, the 
code in tclMacLoad.c will try to load the complete datafork of a file 
as a PPC fragment if no 'cfrg' resource can be found, and a 
traditional pkgindex.tcl file should work with that (via [load]), but 
I have never tried this.
The resource fork obstacle is also the main reason why dynamic 
library loading from vfs in tclkit doesn't work on the mac currently.

Also note that [info script] used to have a bug on the mac that could 
have an impact here, I had a look at it some time back and thought I 
had fixed it, but that may have been post 8-3-4

on the mac, instead of using [info script], it may be easier to embed 
a tclkitrc resource in tclkit that sets the auto_path relative to 
[pwd] (which defaults to the executable's directory at startup) and 
then sources your main.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/>

Re: [MACTCL] [ANS] Running *.tcl scripts

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

Lizardo,

Are you sure HOME is not defined.  When I launch Wish by double-clicking on
it in the finder, then do

parray env

In the Tk console window, I see HOME, PATH, SHELL, USER &
__CF_USER_TEXT_ENCODING.

Jim

> Hi,
> 
> I tried what you said and it didn't work. The binary startup script
> "tkfpw" demands the definition of the environment  variable
> "TKFPW_HOME". That's defined in my ".cshrc" file.
> 
> I'm speculating here, but when I double-click the "TkfPW.app", the
> "Finder.app" performs the action, not me, and it doesn't recognize the
> environment variable.
> 
> Is it possible to edit and define the environment variable in the
> "AppMain.tcl" script?
> 
> I'm sending to you the "AppMain.tcl" script.
> 
> 
> 
> Notice that the "TkfPW" version 1.3 (116 Kb of download),
> ftp://ftp.ec-nantes.fr/pub/DMN/TkfPW
> is pretty simple to install; takes less than five minutes. All you have
> to do, after running the  "Install" script as root, is to comment out
> line 3 of "tkfpw":
> exec wish "$0" "$@"
> 
> and setenv "TKFPW_HOME".
> 
> Running on my system is
> $ /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell -f
> /usr/local/bin/tkfpw
> 
> Still, there are problems of geometry and functionality.
> 
> Thanks,
> Lizardo H. C. M. Nunes
> 
> ...But we preach Christ crucified, to the Jews a stumbling block, and to
> the
> Greeks foolishness;(...)but God has chosen the foolish things of the
> world
> to confound the wise, and God has chosen the weak things of the world to
> confound the things which are strong;(I Cor.1:23&27)
> 
> ------------------------------------
> From: Jim Ingham <ji...@ap...>
> Date: Mon Apr 08, 2002  03:22:06  PM America/St_Johns
> To: "Lizardo H. C. M.  Nunes" <li...@ur...>
> Cc: tc...@li...
> Subject: Re: [MACTCL] [ANS] Running *.tcl scripts
> 
> The other way to do this (probably appropriate for TkfPW) is to make a
> copy of the Wish Shell application, call it something suggestive like
> TkfPW.  Then make a directory in Resources in the App package called
> Scripts.  Put a script called AppMain.tcl there which contains your
> startup code.  The Scripts directory will also be added to the auto_path
> in Tcl, so you can put all your other packages there, and the tcl script
> loading code will find them (provided they have tclIndex's etc...)  Then
> if you want to get fancy, you can change the icon to your own icon, and
> even make your own document types so you can claim .f files, or whatever
> you want...
> 
> Jim
> 

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

[MACTCL] Loading extensions under Tk on Macintosh

[Michael A. C. <mi...@cl...>]

I'm writing a multimedia Tk application which will be distributed on a
CD-ROM.  It uses the Snack extension for audio, and for video either
QuickTimeTcl/TMCI (Windows) or xanim drawing into a Tk frame (Linux;
probably eventually Solaris & *BSD too).

I'd like to add Macintosh support, but I'm having difficulty figuring out
how to (or if it's even possible) to load shared libraries off of the
CD-ROM on-the-fly.

The layout of the file system for the CD is:

    main.tcl
    assets/
    assets/audio
    assets/gifs
    assets/video
    lib/
    lib/generic
    lib/generic/BWidget-1.3.1
    lib/generic/MovieController
    lib/macintosh
    lib/macintosh/QuickTimeTcl
    lib/macintosh/snack2.1
    lib/linux
    lib/linux/Img1.2
    lib/linux/snack2.1
    lib/windows
    lib/windows/Img1.2
    lib/windows/QuickTimeTcl
    lib/windows/snack2.1
    lib/windows/tmci
    bin/
    tcl/

In the bin/ directory I have copies of the tclkit runtime for Windows &
Linux.  (To be clear, I'm not using/creating a scripted document; the
tclkit binaries are just a convenient way to get Tcl/Tk in one nice
self-contained package.)

The main.tcl script figures out where it's running from via [info script]
and then adds the following directories (using [file join]) to auto_path:

    $HOME/lib/[string tolower $tcl_platform(platform)]
    $HOME/lib/[string tolower $tcl_platform(os)]
    $HOME/lib/generic

This works like a charm for Windows & Linux.  Tcl is able to find the
right version of Snack & the other extensions.

On Macintosh, however, it doesn't seem to work--at least, not for the
compiled extensions (BWidgets doesn't have a problem).

I initially tried to use the static build of tclkit for the Macintosh and
the snack package wouldn't load snack.shlb.  I next downloaded the Tcl/Tk
8.3.4 binary from SF.  Same problem.

Only when I specifically installed the Snack .shlb's into the
"Applications:Tcl/Tk Folder 8.3.4:Tool Command Language" folder (and also
ran the QuickTimeTcl installer) was I able to load either package.

I only have limited experience with the Macintosh.  Can someone clue me in
on how I can have my app run on a Macintosh without making the end user
first install Tcl/Tk & then the extensions? Would it be possible to build
Tcl/Tk with QuickTimeTcl & Snack statically linked, and would this solve
my problem? (Not that I have a C compiler for the Mac, but I'd be happy to
PayPal someone who did.)  Or are my problems caused due to the fact that
the CD doesn't have data/resource fork info? And, without Tcl/Tk being
installed, could I work around this using the Mac-specific Tcl commands?

As you can see, I'm rather confused as to what to do.  :-)

Thanks in advance,

Michael

Re: [MACTCL] [ANS] Running *.tcl scripts

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

Hi,

I tried what you said and it didn't work. The binary startup script 
"tkfpw" demands the definition of the environment  variable 
"TKFPW_HOME". That's defined in my ".cshrc" file.

I'm speculating here, but when I double-click the "TkfPW.app", the 
"Finder.app" performs the action, not me, and it doesn't recognize the 
environment variable.

Is it possible to edit and define the environment variable in the 
"AppMain.tcl" script?

I'm sending to you the "AppMain.tcl" script.

Re: [MACTCL] [ANS] Running *.tcl scripts

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

On Monday, April 8, 2002, at 03:22  PM, Jim Ingham wrote:

> The other way to do this (probably appropriate for TkfPW) is to make a 
> copy of the Wish Shell application, call it something suggestive like 
> TkfPW.  Then make a directory in Resources in the App package called 
> Scripts.  Put a script called AppMain.tcl there which contains your 
> startup code.  The Scripts directory will also be added to the 
> auto_path in Tcl, so you can put all your other packages there, and the 
> tcl script loading code will find them (provided they have tclIndex's 
> etc...)

Cool. I read a previous message of yours and I would write to you today 
asking for detalis. Thanks.

Anyway, there's a lot of hacking needed  to let TkfPW fully functional 
and more AQUA-like. If there's somebody interested...

Also, I've compiled and tested some Public Domain Fortran Libs available 
at Netlib:

ATLAS (Altivec enabled)
LAPACK
QUADPACK
ODEPACK
PGPLOT (both X driver and Cocoa AquaTerm.app )
SLATEC

I'm organizing html docs for every routine. My idea is to provide an 
integrated help.  I think that TkfPW could be a GUI fPW and API together.

I compiled MINPACK too, but tests failed. Once I compile SPECFUN, I'm 
done.

Thanks again,
Lizardo H. C. M. Nunes

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

Re: [MACTCL] [ANS] Running *.tcl scripts

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

The other way to do this (probably appropriate for TkfPW) is to make a 
copy of the Wish Shell application, call it something suggestive like 
TkfPW.  Then make a directory in Resources in the App package called 
Scripts.  Put a script called AppMain.tcl there which contains your 
startup code.  The Scripts directory will also be added to the auto_path 
in Tcl, so you can put all your other packages there, and the tcl script 
loading code will find them (provided they have tclIndex's etc...)  Then 
if you want to get fancy, you can change the icon to your own icon, and 
even make your own document types so you can claim .f files, or whatever 
you want...

Jim

On Sunday, April 7, 2002, at 03:43  PM, Lizardo H. C. M. Nunes wrote:

> If there's something else, please let me know.
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] TkfPW on Mac OS X

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

For the Fortran guys,

The TkfPW

http://www.ec-nantes.fr/DMN/WWW/Software/TkfPW

(Tk Fortran Programmer's Workshop is running on my system ). It could be 
a nice replacement for the Absoft IDE.

There are a lot of think to be set yet and it isn't prefect, but it's a 
good start...

Lizardo H. C. M. Nunes

Re: [MACTCL] Alias bug?

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

On Monday, April 8, 2002, at 03:27  AM, Daniel A. Steffen wrote:

> At 3:00 -0300 on 8/4/02, Lizardo H. C. M.  Nunes wrote:
>
>> On "Terminal.app" I tried
>> $ alias wish /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell
>> So,
>> $ wish
>> and I got
>> "/Applications/Wish: Command not found."
>>
>
> you probably wanted:
> 	alias wish '/Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell'

It worked. (Stupid mistake of mine)


>> What I really want to know is how to make "bash" recognize the
>>  "#!/usr/local/bin/wish" line.
>
> create a symolic link:
> 	sudo ln -s /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ 
> Shell /usr/local/bin/wish
>

I did
$ sudo ln -s /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell 
/usr/bin/wish

I'm trying to run a simple "button.tcl" script:
-----------------------
#! /usr/bin/wish -f

button .b -text "Press Me" -command exit
pack .b
  ----------------------
When I type

$ ./button.tcl

nothing happens. Why?

Thanks mate,
Lizardo H. C. M. Nunes

Re: [MACTCL] BUG: tcl8.3.4

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

At 12:27 +0200 on 5/4/02, AO...@t-... wrote:

>   a valid socket file-handle adds "-sockname" to fconfigure.
>   in unix and windows the test on this option is based on
>
>      strncmp(optionName, "-sockname", len)
>
>   which allows -s, -so, .. -sockname as valid optionName.
>
>   at MacOs this does not works because
>
>      strcmp(optionName, "-sockname") is used
>
>   this is a BUG

thanks.

I fixed this in core-8-3-1-branch and HEAD

I'd be easier if you reported bugs on the SF bug tracker:
https://sourceforge.net/tracker/?func=add&group_id=10894&atid=110894

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/>

Re: [MACTCL] BUG: Tcl8.3.4

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

At 12:58 +0200 on 8/4/02, AO...@t-... wrote:

>   set FILE [glob -directory $DIR *.shlb]
>   >> {Macintosh HD:Desktop Folder:Otto:TcLib:TcLib_auto:libTcLib_auto834.shlb}

glob returns a list! (c.f. man n glob)

you want
	set FILE [lindex [glob -directory $DIR *.shlb] 0]

this is not specific to the mac, but it's more common to have spaces 
in paths on the mac...

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] BUG: Tcl8.3.4

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

Hi,

  just a problem with "glob"

  set DIR {Macintosh HD:Desktop Folder:Otto:TcLib:TcLib_auto}

  set FILE [glob -directory $DIR *.shlb]
  >> {Macintosh HD:Desktop Folder:Otto:TcLib:TcLib_auto:libTcLib_auto834.shlb}

  ATTENTION "{" and "}"

  file tail $FILE
  >>libTcLib_auto834.shlb\}


it seems that {}'s are added


mfg

  aotto :)

Re: [MACTCL] Alias bug?

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

At 3:00 -0300 on 8/4/02, Lizardo H. C. M.  Nunes wrote:

>On "Terminal.app" I tried
>$ alias wish /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell
>So,
>$ wish
>and I got
>"/Applications/Wish: Command not found."
>

you probably wanted:
	alias wish '/Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell'

>I moved "Wish\ Shell.app" for "Wish_Shell.app", etc., and things 
>worked fine. Also,
>$ wish -f myfile.tcl
>is launched.
>
>What I really want to know is how to make "bash" recognize the
>  "#!/usr/local/bin/wish" line.

create a symolic link:
	sudo ln -s /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ 
Shell /usr/local/bin/wish

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] Alias bug?

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

On "Terminal.app" I tried
$ alias wish /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell
So,
$ wish
and I got
"/Applications/Wish: Command not found."

It's probably a bug.

I moved "Wish\ Shell.app" for "Wish_Shell.app", etc., and things worked 
fine. Also,
$ wish -f myfile.tcl
is launched.

What I really want to know is how to make "bash" recognize the
  "#!/usr/local/bin/wish" line.

Probably I'll have to create a link and edit ".bashrc". I'm a Unix 
newbie and suggestions are welcome...

Tcl/Tk is amazing! Thanks,
Lizardo H. C. M. Nunes

[MACTCL] [ANS] Running *.tcl scripts

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

Ok. First of all, "Wish Shell.app"

Second, I realized that
$ /Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell -f myfile.tcl
works.

If there's something else, please let me know.

Thanks,
Lizardo H. C. M. Nunes

[MACTCL] Running *.tcl scripts

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

Just now I started to work with Tcl/Tk.

I could run a couple of scripts with "Whish Shell.app" choosing 
"File>Source..." from Menu. But how can I run Unix scripts beginning 
with  " #!/usr/local/bin/wish" ?

Thanks,
Lizardo H. C. M. Nunes

[MACTCL] BUG: tcl8.3.4

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

Hello,

  a valid socket file-handle adds "-sockname" to fconfigure.
  in unix and windows the test on this option is based on

     strncmp(optionName, "-sockname", len)

  which allows -s, -so, .. -sockname as valid optionName.

  at MacOs this does not works because

     strcmp(optionName, "-sockname") is used

  this is a BUG


mfg

  aotto :)