Yes, that should go in the application.dryml As to jquery, I haven't tried it myself.
On Jun 29, 1:18 pm, oldlibmike <[email protected]> wrote: > Thanks Bryan, > I think that will put me on the right track. I assume this should also > be defined in the application.dryml? > I have the hobo-jquery and am currently using its date-picker in the > app but I haven't experimented with formlets or its other features. > They seem even less documented than hobo! > > I think the new tag definition you propose for the "guts" of the form > is a decent workaround though. > Do you know if there are any good jquery-hobo examples available? > > I've also seem some very impressive jquery sortable/editable tables > but I don't think they would be that easy to integrate into a hobo > app. > > - Mike > > On Jun 29, 2:43 pm, Bryan Larsen <[email protected]> wrote: > > > Sorry, I understand the question now. > > > input-many uses a field-list rather than a form, and field-list is not a > > polymorphic tag. So in Hobo 1.0, there's no easy way around your > > problem. hobo-jquery partially fixes this problem, and Tom has some > > plans for Hobo >1.0. > > > But in the meantime, here's what I'd do, to keep everything as DRY as > > possible. > > > <def tag="item-fieldlist"> > > define guts of form here... > > </def> > > > <def tag="form" for="Item"> > > <item-fieldlist/> > > </def> > > > <def tag="form" for="Sale"> > > <field-list:> > > <items-view:> > > <input-many> > > <item-fieldlist/> > > </input-many> > > </items-view:> > > </field-list:> > > </def> > > > kevinpfromnm wrote: > > > Yeah, I was wondering this too. It doesn't seem to use the same form > > > code for the guts of the input-many... which makes sense since it's > > > inside a form already but is annoying as it means possibly needing to > > > code the form twice or once and include in the normal form. > > > > On Jun 29, 9:54 am, Bryan Larsen <[email protected]> wrote: > > >> You seem to be on the right track. Can you post your code? Are you > > >> putting your override in application.dryml? > > > >> oldlibmike wrote: > > >>> I have a master detail relationship with Sales and Items. > > >>> Sales has_many :items, :accessible => true, :dependent => :destroy > > >>> Items belongs_to :sale > > >>> When I display the sales edit form, there is a repeating group > > >>> of :items that I can presumably edit, add or delete. > > >>> I have tried to override the form for item and when editing an item > > >>> all by itself, my overrides work. > > >>> When the item appears on the sales edit form however, none of my > > >>> overrides are there. The default edit form for item is displayed. > > >>> How would I overrided the item form in the context of its parent Sale? > > >>> Thanks in advance, > > >>> Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
