Hi<br><br>Thanks alot for this.<br><br>I've heard that there are benefits on the security side? That it is to be security audited etc.<br><br>Michael<br><br><div><span class="gmail_quote">On 2/2/06, <b class="gmail_sendername">
Terry Hancock</b> <<a href="mailto:hancock@anansispaceworks.com">hancock@anansispaceworks.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, 02 Feb 2006 00:14:59 +0100<br>Rakotomandimby Mihamina<br><<a href="mailto:mihamina.rakotomandimby@etu.univ-orleans.fr">mihamina.rakotomandimby@etu.univ-orleans.fr</a>> wrote:<br>> On Wed, 2006-02-01 at 15:21 +0000, michael nt milne wrote:
<br>> > Is there a page anywhere which lists the main benefits<br>> > of Zope 3?<br><br>You can find the proposal for it starting from <a href="http://zope.org">zope.org</a>, I<br>don't know the actual URLs, but it's not hard to find by
<br>searching.<br><br>> According to the beginer I am, the benefit is that zope2<br>> will disapear (as well as zope 1, for example...). That's<br>> a good reason to learn zope 3 as soon as possible :-)<br><br>Not so much. Zope 3 is a complete rewrite of Zope, so it's
<br>been existing in parallel with Zope 2 for some time. The<br>Zope 2 branch will probably take quite awhile to die out.<br><br>And don't forget that it's still going to be around, even if<br>they aren't actively developing it. I still have a site
<br>using Zope 2.5.1!<br><br>> The documentation is very slim, I agree, but why not help<br>> with your own little tutos? :-)<br><br>It is indeed spotty.<br><br>This cry "if the documentation is too poor, write your own"
<br>does get kind of old, though. Obviously if you understood it<br>well enough to write documentation, you wouldn't be trying<br>to find it!<br><br>Still, Zope 3 is moving towards being better documented than<br>Zope 2 was. This is mainly a matter of making it
<br>"self-documenting." In practice this often works better,<br>because the "documentation" stays up to date. A big problem<br>with earlier versions was documentation that was out of<br>synch with the releases.
<br><br>The *big event* with Zope 3 is the redesign to an "interface<br>+ components" architecture. This makes Zope 3 more like a<br>"tool box" than a "framework" which is generally regarded as
<br>a good thing. There is, of course, a "framework" called<br>"Zope 3" which is built from this "tool box", but it's much<br>easier to deconstruct Zope 3 and combine it with other<br>Python modules.
<br><br>This is a really big win from the standpoint of the Python<br>"Zope Product" developer, who's looking to adapt a bunch of<br>pieces together to make a work web application. It's a less<br>obvious win if you just do "through the web scripting".
<br><br>In the latter case, in fact, you're probably better off<br>(right now) sticking with the Zope 2.x series, because the<br>TTW interfaces for Zope 3 are still very rough (at least<br>this is what the reports say -- I still haven't really
<br>tested it out).<br><br>What I have done is to browse the Zope 3 source tree, and I<br>have made use of the "interface" and "schema" modules. Very<br>nice stuff! If the rest of Zope 3 measures up to that, then
<br>it's going to be a joy to work with.<br><br>Cheers,<br>Terry<br><br>--<br>Terry Hancock (<a href="mailto:hancock@AnansiSpaceworks.com">hancock@AnansiSpaceworks.com</a>)<br>Anansi Spaceworks <a href="http://www.AnansiSpaceworks.com">
http://www.AnansiSpaceworks.com</a><br><br>_______________________________________________<br>Zope maillist - <a href="mailto:Zope@zope.org">Zope@zope.org</a><br><a href="http://mail.zope.org/mailman/listinfo/zope">http://mail.zope.org/mailman/listinfo/zope
</a><br>** No cross posts or HTML encoding! **<br>(Related lists -<br> <a href="http://mail.zope.org/mailman/listinfo/zope-announce">http://mail.zope.org/mailman/listinfo/zope-announce</a><br> <a href="http://mail.zope.org/mailman/listinfo/zope-dev">
http://mail.zope.org/mailman/listinfo/zope-dev</a> )<br></blockquote></div><br><br clear="all"><br>-- <br>Michael