> On Thu, Oct 6, 2011 at 9:09 AM, Tlvenn <tlv...@gmail.com> wrote:
> > Thanks Hampton !

> > Issue 3 is fixed and was a rather stupid one... basically given how
> > the template is passed to sass (as a concatened string within a Java
> > string), double quotes have to be replaced with single quotes.

> > Before : engine = (RubyObject)
> > container.runScriptlet("Sass::Engine.new(\"" + template + "\", {" +
> > params + "})");
> > Now: engine = (RubyObject)
> > container.runScriptlet("Sass::Engine.new(\"" +
> > template.replaceAll("\"", "'") + "\", {" + params + "})");

> > Now the real issues remains and all tied to interpolation.

> > --
> > Chris

> > On Oct 6, 10:21 pm, Hampton Catlin <hcat...@gmail.com> wrote:
> > > Unfortunately, there isn't *official* JRuby support right now. That isn't
> > to say
> > > we aren't more than willing to support it.

> > > Let me look into getting JRuby on my system and see what results we get
> > > for the tests...

> > > -hampton.

> > > On Oct 6, 2011, at 4:35 AM, Tlvenn wrote:

> > > > Hi,

> > > > I am new to Sass and I am trying to use it in our java projects thanks
> > > > to Jruby. All the basic stuff works with some caveats I don't
> > > > understand. I m hoping the nature of errors can help you out pointing
> > > > me into the right direction of what is going on... All the issue seems
> > > > related to interpolation #{}..

> > > > Env: Sass 3.1.7 / JRuby 1.6.4

> > > > Issue 1:
> > > > -------------------------
> > > > $column: 48;
> > > > $gutter: 24;

> > > > $cols1: #{$column + $gutter}em;

