Re: [Zope-dev] refactoring site functionality

2009-06-05 Thread Martijn Faassen
Chris McDonough wrote: On 6/4/09 11:59 AM, Martijn Faassen wrote: [snip] I don't think it's complicated. It's nice to install an object somewhere that stores data and has a UI and also be able to register it as a local utility. If you were to have mutable global configuration, you'd need some

Re: [Zope-dev] refactoring site functionality

2009-06-04 Thread Martijn Faassen
Wichert Akkerman wrote: Previously Martijn Faassen wrote: * often it is nice to have application configuration to have a user interface, so that end users can configure aspects of the application. This may be filling in an email address or customizing a template or adding a user, etc.

Re: [Zope-dev] refactoring site functionality

2009-06-04 Thread Martijn Faassen
Hi there, Jim Fulton wrote: [snip] I think we're talking about 2 different things. There is the registry that is local to the root object and that is stored in the database. Having registration data in the database makes sense for a number of reasons and I don't consider this

Re: [Zope-dev] refactoring site functionality

2009-06-04 Thread Martijn Faassen
Christian Theune wrote: [snip] I find this pattern to be pretty neutral WRT the web or to locations (as we know them from zope.location). I think you're describing the pattern of (contextual) acquisition? :) Unfortunately, I do have to point to a naming thing: the component lookup methods

Re: [Zope-dev] refactoring site functionality

2009-06-04 Thread Chris McDonough
On 6/4/09 11:59 AM, Martijn Faassen wrote: Wichert Akkerman wrote: Previously Martijn Faassen wrote: * often it is nice to have application configuration to have a user interface, so that end users can configure aspects of the application. This may be filling in an email address or

Re: [Zope-dev] refactoring site functionality

2009-06-04 Thread Wichert Akkerman
Previously Chris McDonough wrote: On 6/4/09 11:59 AM, Martijn Faassen wrote: Wichert Akkerman wrote: Previously Martijn Faassen wrote: * often it is nice to have application configuration to have a user interface, so that end users can configure aspects of the application. This may be

Re: [Zope-dev] refactoring site functionality

2009-05-29 Thread Christian Theune
Hi, On Thu, 2009-05-28 at 17:00 +0200, Martijn Faassen wrote: Hey, [...] P.S. As of this point I'm dropping my proposal to rename anything to anything. Let's indeed focus on the wider discussion (as indicated by Roger and Jim) (I'm not directly proposing a naming here, I'm just dumping

[Zope-dev] refactoring site functionality

2009-05-28 Thread Martijn Faassen
Hey, Jim Fulton wrote: 2. I think local configuration address use cases that most people don't have but introduce complexity that I bet a lot of developers trip over. I think there are two cases where people typically deal with local configuration: * setting up local utilities (for

Re: [Zope-dev] refactoring site functionality

2009-05-28 Thread Wichert Akkerman
Previously Martijn Faassen wrote: * often it is nice to have application configuration to have a user interface, so that end users can configure aspects of the application. This may be filling in an email address or customizing a template or adding a user, etc. Local utilities are a nice

Re: [Zope-dev] refactoring site functionality

2009-05-28 Thread Roger Ineichen
] refactoring site functionality Previously Martijn Faassen wrote: * often it is nice to have application configuration to have a user interface, so that end users can configure aspects of the application. This may be filling in an email address or customizing a template or adding a user

Re: [Zope-dev] refactoring site functionality

2009-05-28 Thread Stephan Richter
On Thursday 28 May 2009, Roger Ineichen wrote: btw, you are pointing to a good direction. Didn't we talk about reload global configuration during runtime years ago? BTW, plone.reload looks really promising. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter