On Fri, Feb 3, 2012 at 11:12 AM, John Mettraux <[email protected]> wrote:
> > Hello Kedar, > > welcome to the ruote mailing list. > Thanks, John. > > On Fri, Feb 03, 2012 at 10:53:41AM -0800, kedar mhaswade wrote: > > > > 0- For my Rails app, what should I be using -- ruote-kit+quaderno or > ruote > > is to be used directly along side my application models/resources? > > It depends on your needs. > > Ruote-kit brings you a free admin interface. > > I see. Does it mean I can plug in the admin interface provided by ruote-kit in my web application? Can I configure views so that there is a consistency across the app? > Some people go directly for ruote. > > Quaderno is nice but it perhaps doesn't fit your requirements or the tastes > of your designer. > > Use what you understand (and understand you need). > > Yeah, trying to understand the choices that I should make. I do need to give (some of) my users an ability to modify process definitions, so an admin interface is required, I believe. But then, I am assuming that I will do that using ruote abstractions. Additionally, Kenneth's blogpost gave me an impression that making a commitment to implementing workflows in your application is a fairly heavy-weight decision and I was not sure if I should do that, given that at least initially, most of the decisions are going to be made by other users logging in to my application (there are no multiple applications/services involved). Looks like I have deliberated enough and am leaning toward using ruote. > > 1- Is it possible that a particular process is modified after a few > > instances of it are created? In other words, let's say a process > > administrator who is a user of my application wants to change the course > of > > a process after a particular state has been achieved, will that be > possible > > for me to provide using ruote? > > Yes. > > You should look at > > http://ruote.rubyforge.org/process_administration.html#re_applying > > it explains how to re_apply an expression. That technique is useful for > modifying process instance "in-flight". > > OK! Thanks. I will check that out. > > > 2- How do we import/export a particular workflow/process definition? > > Internally ruote stores them as JSON strings. When passing them around, any > format understood by ruote is OK. > > * Ruby: > https://github.com/jmettraux/ruote/blob/14bbe62447585164ea8b016185999c5804285703/test/unit/ut_0_ruby_reader.rb#L22-36 > * XML: > https://github.com/jmettraux/ruote/blob/14bbe62447585164ea8b016185999c5804285703/test/unit/ut_9_xml_reader.rb#L17-31 > * radial: > https://github.com/jmettraux/ruote/blob/14bbe62447585164ea8b016185999c5804285703/test/unit/ut_24_radial_reader.rb#L177-193 > > * JSON: > https://github.com/jmettraux/ruote/blob/14bbe62447585164ea8b016185999c5804285703/test/unit/ut_24_radial_reader.rb#L187-189 > > > > Is there a repository where people share such definitions? > > I suppose these > > can't be standard, but since several processes are "typical", there > should > > be a way of consuming them in an open manner and formats (XML, JSON)? > > Sorry, there is no such repository, it would indeed be very easy to do. We > could start a git repository for that. > > Anyone here could mail me interesting processes, and I'll start a github > repository for it. > > IIRC, XML isn't used by anyone. Processes in their Ruby or radial > representations are much easier to read than XML or JSON. Ruote just > adapts. > > I see. That helps. Once I am more familiar with this and would have used ruote considerably, I can contribute. Now, I need to get into the code and figure out how to properly use ruote. Regards, Kedar -- 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
