On Friday 07 December 2001 13:15, Chuck Esterbrook wrote: > On Friday 07 December 2001 06:05 am, Geoffrey Talvola wrote: > > The WebKit launcher would accept either a "Configs" directory, or > > a > > We could also take the same route that Python and other apps follow > when searching for files: > > - look in standard places > - WebKit/Configs > - ~.WebKit/Configs > > - look in an environment variable > - CONFIGPATH=/etc/configs/webkit
That's the approach I've taken in the experimental code up until now. It's doing it for a single config file, but the idea is the same. Look for ./webkit.config, ~/webkit.config, /etc/... But Geoff suggested that it might be better to require an explicit arg to the start script to make damn sure it doesn't get them from the wrong place. I don't think it's that likely. Nonetheless the launcher script should loudly declare where it is getting its settings from. Personally I like your suggestion of using an env var. If we went with a python package to contain the configs then you could use PYTHONPATH to locate them, unless WEBWAREPATH was set. ... something like that. The big question though is are we talking about 'WebKit' configs or 'Webware' configs??? There's a big distinction there. 'Webware' configs would allow us to deal with the settings for all Webware components in one place. I don't think the local settings for MiddleKit, UserKit, PieInTheSkyKit, etc. should be sitting in the WebKitConfigs directory. Do you? Tavis _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
