Re: Configuration

On Jan 2, 2006, at 4:58 PM, Julian Fitzell wrote:

> Well, you used to be able to subclass Application but I have a  
> feeling this was deprecated in favour of subclassing session and  
> renderloop... The new configuration stuff never really got fully  
> fleshed out...

So the 2.5 configuration stuff was being reworked for 2.6, but is  
somewhat stalled? Or is that not really going to be a feature in 2.6?

I never used the 2.5 stuff, but now I would like to ;)

Brian
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Well, no, I think it was somewhat stalled even in 2.5.  The idea was to
make it easier to specify configuration in files so that the same image
could be deployed on a test server and a live server for example, or a
new image could be deployed in place and take up the configuration the
previous image was using.

We wanted to make it easy to define site-wide preferences and then have
applications be able to override individual options.

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.

Julian

Brian Brown wrote: _______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

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.

Avi
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside