On 7/12/05, Tres Seaver <[EMAIL PROTECTED]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> I've uploaded a draft of a roadmap for CMF 2.0:
> Please comment there, or follow up here.
Well... I don't really understand the purpose. I know, you write it on
the roadmap, it's to make a smooth migration path to Zope3, but how
does this help more sepcifically?
Currently, you can write Five products and run them under CMF. The
difference between Five products and Zope3 products will get smaller
and smaller. Very little of this will have anything to do with CMF,
although some things will definitely be needed:
* Interfaces for everything in CMF is one good thing.
* Another is the coming support for local utilities in Five, which
needs CMF portals to be a Zope3 site. That could also expand so that
the portal_tools of CMF are registered also as local utilities, so
that you get the tools via getLocalUtility and not via getToolByName.
But all of this are pure add-ons to CMF as of today, and can easily be
implemented in CMF 1.6. So I guess I don't really see what a 2.0 could
give us. I sure don't mind a rewrite of CMF with Five technologies,
but is that really the best way to spend our energy?
Convince me. :)
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests