Plone 3.0 对开发者的影响, 请各位先行者发表一下看法
沈崴
Zope 3 的整合等。
请各位先行者不吝发表自己的见解。
张炳凯
原文：http://theploneblog.org/blog/archive/2007/03/07/march-martin-mythbusting
The idea that Plone is going to stop using Archteypes seems to be
percolating out there in the wild somewhere. As Martin definitively
states: it's not true.
Hi all,
Just in the interest of avoiding confusion and doubt:
The Plone team have no immediate plans to remove Archetypes or
stop maintaining it
Archetypes is alive and well. It has a new, pragmatic and reliable
maintainer in Daniel Nouri. We all use it. Our customer deployments
all rely on it. New documentation is being written for it. Plone's
core content types are all built with Archetypes. Probably 90% of
third party components are built on it as well.
It is true that there are new technologies that overlap in part
with what Archetypes has covered in the past, such as better ways of
making references between content or new ways of generating forms
(especially when those forms are not meant to edit a content object).
As Archetypes evolves, we will standardise on more such technologies
and improve Archetypes' ability to interoperate with other parts of
our stack. This is the way our evolution has always happened.
That does NOT mean that all your AT-based content types will
suddenly stop working. So long as you keep testing your code with the
version of Plone you want it to run with, and listen to deprecation
warnings to pre-empt things being removed (after the standard
two-version deprecation period) all will be well.
In Plone 3, Archetypes has gained a few new features that make
Archetypes content types a bit more fleixble. To my knowledge, "plain"
Archetypes content types should not break in Plone 3.
In other words - this is a big message about nothing. But just
like the "Plone 3 will run on pure Zope 3" myth (also not true!) this
one is dangerous if a number of people believe it to be true.
Regards
Martin
沈崴
译文:
---
关于 Plone 离弃 Archetypes 的街头巷议正在愈演愈烈, 而 Martin 则斩钉截铁: 此乃戏言。
诸公好,
这里来正一下视听。
Plone 工作组尚无立即移除或停止支持 Archetypes 的计划。
Archetypes 活得很好, Daniel Nouri 他们这支勇武可靠的新军正在维护着它。我们都在基于 Archetypes 进行各自
的扩展开发, 新的文档也是籍此。Plone 之核心 Content Types 皆构建于 Archetypes 之上, 而 90% 左右的第三
方组件亦然。
不过 Archetypes 内部确有一些新的替代技术出现。诸如更为优美地在 Content 之间建立 Reference 的新方法, 又如新
的表单 (Form) 生成器 (请设想, 当表单用于面向 Content Object 增删改之外的那些应用)。随着 Archetypes 的
发展, 我们会采用更多的新技术以增强 Archetypes 使之与系统的其他部分协调运作。这便是我们的改良革新之路。
但是这 "并不" 意味着你基于 AT 构建的 Content Types 就会突然停止工作。请坚持在打算兼容的 Plone 版本上继续测试你
的代码, 并倾听 Deprecation Warning, 了解哪些接口即将被淘汰 (在下一个版本中) 一切都会顺利。
在 Plone 3 中 Archetypes 加入了少量的新特性, 其 Content Types 的灵活性略有提高。据我所知, "朴素"
的 Archetypes Content Types 尚不至于在 Plone 3 中挂掉。
基本上, 聊胜于无。但是类似 "Plone 3 将全面支持 Zope3" 那样的神话 (谣言, 又见谣言!) 如果信以为真, 那你就惨了。
> On 3/12/07, 沈崴 <wilei...@gmail.com> wrote:
>
> > 我想了解一下 Plone 3.0 以后, 会对开发造成哪些影响? 比如 Archetypes 在 Plone 3.0 中的变化, 与
> > Zope 3 的整合等。
>
> > 请各位先行者不吝发表自己的见解。
>
> > ---
> > 沈崴
> >http://blog.163.com/eishn
潘俊勇
Plone 3.0的核心代码，逐步移到实例的lib/python目录中了，这里的代码，组织得更好，可重用行更高。
这是Plone发展的趋势，也就是会将代码逐渐转移到lib/python目录中，这个目录中的代码，也是大量用了zope 3的技术。