I have implemented this sort of use case on a different stack with jQuery ajax calls to a controller returning different snippet based views and will be doing similar things on a hobo based stack which screams for a lifecycle approach but am not sure this would prove to be any easier on a less elegant stack.
Lets say you have a like this and you like this states based toggle which would then be removed by a secondary toggle for 2 rsvp and attending states and then coming back with a not attending action which restores both back to to both an rsvp and like it. What I am failing to see is the advantage using a using a Hobo life cycle even though it is a generic life cycle regardless what is used. Yes the code would be a bit more elegant but would there be a rapid advantage? -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
