On Sunday, 7 March 2004 2:15 PM, Laurent SIEBENMANN <lcs@...> wrote: > > > it is still too risky to start > > recursing through nested folder structures. > >I don't understand why. If one can merely be 100% sure that >what is being deleted is trash, then one is safer than the >user of Finder's 'Empty Trash' button. Now, why is one not >sure? I am 100% sure that you can never be 100% sure :-> Usually I write defensive code (when deleting), and in this situation, I cannot think of any technique that will identify what _is_ trash. Trash tends to look alot like the rest of the contents of a hard drive. > >The app needs to be *useful* to get tested and debugged. > As I've said, I was only testing the interface/concept, not functionality. I clearly flagged it as less than prototype stage, merely 'Experiment'. If the interface sits well with me (which it did not in the end), the rest is easy. > > > Alternatively, you can use the old-skool method of removing > > the "INITed" flag from the app (Using resedit), duplicating it to > > another folder, then opening and closing that folder. > >I know these tricks individually, but have never had a 100% >reliable combination; some Finders and some volumes have always >bauked. Distribution with change of creator is failsafe. > This is not a failsafe. If your desktop DB is corrupt, new additions can fail to be added. Rebuilding is not a failsafe either, as the file that houses the desktop db can be in such a state that the only way to fix is to delete the desktop db files, then restart so a fresh file is made. I have even seen utilities that handle this task. If my memory serves me correctly, Easy Open (aka Evil Open), had an option to force the rebuild _every_ time your mac boots! Save a Bundle is noted as being system 7+ <http://www.macupdate.com/info.php/id/7190> > > > And just incase there is any > > confusion - the code runs under pre-OSX only. > >Why not in OSX classic compatibility mode? My pure D&D >"Janitor" design (*) of Mon, 16 Feb 2004 04:10:55 +0100 (MET) >aught to work in OSX, at least if suitably compiled; no jGNE >used. > The Finder does not run under classic, so the jGNE filter I install does not get called for Finder events. The jGNE queue does not seem to extend outside the blue box. Jamin