[Seaside] Configuration

Avi Bryant avi.bryant at gmail.com
Fri Jan 13 10:42:21 CET 2006

On Jan 12, 2006, at 9:13 AM, Julian Fitzell wrote:
> The inheritance was there but we never really got to the file part  
> and never had a good UI for dealing with these inherited properties  
> so it never got used.  Avi was talking about stripping down the  
> inheritance model and making it simpler but to be honest I'm not  
> sure where, if anywhere, that got to.

The latest versions of Seaside 2.6 do have the stripped down model.   
Effectively what's gone is the user-entered site-wide defaults; you  
can have as many levels of programmatic defaults in the code as you  
like, but you only get to manually override at the application level.

Note the "programmatic" - one thing that works fairly well for site- 
wide defaults is to have code in a SystemConfiguration subclass that  
looks at its environment (for example, what working directory the  
image is in or the contents of some files) and sets the defaults  
accordingly.  What I've found myself doing is having those  
programmatic defaults get used in the production environment, and  
then using app-level overrides in the development environment which  
doesn't have all the right config files etc around.


More information about the Seaside mailing list