Thanks for the input.
1) We decided not to allow .css files to be imported largely for reasons of
consistency. It would be confusing if you could do @import "foo.sass" and
@import "foo.scss", both of which would be equivalent to @import "foo",
while @import "foo.css" would work completely differently. Since Sass is a
CSS3 superset, @import "foo.css" must work as it does in CSS, so we made the
decision to disallow importing of .css files altogether. Yes, it's minorly
annoying to rename them to .scss, but ultimately I think it's worth it to
avoid the confusion of having @import work inconsistently.
2) We've considered adding this feature several times, but two things have
stopped us in the past. The first is that the semantics are unclear; there
are many cases where the selector value would be ambiguous or would might
require full resolution of the cascade to determine exactly. This issue
could potentially be avoided or worked though, but for the second issue: we
have yet to see a convincing use case for directly accessing selector
values. Variables tend to do nearly as good a job of reducing the repetition
in every case we've seen. If you have a use where this isn't true, do show
us and we'll look it over.
- Nathan
On Thu, Mar 17, 2011 at 4:36 AM, Alexander Sergeyev <etorea...@gmail.com>wrote:
> Salute to developers.
>
> Hitherto I have used LESS, and after reading rapturous reviews on SCSS
> (3.0.25) am giving it a try. A few hours of training and converting
> stylesheets passed, and as it frequently happens — joys come with miseries
> hand in hand.
>
> 1. Primary stylesheet (let's call it index.scss) begins with dependencies
> import. SCSS doesn't include *contents of *reset.css, colorbox.css,
> miscjs.css, etc if that files' extension is not .scss (or .sass). But, hey,
> it's not convenient to rename such files if you update them from third-party
> sites. For example, when new version of Colorbox rolls out, I just replace
> old colorbox.css with a new one. Or when Eric Meyer rolls our updated
> Reset.css, I just download & drop it into assets folder of the sites I
> maintain. And now you ask me to complicate things with a renaming step.
>
> My proposal on how imports should be handled:
>
> @import "reset"; // Include contents of reset.(sass|scss|*css*)
> @import "reset.css"; // Leave it as it is, i.e. @import url(reset.css)
>
>
> 2. Neither @extend is applicable nor variables are elegant solution when I
> need to inherit *a **single property *of some element. Maybe I've missed
> something, but with SCSS I can't do as follows
>
> p { color: body['color']; }
>
> --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To post to this group, send email to haml@googlegroups.com.
> To unsubscribe from this group, send email to
> haml+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/haml?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Haml" group.
To post to this group, send email to haml@googlegroups.com.
To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml?hl=en.
