[Zope-CMF] Re: backporting GenericSetup to CMF-1.5

2005-11-15 Thread Rob Miller
Raphael Ritz wrote: Rob Miller wrote: [..] to be fair, AT's (un)indexing code is a mess... i tried to change the BaseFolderMixin manage_(after|before)* methods so they explicitly call the PortalFolder implementations and was still ending up w/ subobject orphans left in the catalog after

[Zope-CMF] Re: backporting GenericSetup to CMF-1.5

2005-11-15 Thread Raphael Ritz
Rob Miller wrote: [..] you're more than welcome to either pitch this to plone-devel or to grab it by the horns and start working on it yourself. :-). Hi Rob and all other CMF developers, I know I'm getting myself in danger now as I know too little yet about Zope 3 and I have no practical

Re: [Zope-CMF] Re: backporting GenericSetup to CMF-1.5

2005-11-15 Thread Jens Vagelpohl
On 15 Nov 2005, at 02:56, Rob Miller wrote: to be fair, AT's (un)indexing code is a mess... i tried to change the BaseFolderMixin manage_(after|before)* methods so they explicitly call the PortalFolder implementations and was still ending up w/ subobject orphans left in the catalog after

Re: [Zope-CMF] Re: backporting GenericSetup to CMF-1.5

2005-11-15 Thread Alec Mitchell
On Tuesday 15 November 2005 10:43 am, Rob Miller wrote: Florent Guillaume wrote: Rob Miller wrote: CatalogMultiplex is a subclass of CMFCatalogAware which overrides the (un/re)indexObject methods to perform operations in multiple catalogs, if necessary. your patch changes

Re: [Zope-CMF] Re: backporting GenericSetup to CMF-1.5

2005-11-12 Thread Jens Vagelpohl
On 12 Nov 2005, at 09:04, yuppie wrote: A CMF 1.6 release that requires Zope 2.8 and essentially bundles CMF 1.5 with GenericSetup 2.0 (and compatible CMF setup handlers) might be a good idea. Yes, that's a good idea. It certainly can't go directly in the strictly-maintenance 1.5 branch.

[Zope-CMF] Re: backporting GenericSetup to CMF-1.5

2005-11-12 Thread Florent Guillaume
yuppie wrote: Hi Rob! Rob Miller wrote: those of us planning out the next Plone releases are in a bit of a bind. we really want to make use of GenericSetup's newer Z3-interface-based means of defining import and export handlers, so that we can start work on rewriting our migration engine

[Zope-CMF] Re: backporting GenericSetup to CMF-1.5

2005-11-12 Thread Rob Miller
Jens Vagelpohl wrote: On 12 Nov 2005, at 09:04, yuppie wrote: A CMF 1.6 release that requires Zope 2.8 and essentially bundles CMF 1.5 with GenericSetup 2.0 (and compatible CMF setup handlers) might be a good idea. Yes, that's a good idea. It certainly can't go directly in the

[Zope-CMF] Re: backporting GenericSetup to CMF-1.5

2005-11-12 Thread Rob Miller
Florent Guillaume wrote: +1 on branching CMF 1.6 soon, with the goal of: - dropping support for Zope 2.7 - allowing Five 1.2 events activated to work, even if it doesn't *require* Five 1.2 events - be closer to CMF 2.0 w.r.t. setup. this is perfect for us. there doesn't really need

[Zope-CMF] Re: backporting GenericSetup to CMF-1.5

2005-11-11 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rob Miller wrote: those of us planning out the next Plone releases are in a bit of a bind. we really want to make use of GenericSetup's newer Z3-interface-based means of defining import and export handlers, so that we can start work on rewriting