On Fri, Feb 03, 2012 at 12:31:23PM -0800, kedar mhaswade wrote: > > I see. Does it mean I can plug in the admin interface provided by ruote-kit > in my web application?
Yes. You can, for example, add this to your config/routes.rb: ---8<--- # routes to RuoteKit match '/_ruote' => RuoteKit::Application match '/_ruote/*path' => RuoteKit::Application --->8-- > Can I configure views so that there is a consistency > across the app? Yes, it's doable, it's Haml + CSS (and Ruby). Generally people use ruote-kit's interface as a special admin only zone. When they want to integrate in their core webapp, they look at ruote-kit for inspiration and build their own views and controllers. > 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. Do you mean "modify process instances"? If you need to modify process definitions, only a text editor is required. The admin interface is handy for administering the system, not really to design process definitions. Maybe you meant modifying process instances and in that case, yes, the admin interface offered by ruote-kit is handy (for process administrators). > 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. It's still OK for you to go with simpler abstractions, business objects and plain controllers that modify their states, simple business rules and no workflow engine problems. It's true that ruote is heavy-weight. You shouldn't dive directly into building something with it. Take the time to do a prototype, then you can make the right decision. I'm not selling anything to you. As a fellow developer, it's my duty to tell you not to use ruote if it leads to too convoluted a sytem. Best regards, -- John Mettraux - http://lambda.io/processi -- 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
