---bill lam wrote: > If you want to reuse some common utilities but do not want put > them into the source tab. You may add them to the public > library by modifying the startup.ijs in ~user\config folder, eg > > NB. ========================================================= > NB. PUBLIC classes: > buildpublic_j_ 0 : 0 > utilscripta ~Projects\utils\utilscripta > tara ~addons\tables\tara\tara > )
It seems to me it would be useful to extend this further. Maybe something along these lines: Project Manager could have a couple of extra tabs Source | MyLibrary | AddonLibrary | SystemLibrary | Project | Other SystemLibrary would be the equivalent of the current Library tab and would include scripts that are distributed with J under the System directory. AddonLibrary would list scripts located under the Addons directory. Package Manager could manage this list as it installs new Addons or rebuilds the local repository catalogues. MyLibrary would list scripts specified by the user from other sources. They could add to this using something similar to the current buildpublic_j_ in startup.ijs. The Include Files section of the Build Options dialog would get some more options. So, as an example, you could _include_ scripts from Project source and MyLibraries, but only _require_ Addon libraries and System libraries (as you could expect/direct the end user to have those installed on their system). Options for managing the different lists include: * additional nouns similar to PUBLIC_j_ but with different names, * a 3rd column could be added to PUBLIC_j_ that denoted the library type * anything starting ~system/ is from the System Library, anything starting ~addons/ is from the Addon Library and everything else is from MyLibrary. Does this sound sensible or is it added complexity for little gain? ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
