--
You received this message because you are subscribed to the Google Groups "Compass" group.
To post to this group, send email to compas...@googlegroups.com.
To unsubscribe from this group, send email to compass-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/compass-users?hl=en.
sass 3.1 is out! did feature make it?
--
--
Hunt & pecked on my iPhone... Sorry if it's brief!
On Apr 28, 2011, at 4:23 PM, Mathias Schopmans <mat...@schopmans.me> wrote:
> Output will be printed, where I place the @silent classes, right?
>
On Thursday, April 28, 2011 at 7:24 PM, Eric Meyer wrote:
I see. The strange thing about the proposed syntax is that I don't want all that code to be "silent". I only want the *selector* to be silent. So I don't see it as comparable to media queries. I see it more like mixins, and so a more mixin-like syntax. Hmmm.
--
Also why don't mixins use the same behavior as @extend? For example it
could store the first selector which includes any mixin, and treat any
other selectors including the same mixin as@extending the first
selector. I've also thought it would be nice to have something to
automatically refactor Sass-output CSS files to minimize repetition of
styles.
On Thu, Apr 28, 2011 at 9:00 PM, Mario "Kuroir" Ricalde
Nathan; I understand the problem with conventions. But think about this: we use them already on compiling files.For instance we have "_file.scss" which won't get compiled but can be included. Anyone who's not familiar with the feature to look at "_file.scss" has no idea what it does.That brings.. why don't we do it via. Which is basically a class (without the dot); meaning it's not usable in the DOM since you'll never have that generated !_my-abstract {color:red;}.something { @extend _my-abstract; }
--