THis would be nice as a recipe with all of the code provided. : -) On Tue, Jul 27, 2010 at 7:32 PM, Matt Jones <[email protected]> wrote:
> > On Jul 27, 2010, at 4:41 PM, kevinpfromnm wrote: > > It's not that simple I'm afraid though perhaps there should be since >> this is a semi common occurrence. >> >> Anyway, you need to setup the paginated child collection in the >> controller and pass it to the view. then change the child collection >> call to use the paginated collection and add the pagination navigation >> links/buttons. >> >> Alternatively, you can create an owned index action where you'd get a >> url like /parents/parent-id/childrenname that would show child >> elements paginated. >> > > +1 for this method - it's probably the most straightforward, and I've ended > up using it in several cases. > > In one situation, the "parent" model was basically almost a placeholder > (just a 'name' field and a shedload of has_manys) so what users think of as > "The Foo page" is really /parents/foo/child_models. It also conveniently > keeps the REST police away from my door. :) > > --Matt Jones > > > -- > 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]<hobousers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/hobousers?hl=en. > > -- - Owen Owen Dall, Chief Systems Architect Barquin International Cell: 410-991-0811 -- 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.
