This would be a nice recipe to share with others when you have it all worked out...
On Wednesday, November 21, 2012 7:57:30 PM UTC-5, kevinpfromnm wrote: > > +1 on lifecycle to encapsulate the parse and expose action on > controller/view. > > 1 downside of the link is unless you know your routes well, you'll > probably make it respond to GET request. My general rule with HTML is a > link should never trigger a (significant?) change because robots will > follow them. > > On Wednesday, November 21, 2012 9:51:32 AM UTC-7, Bryan Larsen wrote: >> >> > Talking about coding style, do you have any "rule" when using multiple >> > show&index actions? >> >> Maybe I should, but I don't. :) >> >> cheers, >> Bryan >> > -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/hobousers/-/Gu1Fox_cPjgJ. 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.
