According to ruby documentation using render_component, is generally a bad idea. Specifically it sais to "reserve components to those rare cases where you truly have reusable view and controller elements that can be employed across many applications at once." What if I''m not interested in creating "reusable view and controller elements that can be employed across many applications at once", but am interested in cleanly separating logically different widgets? If I want to have a stock ticker, the weather information, and a forum on a single page, I shouldn''t have to stick all of these things into a single controller class. --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---