You might want to look at the part/update pattern hobo provides though I'm not sure if it will meet what you're needing. You can always fall back to a rails-esque approach while keeping hobo syntax by rendering dryml.
On Wednesday, August 21, 2013 2:37:25 PM UTC-6, Parker Morse wrote: > > I have a model (AnimationPane) with a belongs_to on another model > (Animation). > > There are a few attributes the AnimationPane should try to calculate from > the Animation, but it *may* not be able to. If it can't, the user creating > or editing the AnimationPane should supply those attributes. However, it's > not really transparent to the user when they need to supply the values and > when they can be calculated. It's much easier for the application to check > itself. > > So I'd like to set up the form for the AnimationPane to select the > Animation from a menu (easy) and then show or not show the fields for these > calculated attributes depending on the Animation selected. From the user's > point of view it's pretty simple. From my point of view... ouch, my head > hurts. I know how I would do this with a Rails app (XHR back to the server > for an updated form when the Animation is selected) but I'm not really sure > where to start with Hobo. > > Can anyone give me a toe-hold? Thanks. > > pjm > -- 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.
