No, there are no such plans. We've talked about it extensively, and decided not to allow that, for several reasons:
1. It's really not as useful as you'd think. Unlike normal HTML pages, styles don't really need to change dynamically. 2. It would dramatically decrease Sass' speed, and thus our freedom to do cool stuff. Right now, Sass runs in O(1) time with respect to the number of times it's accessed, so we can make each time it parses the template much slower than it would otherwise be. 3. User agents typically cache CSS pages, so making them dynamically changeable would mean that users would have to refresh their cache every time they change, so it's not really workable. - Nathan On 2/1/07, Chris Abad <[EMAIL PROTECTED]> wrote: > > If you're looking to parse the sass templates directly, does that mean > there are to plans of being able to pass instance variables to sass > templates? Seems it'd be a very handy thing to have. > > On Feb 1, 2007, at 3:44 PM, Nathan Weizenbaum wrote: > > Not to shift the blame, but it was Hampton's decision. There is a good > reason for it, though: eventually, we hope to have a Firefox extension that > parses Sass as well. Then having them publicly available is a benefit, as FF > can parse them directly. However, there is an option you can set to change > the Sass template location. I believe that if you put > > Haml::Sass::Plugin.options[:template_location] = RAILS_ROOT + > '/stylesheets' > > in environment.rb, then Sass will load the templates from there. > > - Nathan > > On 2/1/07, Vladimir Bobes Tuzinsky <[EMAIL PROTECTED]> wrote: > > > > > > One vote for sass files in a non-public directory and an optional > > human-readable CSS output formatting here :) > > > > bobes > > > > On 01/02/07, svenax <[EMAIL PROTECTED] > wrote: > > > > > > Hey, that's a good point! app/stylesheets seems like the logical place > > > to me. > > > > > > /sven axelsson > > > sånt > > > On Feb 1, 8:56 pm, Chris Abad < [EMAIL PROTECTED]> wrote: > > > > Nice. Curious why you didn't put them in a non-public directory like > > / > > > > app/views/stylesheets or even app/stylesheets. Can't the sass files > > > > be accessed directly with them being in the public folder? > > > > > > > > On Feb 1, 2007, at 11:49 AM, Nathan Weizenbaum wrote: > > > > > > > > > Sass files should be put in public/stylesheets/sass, with a .sass > > > > > extensions. They'll automatically be compiled if they need to be > > > > > whenever a controller is accessed, and corresponding stylesheets > > will > > > > > be put in public/stylesheets. For example, if you have > > > > > public/stylesheets/sass/main.sass, it will cause > > > > > public/stylesheets/main.css to be created. > > > > > > > > > - Nathan > > > > > > > > > > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
