-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15 Jan 2007, at 17:00, Rocky Burt wrote:
On Mon, 2007-08-01 at 15:40 +0100, Philipp von Weitershausen wrote:
Since Five is feature-frozen and new stuff should be added in Python
packages anyway, my suggestion is to put this thing into a
five.lo
Rocky Burt wrote:
> On Mon, 2007-08-01 at 15:40 +0100, Philipp von Weitershausen wrote:
>> Since Five is feature-frozen and new stuff should be added in Python
>> packages anyway, my suggestion is to put this thing into a
>> five.localsitemanager package which would then be used by CMF 2.1, Plone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15 Jan 2007, at 17:00, Rocky Burt wrote:
On Mon, 2007-08-01 at 15:40 +0100, Philipp von Weitershausen wrote:
Since Five is feature-frozen and new stuff should be added in Python
packages anyway, my suggestion is to put this thing into a
five.lo
On Mon, 2007-08-01 at 15:40 +0100, Philipp von Weitershausen wrote:
> Since Five is feature-frozen and new stuff should be added in Python
> packages anyway, my suggestion is to put this thing into a
> five.localsitemanager package which would then be used by CMF 2.1, Plone
> 3, etc.. It could p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8 Jan 2007, at 23:54, Martin Aspeli wrote:
Philipp von Weitershausen wrote:
a) somehow bundle CMF 2.1 (and Plone 3) with a package called
five.localsitemanager. Given that Plone 3 already has plone.*
packages (and I assume they also want fi
Philipp von Weitershausen wrote:
a) somehow bundle CMF 2.1 (and Plone 3) with a package called
five.localsitemanager. Given that Plone 3 already has plone.* packages
(and I assume they also want five.customerize), this might probably be
less of an issue for Plone than for the CMF.
This is no
Philipp von Weitershausen wrote:
Jens Vagelpohl wrote:
CMF won't come eggified for this release, that work has stalled.
whit wrote:
plone's egg story looks non-existent until next release.
Right, I figued as much. Also, it's only for Zope 2.11 that we can
actually tackle sensible egg suppo
Jens Vagelpohl wrote:
CMF won't come eggified for this release, that work has stalled.
whit wrote:
plone's egg story looks non-existent until next release.
Right, I figued as much. Also, it's only for Zope 2.11 that we can
actually tackle sensible egg support in the Zope 2 core, so that mak
plone's egg story looks non-existent until next release.
-w
___
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8 Jan 2007, at 19:40, Philipp von Weitershausen wrote:
Me neither. I'd just like to avoid that either CMF or Plone or both
grow their own implementations. The problem is completely generic
to Zope 2, hence we should have an independent package
On 8 Jan 2007, at 17:30 , Rocky Burt wrote:
On Mon, 2007-08-01 at 15:40 +0100, Philipp von Weitershausen wrote:
Using PersistentComponents() as the component registry (a.k.a. site
manager) for local sites isn't enough. That's because it doesn't
understand about containment hierarchies. Imagine t
While I don't have time at this very moment to address this in great
detail, I will mention a few comments.
On Mon, 2007-08-01 at 15:40 +0100, Philipp von Weitershausen wrote:
> Using PersistentComponents() as the component registry (a.k.a. site
> manager) for local sites isn't enough. That's be
12 matches
Mail list logo
