Hey Seb, too much decider code in partials? Use Cells [1], that's view components for Rails and designed to solve problems like yours. Check out some examples at github [2] and be sure to use view inheritance [3], which could be very handy to map all your different user roles in your views.
If you get stuck, feel free to ask us on irc.freenode.org in the #cells channel or mail me directly. Cheers, Nick [1] http://cells.rubyforge.org/ [2] http://github.com/apotonick/cells [3] http://apotomo.de/2010/04/using-cells-view-inheritance-to-clean-up-your-views/ On 7 Sep., 21:09, Sebastião Giacheto F. Júnior <[email protected]> wrote: > Hi, > I have a simple partial, just a file list. > > The list is exactly the same for those who have permission to change > it, and those who just can see it. > > The best way to keep things DRY, I think, is doing some kind of shared > partial. No problem so far. > > But what about the specific actions (new/edit/delete)? Scattering some > conditional statements seems very very uglier, and even more difficult > to maintain, than separate views. So I came up with another solution: > putting some yield statements on the code. Something like, "yield > :delete" for example. Than I render a partial that contains only the > user specific things, and put the content_for's that are appropriated. > > But I think that can be even a prettier solution. So I'm asking you guys :D > Sorry, if this is a newbie question, I'm new to rails, and concerned > about doing things the best way possible. > > Thanks in advance > -- > Sebastião G. Ferreira Júnior > "How much trust is too much trust? Should you even trust?" -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en.
