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 CMFC
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 CMFCatalogAware's manage_before* and
manage_after* methods so that it dele
Raphael Ritz wrote:
<--SNIP-->
Now my questions: is the outline given above correct?
At least w.r.t. the big picute?
in a general sense, i think yes.
If so: Having this in place shouldn't this allow for easy
extension to multiple catalogs (like the uid or reference
catalogs from AT) by sim
Jens Vagelpohl wrote:
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
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 co
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
Rob Miller wrote:
Florent Guillaume wrote:
To repost an earlier mail:
The patch I propose to include is:
http://mail.zope.org/pipermail/cmf-checkins/2005-November/007137.html
Could some Plone folks please test that switching to
CMF/branches/efge-1.5-five-compatible instead of CMF/branches/1.
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 conta
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 container deletions. ideal
Florent Guillaume wrote:
To repost an earlier mail:
The patch I propose to include is:
http://mail.zope.org/pipermail/cmf-checkins/2005-November/007137.html
Could some Plone folks please test that switching to
CMF/branches/efge-1.5-five-compatible instead of CMF/branches/1.5 doesn't
cause prob
Rob Miller wrote:
The patch I propose to include is:
http://mail.zope.org/pipermail/cmf-checkins/2005-November/007137.html
Could some Plone folks please test that switching to
CMF/branches/efge-1.5-five-compatible instead of CMF/branches/1.5
doesn't
cause problems in Plone ? This patch just cha
Florent Guillaume wrote:
Rob Miller wrote:
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
Hi!
Rob Miller wrote:
Jens Vagelpohl wrote:
On 12 Nov 2005, at 09:04, yuppie wrote:
GenericSetup is still a moving target. I would not create a branch
for 1.6 before 2.0 has stabilized.
unfortunately i need to move rather quickly to be able to produce a
proof-of-concept for the framework
On Sunday 13 November 2005 05:21 am, Florent Guillaume wrote:
> Rob Miller wrote:
> > 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
On 13 Nov 2005, at 08:21, Florent Guillaume wrote:
To repost an earlier mail:
The patch I propose to include is:
http://mail.zope.org/pipermail/cmf-checkins/2005-November/007137.html
Could some Plone folks please test that switching to
CMF/branches/efge-1.5-five-compatible instead of CMF/branc
Rob Miller wrote:
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 d
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 t
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
strictly-
Guys, I'm weeping... we're actually talking to each other. :-)
Martin
On Sat, 12 Nov 2005 18:26:22 -, Florent Guillaume
<[EMAIL PROTECTED]> wrote:
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 ma
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 t
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.
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 to use XML import
-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 rewrit
23 matches
Mail list logo
