I can understand wanting to deprecate them, but I have to say, as the
maintainer of a site written by someone else about six years ago in
zope 1 days, that this would be a mess to migrate and require a total
site rewrite. The client is unfortuneatly a non-profit mid-sized
independent press, and this would likely doom them to remain at 2.9
forever...eck, as far as keeping a server going with an increasingly
outdated zope, and probably an outdated python, too...

On Apr 1, 2005 10:15 AM, Lennart Regebro <[EMAIL PROTECTED]> wrote:
> +1 on deprecation.
> 
> (As for "replacements", persistent schemas in Zope3 will enable the
> thing that ZClasses should have been: Combining a set of base classes
> with functionality with a TTW editable schema.
> 
> CPSschemas is halfway there: You can make your own content classes
> already, but you can't change the baseclass. But that's a discussion
> for anotehr day).
> 
> --
> Lennart Regebro, Nuxeo     http://www.nuxeo.com/
> CPS Content Management     http://www.cps-project.org/
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope-dev )
>
_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to