Is that going to be deprecated soon? On Mon, Aug 16, 2010 at 1:20 PM, Nathan Weizenbaum <[email protected]> wrote: > ":prop name" is an older (but still valid) syntax for "prop: name". > > On Mon, Aug 16, 2010 at 2:34 AM, DAZ <[email protected]> wrote: >> >> Thanks Nathan, >> >> I appreciate that start-of-line syntax must make things very >> complicated, so it is probably not worth doing. You're right, it's not >> a huge imposition to have to type out @extend. >> >> If it is possible though, I don't think you should worry about Sass >> becoming a mess of symbols. People will not have to memorise them >> because of the newer, alternative syntax, but people who prefer to >> keep things short can use the shortcut symbols if they wish. >> >> cheers, >> >> DAZ >> ps - what does : at the beginning of a line do? >> >> >> >> >> On Aug 16, 9:58 am, Nathan Weizenbaum <[email protected]> wrote: >> > Any additional start-of-line syntax runs the strong risk of being >> > ambiguous >> > in the indented syntax. We already feel the pain of this with : and +; >> > I'd >> > rather not add more such syntax unless it seems clearly necessary. I >> > don't >> > think typing out @extend is egregious enough to warrant it. >> > >> > I'd also be somewhat worried about Sass becoming a mess of symbols that >> > all >> > had to be memorized. >> > >> > >> > >> > On Sun, Aug 15, 2010 at 11:18 PM, DAZ <[email protected]> wrote: >> > > Thanks for the reply Chris, >> > >> > > That's good to know that + will be kept in. I started using scss, but >> > > actually prefer the shorter syntax of sass. >> > >> > > How about using < to indicate @extends? This would be similar to Ruby >> > > class inheritance. >> > > So for example: >> > >> > > .error >> > > color: red >> > >> > > .bigerror >> > > < error >> > >> > > Does this get in the way of child selectors? If so, how about the >> > > double-angle bracket <<, a bit like appending in Ruby? >> > >> > > .bigerror >> > > << error >> > >> > > Thanks again, >> > >> > > DAZ >> > >> > > On Aug 15, 5:59 pm, Chris Eppstein <[email protected]> wrote: >> > > > @mixin and @include were introduced for scss to avoid introducing >> > > > new >> > > > parsing rules into that syntax. We support the original/shortcut >> > > > syntax >> > > in >> > > > sass files for consistency and do not plan to deprecate them unless >> > > > there >> > > > are changes to the CSS specification require it. >> > >> > > > The examples we use on the website are as similar as possible to >> > > > help >> > > people >> > > > understand easier -- not because of any personal preferences on our >> > > > part. >> > >> > > > As far as @extend goes, we briefly discussed introducing a new >> > > > shortcut >> > > > syntax for it decided to start simple and keep things the same. CSS >> > > > is >> > > such >> > > > a verbose syntax anyway so it didn't seem egregious. I'm not opposed >> > > > to a >> > > > shortcut syntax for @extend in sass files, but I can't think of one >> > > > that >> > > > works well with all the simple selectors extend supports and doesn't >> > > > introduce parsing issues. Did you have something in mind? >> > >> > > > On Sun, Aug 15, 2010 at 8:47 AM, DAZ <[email protected]> wrote: >> > > > > Hi, >> > >> > > > > I've only just started playing around with SASS and realised that >> > > > > you >> > > > > can use + as a shortcut for @include, but this isn't used in any >> > > > > of >> > > > > the examles on the SASS homepage (http://sass-lang.com/), is it >> > > > > going >> > > > > to be deprecated in favour of using @include? >> > >> > > > > Also, is there a similar shortcut symbol for @extend? >> > >> > > > > cheers, >> > >> > > > > DAZ >> > >> > > > > -- >> > > > > 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]<haml%[email protected]>< >> > > >> > > haml%[email protected]<haml%[email protected]> >> > > >. >> > > > > 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 [email protected]. >> > > To unsubscribe from this group, send email to >> > > [email protected] >> > > <haml%[email protected]>. >> > > 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 [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. >> > > -- > 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. >
-- -Richard Aday -- 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.
