This is an issue with how ActionView handles delegate template handlers (e.g. Haml). Theoretically, though, it should be possible to modify ActionView to deal with Haml in an overridable way. Such modifications probably won't make it into Haml proper, because they'd be very rarely useful, but they wouldn't be hard to do (gotta love Ruby's modify-any-class-anywhere functionality), so I suggest you do it for Typo. ActionView isn't terribly confusing... I've made a few mods for Haml, and the template-rendering pipeline (is pretty straightforward.
- Nathan On 2/8/07, Kevin Ballard <[EMAIL PROTECTED]> wrote: > > > I'm sorry if this has been discussed before, but if so I can't find > it. > > A problem I noticed with Haml was that it seems to prevent overriding > any views with rhtml. In Typo we have a themeing system that works by > adding more view paths to search such that the active theme can > override built-in views. However, using Haml 1.0 it seems that any > Haml views are searched for before rhtml, rather than at the same > time. This means that a theme using rhtml cannot override any Haml > views. > > Is this still true in the current development version of Haml? And if > so, is there any way to fix this? I really want Typo to use Haml for > all of the built-in views, but making this conversion now will break > all third-party themes. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" 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/haml?hl=en -~----------~----~----~----~------~----~------~--~---
