Sass functions are always global as they are defined in Ruby code, not in other sass files. Sass saves you so much time... don't try to over optimize things by eliminating one line of code that tells you where stuff is coming from in "this" sass file.
chris On Thu, Jul 16, 2009 at 2:16 AM, José Mota <[email protected]> wrote: > > I want to use something like that. there are some css rules i'd just > rather not have because they're so big... i'm having a general one > called layout.sass and a common.sass with other more common.sass with > non-layout rules. and then i want to have one or other very particular > rules, not to be used that often. > That's why the import is such a great idea. What would be even better > is have the definitions i want initiated on boot, for instance. That > way I wouldn't have to care about adding the import directive into > every single sass file. BTW, is there such a procedure? For instance, > the hsl() function is there and we don't need to import it, get the > idea? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
