-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 yuppie wrote: > Hi! > > > What's the current status of the events support? > > 1.) AFAICS the efge-1.5-five-compatible branch is only merged into the > 1.6 branch. IIRC there were no plans to merge this into the 1.5 branch > because these changes are not 100% backwards compatible. That means that > CMF 1.5 should not be used with Five 1.2/1.3 events. Right? Why are > those changes not merged into the trunk? > > 2.) The CMF 1.6 tests suppress the subscribers deprecation warnings. > Wouldn't it be better to use five:deprecatedManageAddDelete? > > 3.) Is there anything else on the CMF 1.6 / 2.0 todo list that's related > to events? Are there any plans to use events in CMF 2.0?
Good questions. I am about to post a "release status" document, for which those issues are germane. I don't know the answers, BTW, beyond the fact that we *do* plan to publish container and object modification events in 2.0; we won't get around to changing the infrastructure pieces to be based on those events before a 2.0 release. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDxVF5+gerLs4ltQ4RAv/1AKC1+rK7155rL2/WEZmQ1MMmYa/PJwCePkq5 eUIF5fhtfYGoNPAg6zUkZ8Y= =6Mvq -----END PGP SIGNATURE----- _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests