Subj : load() search paths...
To   : Deuce
From : Digital Man
Date : Wed Aug 12 2009 05:31 pm

  Re: load() search paths...
  By: Deuce to Digital Man on Fri Aug 07 2009 10:34 am

 >   Re: load() search paths...
 >   By: Digital Man to Deuce on Thu Aug 06 2009 04:01 pm
 >
 >  > exec/
 >  >   login.js
 >  >   logon.js
 >  >   listserver.js
 >  >   nntpservice.js
 >  >   etc.
 >  > exec/include
 >  >   *defs.js
 >  >   *lib.js
 >  >   *util.js
 >  >
 >  > where 'exec' can be replaced with 'mods' (and is searched first), as is
 >  > the current scheme.
 >
 > Yeah, but I like the idea of allowing it to be deeper.  As for include/lib,
 > I'm not overly fond of either one to be honest... exec/load perhaps?

Yeah, I like exec/load (and by extension, mods/load).

 > I'm also very fond of the idea of adding a directory under the exec/mods
 > dir to group related files together... while I expect 3rd party scripts to
 > be added to the mods directory rather than exec, a bit of grouping may
 > help.  The question of course is how to group everything.

Wouldn't that be up to the 3rd party developers? I don't know how we could
enforce a grouping.

                                            digital man

Snapple "Real Fact" #57:
You blink over 10,000,000 times a year.

.