From: Gerald W. L. <Ger...@co...> - 2004-04-27 13:34:20
|
Andreas Kupries wrote: > TIP #189: TCL MODULES >======================= > Version: $Revision: 1.2 $ > ... > Alternate suggestion, have an environement variable that contains a list of fully qualified file names that are the "index" of installed modules. When a module is installed at a site, an entry would be modified/added for that module. Ship a command line (tcl) and GUI (tcl/tk) script to register/deregister/update modules. Also provide an API where a script could "register" a new module in the in memory registery. The above has several appealling aspects: 1) It will futher reduce file system access to a nominal three or four files 2) It would allow an administrator to see which modules are installed Since a user could extend the list of the environement variable, they can still add "personal" modules. Since an application can "register" a new module for its run life time, applicatin developers can still have custom modules which their application is decomposed into. -- +--------------------------------+---------------------------------------+ | Gerald W. Lester | "The man who fights for his ideals is | | Ger...@co... | the man who is alive." -- Cervantes | +--------------------------------+---------------------------------------+ |