On 5-okt-2007, at 23:01, Michael Koziarski wrote:
> We can push something like that into ActionView once we've branched > for 2.0, along the lines of charlie's suggestions: > > http://cfis.savagexi.com/articles/2007/09/16/making-rails-better- > actionview-needs-a-makeover > > There's a *lot* of room to improve actionview, but it can wait for > 2.1 when we can do it properly. Well, I've got a radical proposal then. Why don't we _abolish_ the multiple view paths until 2.1 hits the streets? I mean, it's edge functionality, people using it must have known what they are doing. John Long doesn't seem to be providing any feedback. And it's misimplemented AFAIK. If you ask me I consider these multiple view paths more breakage than an medicine, it's an underpowered, crippled solution which, thus far, has broken all of my apps and has complicated the situation instead of giving a cure. So let's put it so: I'm all for a refactoring run (and I will have some time to put into that shortly), but this abomination has to go for 2.0. Implementing a custom theming strategy is also much simpler with a single template_root. -- Julian 'Julik' Tarkhanov please send all personal mail to me at julik.nl --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
