🚀 go-pugleaf

In article <34776@amdahl.uts.amdahl.com> (Kevin Clague) writes:
->  3.  Using the name string and the file lock (and Examine() and
->      ParentDir()) I create a string that contains the full path name
->      of my program.  This tells me where the user has put my program
->      before executing it.   Later I use this as the ToolType in any
->      project Icons that are written to disk.

Not the ToolType, should be in the DefaultTool pointer.

->  5.  When the user saves projects to disk, if the program was started
->      from the CLI, I don't create icons for it.  If started from the
->      WBench I write out icons using the freshly created tooltype
->      string created in step 3.

You should also check to see if the icon already exists, and if so *not*
overwrite it. (The user may have customized it) Also see the comment 
above about where the default tool goes. 

->  I'm a CLI kinda guy.  The WorkBench stuff is all new to me.  Is this
->the proper approach?  Am I working too hard at the ToolType stuff?
->Does the system handle this in some other kinda way?  Am I missing
->anything?  Inquiring minds WANT to know!
->  -kevin

Seems like you are right on track. Wish more people would consider it for
their programs.

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.