[Zope3-dev] Re: Zope 3 Roadmap thoughts

[Gary Godfrey]

In article <3E37C327.1070506@zope.com>, Jim Fulton wrote:
>> Paul Everitt wrote:
>>> Jim Fulton wrote:
>>> [deleted]
>>> For Zope 3.0:
>>>
>>>    Note that Zope 3.0 will provide support for migrating
>>>    Zope 2 data and applications to Zope 3. This will probably take the
>>>    form of migration tools, rather than direct backward
>>>    compatability.
>> 
>> 
>> Can you describe this more? 
> 
> Not really. The reason is that we made a concious decision not
> to be distracted by backward compatability during the design of 3x.

I guess what I would wonder is what type of constructs are likely to
migrate easily and which are going to be difficult.  I suspect that
the z3 architecture is far enough along that items in the z2/z3 
"compatability framework" (for lack of a better term) could be
roughly outlined.  For instance, one product I have requires
the following (quick glance):

- Formulator
- context.registerClass/registerBaseClass
- meta_type
- manage_options
- SimpleItem.SimpleItem
- REQUEST.RESPONSE.redirect
- REQUEST.form has form items (int: translation, etc.).
- PageTemplateFile / Page Templates
- here/manage_page_header / here/manage_tabs
- html_quote 
- index_html is called by default on a folder.
- Z SQL Methods

Not a big list.  Of course, Formulator is far bigger than my stuff.

What I would look for is a "best practices for Zope2 development" which
outlines constructs which would migrate easily to Zope3.  In some cases,
it might make sense to move some Zope3 functions to Zope2 in order to
provide a platform for products to move forward.

Gary Godfrey
Austin, TX USA