> > > >>> (NoMethodError) undefined method `+' for nil:NilClass

> > > > Issue 2:
> > > > --------------------------
> > > > @mixin grid-base(
> > > >  $base-class: grid-column,
> > > >  $first-column-class: g-all-f,
> > > >  $last-column-class: g-all-l
> > > > ) {
> > > >  .#{$first-column-class} { margin-left: 0 !important; clear: left; }
> > > >  .#{$last-column-class} { margin-right: 0 !important; }
> > > > }

> > > >>> (SyntaxError) <script>:6: syntax error, unexpected tRCURLY
> > > > .#{$first-column-class} { margin-left: 0 !important; clear: left; }
> > > >                        ^

> > > > Issue 3:
> > > > --------------------------------
> > > > // If i use single quote instead of double quote, it works...
> > > > input[type="reset"] {
> > > >    cursor: pointer;
> > > >    -webkit-appearance: button;
> > > > }

> > > >>> (SyntaxError) <script>:1: syntax error, unexpected tIDENTIFIER
> > > > Sass::Engine.new("input[type="reset"] {
> > > >                                  ^

> > > > I am pretty sure it is something fairly stupid on my end but I don't
> > > > see what and from my lack of expertise with Sass or Ruby, I need your
> > > > help :)

> > > > Thanks in advance !

> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups "Sass" group.
> > > > To post to this group, send email to sass-lang@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > sass-lang+unsubscribe@googlegroups.com.
> > > > For more options, visit this group athttp://
> > groups.google.com/group/sass-lang?hl=en.

> > --
> > You received this message because you are subscribed to the Google Groups
> > "Sass" group.
> > To post to this group, send email to sass-lang@googlegroups.com.
> > To unsubscribe from this group, send email to
> > sass-lang+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/sass-lang?hl=en.

> Imagine a scenario where you have some nested SASS rules for an
> element, but want these changed if the browser doesn't support a
> certain feature. With current SASS you would need to do something like
> the following

> #page {
>    //some rules
>    .video {
>        display: block;
>    }
> }

> html.no-html-video {
>   #page {
>        .video {
>            display: none;
>        }
>    }
> }

> But if sass had a "prepend to the selector string" operator (I'll use
> ^, though this may not be a sensible choice) you could do the
> following

> #page {
>    //some rules
>    .video {
>        display: block;
>    }

>    ^html.no-html-video { // equivalent to html.no-html-video
> #page .video
>         .video {
>             display: none;
>          }
>    }
> }

> In the example I've given the difference isn't very striking, but when
> you get into several levels of nested rules it could be very useful
> for keeping the CSS statements well-organised and more easily
> maintainable as you only have to have one copy of the nested CSS
> selectors.

> --
> You received this message because you are subscribed to the Google Groups
> "Sass" group.
> To post to this group, send email to sass-lang@googlegroups.com.
> To unsubscribe from this group, send email to
> sass-lang+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/sass-lang?hl=en.

> On Thu, Oct 6, 2011 at 2:12 AM, wheresrhys <wheresr...@gmail.com> wrote:
> > Given the current vogue for feature detection javascript libraries
> > which add classes to the <html> tag, I reckon the following might be a
> > useful (and maybe not too difficult to add) feature for SASS.

> > Imagine a scenario where you have some nested SASS rules for an
> > element, but want these changed if the browser doesn't support a
> > certain feature. With current SASS you would need to do something like
> > the following

> > #page {
> >    //some rules
> >    .video {
> >        display: block;
> >    }
> > }

> > html.no-html-video {
> >   #page {
> >        .video {
> >            display: none;
> >        }
> >    }
> > }

> > But if sass had a "prepend to the selector string" operator (I'll use
> > ^, though this may not be a sensible choice) you could do the
> > following

> > #page {
> >    //some rules
> >    .video {
> >        display: block;
> >    }

> >    ^html.no-html-video { // equivalent to html.no-html-video
> > #page .video
> >         .video {
> >             display: none;
> >          }
> >    }
> > }

> > In the example I've given the difference isn't very striking, but when
> > you get into several levels of nested rules it could be very useful
> > for keeping the CSS statements well-organised and more easily
> > maintainable as you only have to have one copy of the nested CSS
> > selectors.

> > --
> > You received this message because you are subscribed to the Google Groups
> > "Sass" group.
> > To post to this group, send email to sass-lang@googlegroups.com.
> > To unsubscribe from this group, send email to
> > sass-lang+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/sass-lang?hl=en.

> On Thu, Oct 6, 2011 at 2:12 AM, wheresrhys <wheresr...@gmail.com> wrote:
> > Given the current vogue for feature detection javascript libraries
> > which add classes to the <html> tag, I reckon the following might be a
> > useful (and maybe not too difficult to add) feature for SASS.

> > Imagine a scenario where you have some nested SASS rules for an
> > element, but want these changed if the browser doesn't support a
> > certain feature. With current SASS you would need to do something like
> > the following

> > #page {
> >    //some rules
> >    .video {
> >        display: block;
> >    }
> > }

> > html.no-html-video {
> >   #page {
> >        .video {
> >            display: none;
> >        }
> >    }
> > }

> > But if sass had a "prepend to the selector string" operator (I'll use
> > ^, though this may not be a sensible choice) you could do the
> > following

> > #page {
> >    //some rules
> >    .video {
> >        display: block;
> >    }

> >    ^html.no-html-video { // equivalent to html.no-html-video
> > #page .video
> >         .video {
> >             display: none;
> >          }
> >    }
> > }

> > In the example I've given the difference isn't very striking, but when
> > you get into several levels of nested rules it could be very useful
> > for keeping the CSS statements well-organised and more easily
> > maintainable as you only have to have one copy of the nested CSS
> > selectors.

> > --
> > You received this message because you are subscribed to the Google Groups
> > "Sass" group.
> > To post to this group, send email to sass-lang@googlegroups.com.
> > To unsubscribe from this group, send email to
> > sass-lang+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/sass-lang?hl=en.

> .class {
>    font {
>        @if true == true {
>             style: italic;
>        }
>    }
> }

> doesn't work.

> NOt sure if this is a bug to fix or maybe something that shoudl be
> mentioned in the documentation

> --
> You received this message because you are subscribed to the Google Groups
> "Sass" group.
> To post to this group, send email to sass-lang@googlegroups.com.
> To unsubscribe from this group, send email to
> sass-lang+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/sass-lang?hl=en.

> On Thu, Oct 6, 2011 at 4:09 AM, wheresrhys <wheresr...@gmail.com> wrote:
> > While writing some mixins I just realised that putting a control
> > directive inside a nested property doesn't work. So

> > .class {
> >    font {
> >        @if true == true {
> >             style: italic;
> >        }
> >    }
> > }

> > doesn't work.

> > NOt sure if this is a bug to fix or maybe something that shoudl be
> > mentioned in the documentation

> > --
> > You received this message because you are subscribed to the Google Groups
> > "Sass" group.
> > To post to this group, send email to sass-lang@googlegroups.com.
> > To unsubscribe from this group, send email to
> > sass-lang+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/sass-lang?hl=en.