Andreas Kupries wrote:

> > I don't think it really *requires* it (though I'm sure it .icns
handling
> > would be nice). It just means you do a:
> >
> >  file copy $userfile Appname.app/Contents/Resources
> >
> > At the end of the application bundle creation process. Then a one-line
> > entry in Appname.app/Contents/Info.plist so the OS knows which icns
> > file to show.
> >
> > Tclapp doesn't really need to know anything about the file format of
> > the icon at any stage.
> 
>  I believe you are forgetting that the GUI of TclApp shows the contents
>  of the selected icon file.

As a Tclapp user, I've got to say I'd much prefer the icon bundling
functionality was there and Tclapp for Mac simply produced a generic
placeholder image where the icon image would normally be.

Use a metaphor and it'd look fine: green traffic light for found file, red
for no icon listed by user, and it wouldn't be too out of place :-).

Another thing to add:

On Mac, the Kit Info tab is blank apart from the Prefix File entry. On
Windows in v3.2 (haven't checked 4.0beta yet), this has all sorts of
generic data items.

Mac has similar info to input and it would be nice to see that also go
into the same location. The data ends up as XML entries in Info.plist
after application bundling.


-PC.