OK, some initial, fuzzy comments:
On 2/27/06, Jim Fulton <[EMAIL PROTECTED]> wrote:
> In this vision, Zope 3 would have to become a lot more like
> Zope 2, or we would lose features.
You are thinking about things like TTW development and such? Because I
see that as add-on products of different kinds. Like cpsskins to
develop the look, and some sort of persistent schemas combined with
some sort of aspect-oriented classes. ;-)
If there is some sort of real "core" thingy that you lose going from
Zope2 to Zope3 I must have missed it. :-p
> 2) In an alternate vision, Zope 2 evolves to Zope 5.
> - Zope 5 will be the application server generally known as Zope. It
> will be backward compatible (to the same degree that Zope 2
> releases are currently backward compatible with previous Zope 2
> releases) with Zope 2. Zope 5 will similarly be backward
> compatible with Zope 3 applications built on top of the current
> Zope 3 application server.
> Note that Zope 5 will leverage Zope 3 technologies to allow a
> variety of configurations, including a Zope 2-like configuration
> with implicit acquisition and through-the-web development, and a
> Zope 3-like configuration that looks a lot like the current Zope
> 3 application server. Maybe, there will be a configuration that
> allows Zope 2 and Zope 3 applications to be combined to a
> significant degree.
This overwhelms my complexity sensor. :-)
I like the vision of Zope2 becoming a set of extra packages you
install for Zope3, to get backwards compatibility. Maybe this is the
same as what you call Zope 5, maybe not.
> - There wouldn't be confusion about 2 Zopes.
This is definitely true...
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
Zope3-dev mailing list