Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!udel!ee.udel.edu
From: new@ee.udel.edu (Darren New)
Newsgroups: comp.sys.amiga
Subject: Re: Command path question posted as 'Re: CDTV disk'
Message-ID: <27722@nigel.ee.udel.edu>
Date: 17 Aug 90 13:06:57 GMT
References: <4562@jato.Jpl.Nasa.Gov> <3539@leah.Albany.Edu> <1990Aug16.204607.24642@msuinfo.cl.msu.edu>
Sender: usenet@ee.udel.edu
Organization: University of Delaware
Lines: 40
Nntp-Posting-Host: estelle.ee.udel.edu

In article <1990Aug16.204607.24642@msuinfo.cl.msu.edu> jap@convex.cl.msu.edu (Joe Porkka) writes:
>I think that the idea is to allow a data file to simply give the name
>of the tool. Then all of those #?.doc files would have "More" as
>their default tool, rather than ":more" or "sys:utilities/more".

The easiest way to do this would be to have an icon that has in it's 
ToolTypes a list of directories where WorkBench tools might be found and
a list of equivalent programs (less==more, uShow==ShoWiz, ...).
Then that tool, when double-clicked, would go through you disk and do
the following:

1) If the file is a directory, recurse
2) If the file is not a project .info file, iterate
3) If the file has a complete path in the default tool, check that the
   pointed-to file is an executable. If not, strip off the path.
4) If the project can be found in the same directory as the tool, save the
   full path and iterate.
4) If the resulting name is on the left side of an assignment in the ToolTypes
   list of the fixer program, replace it with the right-hand side and iterate.
   Hence, I could change all the "less" programs to "more" with
     LESS=SYS:UTILITIES/MORE
5) If the resulting name is not on the left side, look through the list of
   directories to see if can be found. Hence, we don't need to list every
   program in the Utilities directory as an alias.
6) If the tool for this project still isn't found, look in parent directories
   for it. Hence, any ILBMs saved in (say) subdirectories of DPaint will be
   able to find DPaint as their tool.

It really bugs me that programs insist on clobbering stuff in the icons when
saving files. For example, I carefully save the complete path to the VoRecOne
recognizer (which works much better with one of those little foam wind blockers,
BTW), and the next time I save the file, the path gets screwed. Especially years
after CBM came out with the guidelines on when to muck with the path in an icon.
As usual, if I had all the time in the world, I would do this myself. :-(
		    -- Darren



-- 
--- Darren New --- Grad Student --- CIS --- Univ. of Delaware ---