Hello Florent, The changes in the two files are only to be able to more easily subclass the TransitionDefinition and ProcessDefinition which aren't yet persistent. I changed only the hardcoded references to class properties. No API changes, every test passes unchanged of course.
The goal is (was) to be able to keep the workflow definition persistent in a local utility. The persistent WFMC support is going to be implemented in a completely _different_ package, it might _not_ be even part of the release. In fact it is working for me, I just have to make a package or something publishable out of it. Saturday, April 29, 2006, 5:52:39 PM, you wrote: > Adam Groszer wrote: >> Log message for revision 67734: >> Preparations for persistent WFMC, >> as discussed at the SwissSprint >> >> Changed: >> U Zope3/trunk/src/zope/wfmc/process.py >> U Zope3/trunk/src/zope/wfmc/xpdl.py >> > Hi Adam, > Please keep in mind that discussion at a sprint does not replace > discussion in the list, and that changes to Zope need to follow a > proposal-based model. Could you detail what your plan is? > Florent -- Best regards, Adam mailto:[EMAIL PROTECTED] -- Quote of the day: As far as we know, our computer has never had an undetected error. _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
