Michel Pelletier wrote:
The objects that PTK come with are stock objects, most of which will be 'ports' of the existing zope site objects. They will change in minor ways, ie, they will use MFI, their interfaces will be more consistent, and their behavior will be analyzed (hopefully by all of you!) to see if they can be made more useful.
Are you planning on having MFI or PortalObjects subclassable by ZClasses? ZClasses that subclass PortalObjects might participate in the PTK system (create, review, reject or publish & catalog) without creating a product. Will there be a SQL Method interface for storing PTK objects in a RDBMS? Or will PTK objects only be storable in the ZODB?
A familiar rhythm I'm looking for is 1) release an alpha, 2) someone points out a problem, 3) that person, using the model, describes exactly how they think it should work. This doesn't mean you have to be a modeler, but you should be able to look at UML and at least be able to say "Class such-and-such defines this method, I think the method should return X". In fact, this doesn't even need UML, you can do this from the source. The model is to make it easer for us all the grasp the big picture.
For those of us that use OD, it would be useful to browse or update your model directly in OD, would you consider releasing the full model rather than the HTML export? Andrew Lahser