[Zope-CMF] Re: CMFSetup profile changing
Hi Florent! Florent Guillaume wrote: By the way will you (or others) be at EuroPython ? It would be nice to discuss plans for CMFSetup face to face. I'll not make it to Göteborg and I'm not sure who the 'others' interested in CMFSetup development are. But I have many plans for CMFSetup and would love to hear your plans and to discuss them. Unfortunately I can't make this work part of one of my customer projects, so I can't spend as much time on CMFSetup development as I would like to. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: CMFSetup profile changing
By the way will you (or others) be at EuroPython ? It would be nice to discuss plans for CMFSetup face to face. Florent yuppie <[EMAIL PROTECTED]> wrote: > Florent Guillaume wrote: > > In the Properties tab of CMFSetup, you can choose an active site > > configuration, among the snapshots and the registered profiles. > > This sets the current context_id for the tool, and loads the import > > steps, export steps and toolset for that configuration. > > > > When you switch to a new base configuration, the import/export steps > > are loaded on top of the current ones without purging. So for instance > > if you: > > - select CMFDefault Site. The import steps now comprise 8 steps. > > - select CMFCalendar. The import steps now have an additional "Various > > Calendar Settings" step. > > - select CMFDefault Site again (or a third-party base (non-extension) > > profile). The Calendar step is retained. > > > > Is this intended ? If yes, why ? My reasoning would be that when you > > import a base profile, you want just that, not what was previously there. > > > > I'll fix that if we agree it's a bug. > > Well. This is still a mess. Loading import/export steps from the profile > did make more sense before I added extension profile support. Now I > would prefer to register *all* handlers on Zope startup. > > The handlers are supposed to do nothing if there are no related > XML-files in the selected profile. But this rule doesn't work with the > provisional handlers in CMFDefault and CMFCalendar because they don't > depend on an XML-file. > > The problem with the fix you proposed is that we currently need a > complete set of import/export handlers for snapshots/exports. Switching > back to the base profile would reset all handlers and make snapshots > incomplete. > > > Cheers, > > Yuppie > > ___ > Zope-CMF maillist - Zope-CMF@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 [EMAIL PROTECTED] ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: CMFSetup profile changing
Hi Florent! Florent Guillaume wrote: In the Properties tab of CMFSetup, you can choose an active site configuration, among the snapshots and the registered profiles. This sets the current context_id for the tool, and loads the import steps, export steps and toolset for that configuration. When you switch to a new base configuration, the import/export steps are loaded on top of the current ones without purging. So for instance if you: - select CMFDefault Site. The import steps now comprise 8 steps. - select CMFCalendar. The import steps now have an additional "Various Calendar Settings" step. - select CMFDefault Site again (or a third-party base (non-extension) profile). The Calendar step is retained. Is this intended ? If yes, why ? My reasoning would be that when you import a base profile, you want just that, not what was previously there. I'll fix that if we agree it's a bug. Well. This is still a mess. Loading import/export steps from the profile did make more sense before I added extension profile support. Now I would prefer to register *all* handlers on Zope startup. The handlers are supposed to do nothing if there are no related XML-files in the selected profile. But this rule doesn't work with the provisional handlers in CMFDefault and CMFCalendar because they don't depend on an XML-file. The problem with the fix you proposed is that we currently need a complete set of import/export handlers for snapshots/exports. Switching back to the base profile would reset all handlers and make snapshots incomplete. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests