Andreas Jung wrote:
for next release we plan to replace several parts with the corresponding components from Zope 3 (e.g. ZPTĀ“). Philipp is working on a proposal on that issue. In addition I would like to get rid of some old stuff that is no longer maintained and buggy:

- ZopeTutorial (could be ripped off without implications and made available
  for download on


- HelpSys - from a programmers view pretty much useless and not very
  helpful. I consider to replace it with something more useful (not sure
  we can re-use apidoc from Zope 3 in some way, perhaps the inclusion
  of Dieter's Docfinder might be more useful for programmers)

+0, it would be useful to not use the explanation texts that are in the help system, or at list check that other material (docstrings, zope book) are at least as comprehensive.

- Gadfly(DA) - do we really need this? We discussed this already. In my
  opinion the purpose of Gadfly is only educational but nothing that one
  really needs or uses for production. It could be removed and made
  available for download on

Gadfly should go, but OTOH have sqlite in its place would still provide SQL inside Zope and that could be a good plus.

And my favourite enemy in Zope: ZClasses :-) I would like to mark them _clearly_ as an obsolete feature (DeprecationWarning, Warnings in the ZMI and the Zope Book). I _don't_ propose to remove them at some point but ppl should be aware that they are using one of the most-scary components in Zope (please no further discussion about the pros and cons of ZClasses..this discussion took already place already a bunch of times on the list).

+1 as I don't use ZClasses and don't intend to maintain them.


Florent Guillaume, Nuxeo (Paris, France)   CTO, Director of R&D
+33 1 40 33 71 59   [EMAIL PROTECTED]
Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to