Re: Re: The components of Archetypes

Martin Aspeli wrote:
> So I see two options:
> 
>  1. Try to evolve Archetypes from the current model into a more modern 
> Z3  one.
> 
>  2. Try to document how to do things people are used to do with 
> Archetypes  with Z3, cataloging patterns and best-practice, and at the 
> same time  factor things out of Archetypes that are missing in the pure 
> Z3 world in  such a way that they may be usable there.
> 
> I'm leaning heavily towards 2. 

I agree with the attraction of 2. I'm coming from the other direction, 
not using AT right now, but hoping to gain from AT's cool stuff and 
experience in Z3/Five land. I am hoping eventually we'll end up using 
the same stuff. :)

I think Five has taken a route like your 2 for Zope 3 stuff in Zope 2. 
Instead of trying to evolve the Zope 2 stuff directly, we worked around 
it by adding Zope 3 stuff as an alternative way to do things, and in the 
end we end up evolving Zope 2 too. :)

So, I think 1 and 2 aren't that far apart sometimes.

Additionally, I think sometimes doing some of 1 can be beneficial to 2. 
In particular, it may be worthwhile to start supporting Z3 widgets in 
Archetypes (I read somewhere that plone_schema makes this possible 
already? Cool!). In that case, it may make sense to adapt Archetypes to 
support them, in turn stimulating people to port their widgets, or write 
new widgets that way at least. That way, they get immediate 
functionality while doing the right thing for future development, and Z3 
gets lots of cool new widgets.

Regards,

Martijn


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click