[Zope-CMF] [dev] CMFSetup add-on support: a rough proposal

[Florent Guillaume]

Hi Yuppie,

While I still couldn't find time to work with CMFSetup, let me say that
I support your goals.

At some point I want to move CPS's configuration to be entirely based on
CMFSetup. For this the main requirement is that some add-on (or
customer) products will want to "update" the setup of the site, changing
only small pieces.

Included in these "updates" would probably also be removal of some
configuration (actions, portal types, workflow transitions, etc). I know
that's not the primary focus of CMFSetup which is mainly a static
description of a site, but as soon as you begin talking about add-ons I
feel this comes into play. But this turns a static file declaration into
a slightly more complex declarations-with-constraints framework...

Florent


yuppie  <y.2005- at wcm-solutions.de> wrote:
> Hi!
> 
> 
> Currently CMF has two machineries for setting up / configuring a site. 
> While the new CMFSetup machinery has replaced the old way to set up 
> complete sites, it doesn't allow to add configuration fragments needed 
> by add-on products.
> 
> A while ago the problem was discussed in this thread:
> http://mail.zope.org/pipermail/zope-cmf/2004-November/021476.html
> 
> 
> AFAICS the following changes are necessary to add basic support for 
> 'profile fragments':
> 
> 1.) extending the ProfileRegistry to allow specifying two different 
> types of profiles: 'base' and 'add-on'
> 
> 2.) not clearing _import_registry and _export_registry if add-on 
> profiles are loaded
> 
> 3.) distinguishing between registered and available import steps 
> (registered export steps are always available)
> 
> 4.) disabling purge mode for add-on profiles
> 
> 5.) improving the 'skip purge' behavior, adding special merging 
> instructions to the XML if necessary, e.g.:
> 
>      <skins-tool>
>       <skin-path id="*">
>        <layer name="zpt_calendar" before="zpt_content"/>
>        <layer name="calendar"/>
>       </skin-path>
>      </skins-tool>
> 
> This would insert the layer 'zpt_calendar' before 'zpt_content' and 
> 'calendar' at the end of each skin path.
> 
> 
> If there are no objections or better ideas, I'd like to work on this on 
> HEAD and merge it into the 1.5 branch as soon as it is stable enough.
> 
> 
> Cheers,
> 
> 	Yuppie
> 
> _______________________________________________
> Zope-CMF maillist  -  Zope-CMF at lists.zope.org
> http://mail.zope.org/mailman/listinfo/zope-cmf
> 
> See http://collector.zope.org/CMF for bug reports and feature requests
> 


-- 
Florent Guillaume, Nuxeo (Paris, France)   CTO, Director of R&D
+33 1 40 33 71 59   http://nuxeo.com   fg at nuxeo.com