On Thursday 06 December 2001 15:04, you wrote: > On Thu, Dec 06, 2001 at 03:34:29PM -0800, Tavis Rudd wrote: > > If we just make WebKit and all other Webware components > > """import webware_config""" to get their settings we can use a > > single 'webware_config.py' module or 'webware_config/' package. > > Both look the same to Python. WebKit would have settings in > > webware_config.WebKit, UserKit would have them in > > webware_config.UserKit, and so on. If we use the 'class > > whatever:' scheme you suggested, the settings for WebKit could be > > in the module webware_config.WebKit OR the class WebKit in the > > module > > webware_config. The settings for AppServer could be in > > the module webware_config.WebKit.AppServer or in the class > > AppServer inside the webware_config.WebKit module. And so on ...
> As long as the config files are kept in separate directories from > the Webware modules. We want a directory structure that's split > according to "who maintains this file", and being able to update > Webware by simply unrolling a tarball. Of course. That's my major complaint about how it works at the moment. > > class WebKit: > > class AppServer: > > port = 8080 > If the Python parser accepts this. I like Python config files over > custom ones. Same here. Chuck and Geoff said the same. _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
