I was imagining that the plugin would be a normal Rails plugin which would assume Haml is installed and use monkeypatches to modify its behavior.
Adam Hooper wrote: > On Sun, Sep 28, 2008 at 9:08 PM, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote: > >> This seems like a good candidate for a separate plugin. I don't like >> tying Haml and Sass too closely to Rails or to each other, and the idea >> of adding behavior for a certain workflow seems to map well to the idea >> of an individual plugin. >> > > I agree fully. > > I am at a loss as I do not know how to go about plugin-izing this > functionality. Does Haml support plugins, either implicitly or through > Rails? Really, I'm looking for the "step 1": as in, what will the > end-user do to install my separate functionality into his/her Rails > application? > > And if you have any intention of *changing* Haml in the future to make > it support plugins, do you have any design preferences for a plugin > system, placement of hooks for plugins, etc? If I do patch Haml for > plugin purposes, it would be nice for me to steer it in the direction > you foresee, if any. > > Adam > > -- > My Website: http://adamhooper.com > My Blog: http://adamhooper.com/blog > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
