the simplest way given the amount of customization it'd take to use update-button or lifecycles, would be to make a form with hidden user and recipe inputs with your button. then a controller action that handles creating/destroying the join.
the only reason this is easier than lifecycles is with lifecycle you have to make the form(s) yourself anyway along with the transitions. although, this is not an uncommon design pattern if you think of it more like a 'watch this item' type flag and maybe we should make an easier way to handle with transitions? -- 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.
