Thanks for the advice.
I have looked at that before, and having a hybrid ZClass/Python product
seemed to place a lot of design considerations heavily in the python base
class. I've looked _holdOntoYourButts before as well.
> On Tue, 24 Oct 2000 20:16:30 GMT, "Jason Spisak" <[EMAIL PROTECTED]>
> >I am trying to address shortcomings like not having a
> >"dictionary" type property in Zope properties, etc.
> Aha! in that case you dont really need to convert from ZClass to
> python class; you only need to modify your existing ZClass so that it
> has an extra python base class.
> * No need to trawl through your database to convert each instance
> * No need to rewrite the bits that work well as a ZClass
> You can do this using the method _setBasesHoldOnToYourButts defined in
> ZClass.py, and you may be able to find some instructions in the list
> (Its often safer to create a special python base class for each new
> ZClass, even if that class is empty, just in case)
> Toby Dickenson
> [EMAIL PROTECTED]
> Zope-Dev maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -