> Steve, is it possible to see an implementation? If it's not open-source, could you provide snippets?
I wish! I'd have to get permission from management folks who would need a lot of convincing. It's not a battle I want to fight, which is why I had to describe it only at a high-level. I don't think I'm doing anything especially clever that would make a code snippet useful. At least, I don't think so. My goal was to give an example, "here's one way to decide about ruote/ruote-kit in a rails app". Your point about the REST interface is another way to decide, although I'm not convinced. What does decoupling rails from ruote buy you, other than less gem dependencies? Doesn't your client code just end up duplicating the gem functionality with REST calls? On Friday, November 15, 2013 11:12:04 AM UTC-5, Danny Fullerton wrote: > > Also, keep in mind that ruote-kit main objective is to provide a RESTful > interface to ruote. If you wish to decouple rails from ruote, this is very > useful. > > Steve, is it possible to see an implementation? If it's not open-source, > could you provide snippets? > > Regards, > > -- > Sent from smartphone. Sorry for any typos. > > Steve Sexton <[email protected] <javascript:>> wrote: > > > 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] <javascript:> > to unsubscribe : send email to [email protected]<javascript:> > 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] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- 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.
