Would this approach be appropriate? http://dev.zope.org/Members/Caseman/Dynamic_HotFix_News/Dynamic_Hotfix
From: "Ulrich Eck" <ueck@net-labs.de> Date: Wed, 11 Jul 2001 19:33:15 +0200 To: "ZOPE-DEV Mailingliste" <zope-dev@zope.org> Subject: [Zope-dev] Patching Zope Products .. next Question
can I do this with: -- import Products.CMFCore.PortalContent
<<define myclass here >>
InitializeClass(<<myclass>>) Products.CMFCore.PortalContent.PortalContent = <<myclass>> --
ok this works but there is another tricky thing now ...
I need to patch two products: CMFCore and CMFDefault.
first i patch CMFCore and I think this works (at least a portalfolder is a customizerfolder :)
I have now 2 new Classes PortalFolder and PortalContent ..
but
the CMFDefault.Document for example is still subclassed from CMFCore.PortalContent (the default) and therefore doesn't behave like a dataskin ..
any ideas ?
is the order in wich the modules are loaded known or changeable ??
if this doesn't work .. I need to release the patches as diffs or tarballs replacing CMFDefault and Core .. not as nice as just patching them ..
thanks
Ulrich Eck
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )