[Zope-CMF] [dev] CMFSetup: simplifying handlers

yuppie y.2004_ at wcm-solutions.de
Fri Dec 3 05:45:11 EST 2004


What's the reasoning behind the current structure of setup handlers?

Why are methods like _extractStateNodes not bound to the Configurator 
class, but e.g. _extractStates?

I propose to factor out some code into a Configurator base class and to 
bind the DOM parsing utility methods (like _queryNodeAttribute) to that 
base class.

Instead of passing around the 'encoding' I propose to make _encoding an 
attribute of the Configurator object.

Any thoughts? Do we need a migration path for some of these methods?

If there are no objections I'll change CMFSetup as proposed.


More information about the Zope-CMF mailing list