I was also thinking. Both "actions" should still call artists#index. In artist#index, I'll have an if condition that checks which template/ view to render.
Is this a sensible approach? On Oct 11, 11:29 pm, Christian Fazzini <[email protected]> wrote: > Need some advice. I've got two modules: artists and paintings. > > In my home page, I've got a 2nd page that says "Browse paintings", > which displays ALL paintings of ALL artists. This is being rendered by > paintings#index. > > In another page, I should show all paintings of a specific artist > ONLY. Meaning, paintings from ONE artist. I cant use paintings#index > for this anymore since it is already being used by the homepage. Also > take note, both pages are rendered differently (meaning, data and > display are not the same). They don't look alike. So I can't use index > for both pages. > > What approach would you take? > > I am thinking of creating a method in the artists module called: > list_paintings. And then in /app/views/list_paintings.html.erb > > What are your thoughts? -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
