Re: [Zope-CMF] Re: Re: CMF roadmap update

2006-04-26 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26 Apr 2006, at 07:40, Martin Aspeli wrote: On Tue, 25 Apr 2006 20:21:09 +0100, Martin Aspeli <[EMAIL PROTECTED]> wrote: On Tue, 25 Apr 2006 16:33:01 +0100, David Pratt <[EMAIL PROTECTED]> wrote: Hi Jens. Z3 has it own uid facilities. I g

Re: [Zope-CMF] Re: Re: CMF roadmap update

2006-04-26 Thread Alec Mitchell
CMFEditions makes heavy use of CMFUid, though if an alternate preferred uid generation mechanism were decided upon, it likely wouldn't be hard to switch. Alec On 4/26/06, Jens Vagelpohl <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > On 26 Apr 2006, at 07:40, Ma

[Zope-CMF] Re: CMF roadmap update

2006-04-26 Thread yuppie
Tres Seaver wrote: Paul Winkler wrote: I saw Philip W. do a working prototype of this at the PyCon Dallas sprints. I don't know if anything happened with this after PyCon, and it would need at least some UI work. If the UI is to integrate with the CMF skins tool, I suspect there will need t

[Zope-CMF] CMF Collector: Open Issues

2006-04-26 Thread tseaver
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/CMF). Assigned and Open jens - "CachingPolicyManager: Support OFS.Cache.CacheManager", [Accepted] http://www.zope.org/Collectors/CMF/408 - "CachingPolicyManager: Make Ma

Re: [Zope-CMF] Re: CMF roadmap update

2006-04-26 Thread Stefan H . Holek
I am using it rather heavily. The "overengineery" impression comes from the fact that it is intended to be highly pluggable (CMF-style, i.e. by replacing tools). For example I always replace the generator with something more robust than a simple counter. Using it is straight forward, you ju

Re: [Zope-CMF] Re: CMF roadmap update

2006-04-26 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26 Apr 2006, at 09:38, Stefan H.Holek wrote: I am using it rather heavily. The "overengineery" impression comes from the fact that it is intended to be highly pluggable (CMF- style, i.e. by replacing tools). For example I always replace the

[Zope-CMF] Re: CMF roadmap update

2006-04-26 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: > Tres Seaver wrote: > >> Paul Winkler wrote: >> >>> >>> I saw Philip W. do a working prototype of this at the PyCon Dallas >>> sprints. >>> >>> I don't know if anything happened with this after PyCon, >>> and it would need at least some

[Zope-CMF] Re: CMF roadmap update

2006-04-26 Thread Rocky Burt
On Wed, 2006-26-04 at 05:44 -0400, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > yuppie wrote: > > Tres Seaver wrote: > > > >> Paul Winkler wrote: > >> > >>> > >>> I saw Philip W. do a working prototype of this at the PyCon Dallas > >>> sprints. > >>> > >>> I don't know

[Zope-CMF] [dev] 'request' in expression context

2006-04-26 Thread yuppie
Hi! In createExprContext 'request' is currently set to getattr(object, 'REQUEST', None). 'object' might be None, making 'request' None as well. Would anybody mind if I change that to getattr(portal, 'REQUEST', None)? AFAICS portal is always available and can acquire REQUEST. If there are n

[Zope-CMF] CMFFolderExport Add-on Available

2006-04-26 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Overview The implementation is dirt simple: it just leverages the "content space" export import facilities of GenericSetup, including the stock adapters registered by GenericSetup and CMFCore. If you don't like the filesystem representation those