Sort of; if I have interpreted unofficial statements on the list from DC people correctly, ZClasses replace products in many cases, although very possibly not all; for example, I'm quite certain that most of Confera could have been implemented as a ZClass. Certainly the product API is complex (or undocumented) to an extent which makes ZClass more desirable, moreover from an object-orientated design perspective, products are inferior. (If that is what you asked. If the question was "What is the product interface for?" then the answer isn't "So you can edit properties through the standard management interface," and it isn't "So you can have properties as objects," either.) -- Alexander Staubo http://www.mop.no/~alex/ "What the hell, he thought, you're only young once, and threw himself out of the window. That would at least keep the element of surprise on his side." --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_
-----Original Message----- From: bruce@perens.com [mailto:bruce@perens.com] Sent: 6. juli 1999 07:26 To: alex@mop.no; zope@zope.org Subject: RE: [Zope] Using Zclasses
From: Alexander Staubo <alex@mop.no>
Your second question is trickier, because Zope does not, afaik, support properties that are objects. It's possible, but I believe you can't edit these properties through the standard management interfaces.
Naievely I ask, isn't that what the product interface is for? I must be missing something.
Thanks
Bruce