[Zope-CMF] CMF Collector: Open Issues
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/CMF). Assigned and Open mhammond - Windows DevelopmentMode penalty in CMFCore.DirectoryView, [Accepted] http://www.zope.org/Collectors/CMF/366 Pending / Deferred Issues - FSPropertiesObject.py cannot handle multiline input for lines, text attributes, [Deferred] http://www.zope.org/Collectors/CMF/271 - Can't invalidate skin items in a RAMCacheManager, [Pending] http://www.zope.org/Collectors/CMF/343 - workflow notify success should be after reindex, [Deferred] http://www.zope.org/Collectors/CMF/389 - Possible bug when using a BTreeFolder Member folder, [Pending] http://www.zope.org/Collectors/CMF/441 - Proxy Roles not Working/Applied to Worflow Transition Scripts, [Pending] http://www.zope.org/Collectors/CMF/449 - safe_html filters some tags which should probably not be filtered, [Pending] http://www.zope.org/Collectors/CMF/452 - purge_old in runAllImportSteps not working, [Pending] http://www.zope.org/Collectors/CMF/455 - PUT handling for Events is broken, [Pending] http://www.zope.org/Collectors/CMF/458 - Danger from Caching Policy Manager, [Pending] http://www.zope.org/Collectors/CMF/460 Pending / Deferred Features - Favorite.py: queries and anchors in remote_url, [Pending] http://www.zope.org/Collectors/CMF/26 - DefaultDublinCore should have Creator property, [Pending] http://www.zope.org/Collectors/CMF/61 - Document.py: universal newlines, [Pending] http://www.zope.org/Collectors/CMF/174 - portal_type is undefined in initialization code, [Pending] http://www.zope.org/Collectors/CMF/248 - CMFTopic Does Not Cache, [Deferred] http://www.zope.org/Collectors/CMF/295 - Wishlist: a flag that tags the selected action., [Pending] http://www.zope.org/Collectors/CMF/301 - CMFDefault should make use of allowCreate(), [Pending] http://www.zope.org/Collectors/CMF/340 - Nested Skins, [Deferred] http://www.zope.org/Collectors/CMF/377 - CatalogVariableProvider code + tests, [Pending] http://www.zope.org/Collectors/CMF/378 - manage_doCustomize() : minor additions, [Pending] http://www.zope.org/Collectors/CMF/382 - CMF needs View-based TypeInformation, [Pending] http://www.zope.org/Collectors/CMF/437 - Marker attributes should be deprecated, [Pending] http://www.zope.org/Collectors/CMF/440 - Patch to let DCWorkflow emit events on transitions, [Pending] http://www.zope.org/Collectors/CMF/461 ___ 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
Re: [Zope-CMF] Zope 3 events from workflow
Hi All, Martin Aspeli wrote: class IWorkflowEvent(IObjectEvent): A workflow related event wf_name = TextLine(title=uThe name of the workflow this event is part of) transition = TextLine(title=uThe name of the transition taking place) state_before = TextLine(title=uThe object's state before the transition) state_after = TextLine(title=uThe object's state after the transition) I know I'm very late on this (sorry for taking a christmas vacation ;-) but how would I go about subcribing to a particular transition of a particular workflow? This feels like the most common case for me, but it would seem that if you want to do that with the current patch, you'd have to have a generic subscriber that then if/then/else'd its way to only doing the right thing for the right workflow and the right transition. I thought avoiding that kind of if/then/else'ing was what event subscribers were all about. Hopefully I'm just missing something, could someone enlighten me? (and by enlighten, I don't mean anything involving automotive fuel and matches :-P) cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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
[Zope-CMF] Re: Zope 3 events from workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: Hi All, Martin Aspeli wrote: class IWorkflowEvent(IObjectEvent): A workflow related event wf_name = TextLine(title=uThe name of the workflow this event is part of) transition = TextLine(title=uThe name of the transition taking place) state_before = TextLine(title=uThe object's state before the transition) state_after = TextLine(title=uThe object's state after the transition) I know I'm very late on this (sorry for taking a christmas vacation ;-) but how would I go about subcribing to a particular transition of a particular workflow? This feels like the most common case for me, but it would seem that if you want to do that with the current patch, you'd have to have a generic subscriber that then if/then/else'd its way to only doing the right thing for the right workflow and the right transition. I thought avoiding that kind of if/then/else'ing was what event subscribers were all about. Not necessarily. You could always register a generic subscriber which then republished the more discrete events to those subscribers interested. Type-based dispatch is not an *end*, its a means, and sometimes the burden needs to be distributed. Hopefully I'm just missing something, could someone enlighten me? (and by enlighten, I don't mean anything involving automotive fuel and matches :-P) No Yuletide bonfires here. ;) Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFmoM5+gerLs4ltQ4RAu0PAJ9+VFrIxT5xhIMesaKAx3GXoFIveQCfVr8d V19ywCpKDkBjCy9GEpomuZc= =hP7n -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
