Agree. I've been in production with ruote + ruote-kit for a year and a half now.
We use ruote-kit for admin purposes, to look at the internals when needed. Why build our own controller+views for this when there is ruote-kit? It is at the wrong level of detail for our users though. For regular users, we use ruote to launch the workflows in response to certain user actions (e.g. a registration/review process that requires multiple sign-offs), and we have a controller that provides a user-facing dashboard (index method on the controller) for the work. The dashboard links to workitem-specific pages (edit method on the controller) using partials with filenames that are constructed from the process name, the participant and the a "task" attribute. HTH, Steve On Friday, November 15, 2013 3:10:06 AM UTC-5, Torsten Schoenebaum wrote: > > Kiran wrote: > > To use ruote in rails project which is the best option ruote or > ruote-kit ? > > That depends on your requirements. Route-kit is fine for exploring running > workflows, see it as kind of admin frontend for ruote. > > So, there's no need to use it, but it may be helpful, at least during > development. > > Cheers, > Torsten > -- -- 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 --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
