Two things are happening: 1) When I copy the program out to the clients the stamps are not copied (even if I try to copy them as a separate application) and the program is not configured the way it is on my workstation.
The Stamps Installer places the stamp files in the user's '~/Library/Application Support/TuxPaint' folder, which means the stamps have to be installed separately for every user (and hence for every user on every workstation as well). I think a more sensible thing is to install the stamps direclty into the TuxPaint application bundle; then the stamps are available for all users, and the stamps will also be distributed when TuxPaint is copied to other workstations. I can write a new Applescript installer for this (the installer would replace the current stamps installer).
2) When I look for Tux Paint in order to give the permissions to the workgroups , permission is given to something that appears as com.apple.creatorcode.???? on the list of permitted applications even tho I am selecting Tux Paint on my workstation. (I have figured out a work-around for this, but it would still be nice to know what is happening.)
TuxPaint does not have a creator code assigned to it. On OS X, Creator Codes are four letter codes that associate documents with an application (like the three letter file extension used commonly on Windows and Linux), so that a document can be opened in the correct program when double-clicked. Since TuxPaint does not produce any double-clickable documents (all documents are handled internally via the document browser when you click open), TuxPaint has no creator code and OS X assigns a default code of ????. I don't think this should be of any concern.
I hope there is a fix, We really love Tux Paint--all the kids who have t ried it are very enthusiastic and we have lots of ideas for projects. It's really a great product.
Thanks, Linda
Martin
_______________________________________________ Tuxpaint-dev mailing list [EMAIL PROTECTED] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
