On Tue, 10 Mar 2009 04:46:22 -0700 (PDT)
Lasertoast <jar...@gmail.com> wrote:

> 
> I'm a relatively new Rails developer, but I think I have a good grasp
> on the paradigm and I'm trying my best to adhere to RESTful standards.
> 
> First, let me describe the basic structure of my Rails app (only the
> pieces relevant to my problem of course):
> 
> I have a User_Layouts controller.  Each User contains multiple
> User_Layouts.  Each User_Layout entry describes a Module that the user
> is subscribing to (and thus will be displayed on his dashboard -
> essentially a collection of User_Layouts).  Thus, the
> User_Layouts#index should display a dashboard containing all Modules
> the User is subscribed to (very similar to iGoogle). I want to be able
> to create these Modules easily (perhaps using a tailored generate
> script) - each module having its own model, view, and controller.
> 
> My question is, what is the proper way to structure this?  When
> User_Layouts#index is invoked, how to I tell Rails to render each
> Module's view and place it in the proper div on the User_Layouts#index
> view?  I've toyed with rendering partials, and render :update to
> replace the innerHTML, but none of these seem elegant enough to be
> standard practice.

I would probably just create partials for each type of module. Then you can use 
render :partial => @module, which will render the correct partial for the 
object type.

SH
-- 
Starr Horne
My blog: http://starrhorne.com
Check out my Helpdesk RailsKit: http://railskits.com/helpdesk/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to