[Zope-CMF] Re: CMF 2.0 Release Status

[Martin Aspeli]

Hi,

On Wed, 11 Jan 2006 18:42:08 -0000, Tres Seaver  
<tseaver at palladion.com> wrote:

> I'd like to review the current status of a number of the CMF 2.0 roadmap
> items, and ask for feedback from the community on how they fit into a
> near-term release of a beta for CMF 2.0. In fact, I would like to
> release an alpha this weekend, followed by a more-or-less feature
> complete beta by the end of the month.  I have "posted a blog entry,",
>  http://palladion.com/home/tseaver/obzervationz/2006/cmf_2_0_update_20060111
> summarizing what I think is the current status of the project.  Please
> comment here on ths list, correcting my mistakes or omissions, as well
> as responding to the "open questions" section.

I had a browse through the code at  
http://svn.zope.org/CMF/trunk/CMFCore/interfaces. This work is interesting  
to me not at least because it will enable us to write against CMF (and  
hopefully Plone soon) code using Z3 idioms (e.g. accessing things through  
interfaces, making it possible to use adapters etc.) I think the migration  
path here has to be to get all the interfaces in place first, and then  
gradually refactor code to work through these interfaces as necessary.

However, I notice that none of the manage_* methods are not there, and  
that many things have accessors only. I haven't looked at it in the  
detail, but I'm wondering what the policy is here. For things like setup  
scripts or control panel views or whatnot, being able to mutate the values  
in tools (http://svn.zope.org/CMF/trunk/CMFCore/interfaces/_tools.py) and  
elsewhere (e.g. just setting dumb properties) would seem a necessary of  
the interface. Am I missing something?

Martin

-- 
(muted)