🚀 go-pugleaf

In article <1992Apr12.232626.2319@wcraft.wimsey.bc.ca> jchin@wcraft.wimsey.bc.ca writes:
>In article <sadbkINNsn9@agate.berkeley.edu> izumi@pinoko.berkeley.edu  
>(Izumi Ohzawa) writes:
>While we're bitching ...
>
>I am quite annoyed by application software that keep their sample files,  
>demo files, and other non-directly related stuff in the *.app wrapper  
>which are almost always kept in /LocalApps residing on the aforementioned  
>filesystem. For consistency sake, why not keep them in the  
>/LocalLibrary/Documentation/... folders? Besides the application  
>executables and configuration files, help files should be the only other  
>files allowed to reside in the wrapper.

The other reason not to do this , is performance.  The Workspace scans
all the files in /LocalApps to build its icon and program information.  
Lots of files can cause poor login performance.  I know someone that had
all of coexist in /LocalApps (not recommended by the vendor) and
login time took a little while.
>
>Back to the original complaint about stray files in home folders, I prefer  
>the ~/Library/<application_name> approach. It is clean and easy to manage  
>and far enough out of the way of the home folders that the (expert) users  
>don't have to see it all the time.
>
I like it.  But then, I don't know what the real answer is supposed to be.

-- 
Joe Freeman	jfreem@uncecs.edu
		jfreeman@next.com (NeXT Mail)
The opinions espressed here are my own and are not shared by my employer  or
anyone else I know of.  Flames can be mailed to me or routed to /dev/null.