On Mon, May 17, 2010 at 10:28:31PM -0400, Cappelaere Patrice wrote: > John, > > Well... parser.rb takes a definition (from a file, string...) creates a new > instance of a Ruote::Parser, calls parse... > calls ruby_eval... which eventually calls the ruby_dsl. > Coming from ruote_fluo, it is a JSON string parsed to a tree back to ruby... > > So there is quite a bit of transformation involving strings here....
Please re-read the example I passed in http://groups.google.com/group/openwferu-users/msg/c4befb96480e71bb And tell me when parse is called. > I would love to be able to use more ruby code within a pdef like... > and pass it to ruote_fluo to display as a workflow > > pdef = Ruote.process_definition do > sequence do > x = some_function(3 + ${f:v}) > y = 1 + 5 / 6 > alpha x, y > bravo > end > end > > actually in my case it would be more like: > pdef = Ruote.algorithm_definition do > sequence do > x = some_function(3 + ${f:v}) > y = 1 + 5 / 6 > alpha x, y > end > end > > and then use those algos as subprocess.... > > Does this make sense? It makes sense for you, in your project. For me, it makes for crowded process definitions. Such calculations are better when placed in a participant that may be re-used by multiple process definitions. Best regards, -- 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
