Re: What does Five and Z3 mean for Archetypes?

hello werewolf...
<snip>
> I intend to start looking at using zope.formlib in Zope 2 through Five. 
> In the Zope 2.9/3.2 world this becomes possible; previous versions of 
> Zope 2 have versions of Zope 3 that are too old. Through this route I 
> hope to get some benefits of Archetypes in Zope 2, while keeping in line 
> with Zope 3 code as well.
> 

geoffd, jim and the zope-corp dev team had a powwow a the end of October 
about CMFFormController (on which AT heavily depends).  The general 
consensus was that they solved some of the same problems, but that one 
of the big use cases for CMFFormController, simple reuse and editing of 
flow state through a sequence of forms was not handled by formlib.

sidnei apparently has had some luck in getting z3 views to use the 
machinery of CMFFormController, but but it would be nice to have unified 
approach throughout the zope world.

> One route I could see is that eventually, once Zope 3 and Five become as 
> full-featured as current AT, we get conversion guides and tools to move 
> from AT to the new story. Tools like AGX can help with this, as they 
> could potentially be used to create Zope 3-based code instead of 
> AT-based code from the same model. Again, as with all things Five, this 
> would be a slow evolutionary process. Since AT is largely declarative 
> already it is more easily convertable to a new system than if it were 
> not, so you're relatively safe sticking with that for the foreseeable 
> future.

indeed. I think at could eventually just provide a system of 
configuration allowing a nice interface to what ever happend to be 
beneath. AGX could utilize this, but for those of us who want to throw 
our computer out the window everytime poseidon freezes, hopefully it 
would be generic enough for those of us who generate our types in emacs.

> It may be that this proposed route is presumptuous towards AT developers 
> however. I am curious to see more discussion of this. Again, one of my 
> important motivation is to make sure the various Zope codebases and 
> platforms can more easily exchange code, so that I can benefit better 
> from your work (and you better from mine). This makes it essential I'm 
> on the same page as the AT developers with this.

well, we have to go in some direction and I for one am glad we have 
drawn your notice ;)

-w



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php