Hi, I have sometimes used AASM (https://github.com/aasm/aasm). It's not as nice as Hobo, because you have to define all actions in the controllers, but the model syntax is similar.
I would go that way because I don't have experience integrating pieces of Hobo :P. Regards, Ignacio El 29/01/14 13:40, Stefan Haslinger escribió: > Hi folks, > > I'm thinking about getting lifecycles in a legacy rails app, that is using > > * cancan for authorizations > * devise for authentication > * simple form in views > > Getting lifecycles would mean, I need to use hobo_model. Easy. > But that needs a hobo user model > > 1. ... so I had to throw out devise. > 2. To get authentication consistant, I had to throw out cancan. > 3. Do get authentication view integration I had to switch to dryml. > > Well I think that's almost a rewrite ... > Maybe it's better to throw in statemachine there or workflow gem... > > Are my assumptions right here? Has anybody been in a similar situation? > Please share your thoughts on this! > > Cheers, > Stefan > > -- > You received this message because you are subscribed to the Google > Groups "Hobo Users" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/hobousers. > For more options, visit https://groups.google.com/groups/opt_out. -- Ignacio Huerta Arteche http://www.ihuerta.net Teléfono: 0034 645 70 77 35 Email realizado con software libre -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/groups/opt_out.
