This isn't really feasible. Not only do I not want to complicate the Haml installation process, but that would break all previous Haml installations. I don't like breaking changes, especially of this magnitude.
railsjedi wrote: > Hi. I'd really like to propose extracting all the Rails hacks out of > the next point release of Haml (2.1?). After doing some hacking on the > source, it really seems to me that a huge portion of the haml code is > dedicated to hooking Haml into Ruby on Rails, with some spaghetti > logic required to support for all subsequent versions (1.2, 2.0, 2.1, > etc) > > I think merb-haml plugin does it perfectly. Leaves Haml on its own to > work independently of the web framework. We should extract that idea > for the Rails version. > > Since we have the ability to use config.gem since Rails 2., all you > need to do is create a haml_rails gem that people can use to add haml > support to their rails projects. I'd even take out all the junk for > Rails 1.2.3 (patches.rb) to simplify things even more. Anyone who > requires an older version of Rails can just as easily grab a copy of > the 2.0.x release of Haml. > > Any thoughts on turning Haml lean and mean for a 2.1 without the Rails > hacks? The haml_rails gem/plugin would be dead simple to build and > easier to upgrade when each subsequent release of Rails breaks the > wonderful alias method chaining in action_view_mods. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
