From: Martin@Cleaver.org <mrj...@gm...> - 2006-02-07 21:51:51
|
On 07/02/06, Meredith <ms...@sp...> wrote: > > On Feb 7, 2006, at 4:06 PM, Martin@Cleaver.org wrote: > > > Hi Meredith, > > > > Are you familiar with Chris Winter's workflow CPAN module? I note you > don't say you are using it. > > > > http://www.google.ca/search?q=3Dcpan > > +workflow&start=3D0&ie=3Dutf-8&oe=3Dutf-8&client=3Dfirefox- > > a&rls=3Dorg.mozilla:en-US:official > > Just wondered if hooking into that would afford us whatever > > capabilities Chris adds to his module in the future. > > > > Cheers, and good work, > > Martin. > > > > -- > > Martin@Cleaver.org > > > > > > I'm not using it. I took a very brief glance at it, but the workflow > is defined using XML, which probably isn't what we want? The state > table and transition table are defined using the familiar | state | > permissions | message | syntax, which seems to be more TWiki than the > module. > Hi Meredith, Its true that we'd want to define it using a TWiki table, but I suspect tha= t the way to go would be to transform back and forth to XML from TWiki table. > At second glance, I see that one can create one's own > parser, which means, I suppose, that it's possible it could > be used. When I have a bit more energy, I'll give it another > look and see how hard it would be to hook it in. http://www.cwinters.com/pdf/workflow_pgh_pm.pdf (linked to from Codev.WorkFlow) makes me think that Chris must have spent months building out this capability. It would be great to leverage both the existing code and that which he builds in the future. Using more standard stuff is good for Perl - and, assuming its performant - good for TWiki. Writing a CPAN WorkFlow parser is probably easiest but actually a transformation from TML <-> XML should be an TWiki-infrastructure provided component, so if we were to write this it would be universally useful and a likely library component for the core. Regards, M. -- Martin@Cleaver.org MSc MBA |