Yep, it also is being used as a live representation of the process state much in the same way ruote-fluo does with canvas in RuoteKit.
Of course html elements are less versatile than drawing direct to canvas but with a bit of css I can get it looking quite nice and understandable. Initially I started writing a human readable description of the process separately from the process definition, however I quickly found this took a while and really was a duplication of the information held within the pdef, any pdef changes meant re-writing the human readable text. By attaching a :description attribute to each command in the pdef I can quickly annotate each step. These nicely survive any logic or order changes within the pdef. On Feb 3, 2:40 am, John Mettraux <[email protected]> wrote: > On Wed, Feb 02, 2011 at 07:40:00AM -0800, rebo wrote: > > > Had to do quite a bit of rendering to html of process definitions > > lately, so extracted out the formatter i've been using. > > >https://github.com/rebo/Simple-Ruote-Formatter > > > Its missing loads of ruote commands and the hamlFormatter example is > > largely dependant upon my processs definition style but hopefully can > > help someone. > > Hello Rebo, > > nice idea ! > > Are you using it to document your process definitions ? When people are > browsing your definition portfolio ? > > I will link to it from the website. > > Many thanks, > > -- > John Mettraux -http://jmettraux.wordpress.com -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
