wouldn't view partials still require the view script to exist? I was trying to avoid having the actual files there too. Infact, the perfect solution would be to override if the file does exist.
On Mon, Jan 19, 2009 at 3:32 PM, Chris Weldon <ch...@chrisweldon.net> wrote: > Action Helpers are really dependent upon what you are trying to do. > Something that's static I would render out using partials. However, if > you're doing a bit of output processing (nothing static), I would > recommend using an Action Helper. :-) > -- > Chris Weldon > > On Sun, Jan 18, 2009 at 11:17 PM, Cameron <themsel...@gmail.com> wrote: > > Hi guys, > > > > I have an application that is growing piece by piece, table by table, and > as > > it grows, as do the number of view scripts the application needs. In > order > > to ease maintenance on these, I've managed to make the vast majority of > the > > views indentical across controllers, by just passing the relevant > variables > > in to the view. Of course, this means I still have to cut and paste the > > views each time I make a change to one of them, which is clearly > > inefficient. So, what's the standard way around this? I saw Action > Helpers, > > and they seem like they would do the trick, but I'm not sure if that's > > considered "best practice". Any ideas? > > > > > > -- > Christopher Weldon > http://chrisweldon.net > ch...@chrisweldon.net >
