Hi folks,
I wanted to take an informal poll on a Sass 3 design issue. We're planning
on adding a new prefix character for variables, "$", because "!" doesn't
really feel right to us and many people we've talked to. I'll expand more
upon this in a blog posts soon, but for now I wanted to ask you th
I think variables should not contain a prefix (like in plain ruby). $
looks like PHP and ! is too strange :)
I like this:
=border-radius(radius)
border-radius = radius
-moz-border-radius = radius
-webkit-border-radius = radius
Looks more clean. What you think?
Em 06/03/2010, às 20:28,
I'm in favor of simplification (only one option) as well as the
switch. A bit more work, but nothing we can't handle.
Cheers,
-e
On Mar 6, 6:28 pm, Nathan Weizenbaum wrote:
> Hi folks,
>
> I wanted to take an informal poll on a Sass 3 design issue. We're planning
> on adding a new prefix charac
We were originally planning to go this direction. Unfortunately, we're also
planning on getting rid of the need for "=", so you can use variables with
":". In this case, variables need a prefix so they're not ambiguous with
normal property values.
On Sat, Mar 6, 2010 at 3:38 PM, Gabriel Sobrinho
In this case, I think the $ will be more readable. Are you planning to
do this?
=border-radius($radius)
border-radius: $radius
Em 06/03/2010, às 20:43, Nathan Weizenbaum escreveu:
We were originally planning to go this direction. Unfortunately,
we're also planning on getting rid of the ne
Yes, that's exactly what we're going for.
On Sat, Mar 6, 2010 at 3:45 PM, Gabriel Sobrinho wrote:
> In this case, I think the $ will be more readable. Are you planning to do
> this?
>
> =border-radius($radius)
> border-radius: $radius
>
> Em 06/03/2010, às 20:43, Nathan Weizenbaum escreveu:
>
I always thought that the "!" prefix tends to be a bit ambiguous
because of its common notion of a logical NOT.
I mean that reading
=column-base(!last = false)
+float-left
@if !last
+last
reads to a Java/Ruby/JavaScript/C/… programmer as "IF NOT LAST" which
is exactly the opposite
I strongly agree that $ will be better than !. As far as deprecations go,
perhaps you could go with first a warning for one release cycle, and then
leave it as a non-default configuration option for another release cycle
before eliminating it entirely.
On Mar 6, 2010 9:13 PM, "Tobias Adam" wrote:
I'd prefer no prefix but would be content with $.
Norman Clarke wrote:
I strongly agree that $ will be better than !. As far as deprecations
go, perhaps you could go with first a warning for one release cycle,
and then leave it as a non-default configuration option for another
release cycle
Let's assume for a second that it didn't create parsing ambiguities.
Would you really prefer:
div
border: width solid blue
over:
div
border: $width solid blue
I think the latter is much more clear from a reader's perspective.
And without the prefix we could also do horrible things like th
10 matches
Mail list logo