Update to Sass 3.2

[iainvdw]

Sass has been updated to version 3.2:
http://sass-lang.com/docs/yardoc/file.SASS_CHANGELOG.html

Could SassAndCoffee be updated to this version?

[slopesidecreative]

I second that motion. With a pretty please. We'd sure like to be able to use "respond-to" in our current project...please.

[mindcrash]

Uhm, mixins already work to a certain extent with SaC 2.0.2.0. I know because I just succesfully compiled a sass file with a mixin using the OrangeBits compiler extension for WebMatrix (which uses SassAndCoffee.Ruby for handling scss and sass files)

So maybe it doesn't have the latest and greatest features but it's still useful anyway ;)

[slopesidecreative]

We're using "respond-to" which requires 3.2 of Sass. My bad for calling it a mix-in. For now, we're just manually compiling the files from .scss to .css, but would like to automate in the future.

[panec]

Is this a possible anyway? This project looks dead to me, and I really need SASS 3.2 support.
Are there any alternatives?

[iainvdw]

This project seems dead, alas. It's been months since any of the lead developers responded to any ticket and there have been no commits as well... We've switched to using Mindscape's Web Workbench in Visual studio to compile the Sass files to CSS during development as we experienced stability and caching issues with SassAndCoffee. Web Workbench does have Sass 3.2 and Compass support now, so I advise using that instead of SassAndCoffee.

[panec]

I did the same for the development, but one of my requirements is that style files can be altered outside VS and they have to work either. Also I'm experiencing some slowness when I'm editing sass files (VS stops responding for couple of seconds, every time I write new selector, even when I have disabled intellisense for sass files).
So no hope to do it when file is requested... :|

[iainvdw]

Outside of VS there are alternatives for compiling Sass files. Use the command line, or one of the (excellent) apps for Windows or Mac.

Apart from that, I've stepped away from the idea that Sass files should be handled by a server and that they should be in working order before they are uploaded. Compiling during development handles that. If it doesn't work, it doesn't compile and you don't want that to happen on a server when someone uploads a modified file and your CSS gets borked because the modification doesn't compile. Also, the authors of Sass (and even LESS and consorts) never meant for those files to be compiled by a server, not on a live site anyway.

[slopesidecreative]

Our solution was to compile the SASS 3.2 before uploading to the server.
Easy enough to do. And you can set the command line or other programs to
watch and automagically compile your SASS (as mentioned), which makes it a
breeze.

Erik

On Thu, Oct 11, 2012 at 7:04 AM, Iain van der Wiel <notifications@github.com

wrote:

Outside of VS there are alternatives for compiling Sass files. Use the
command line, or one of the (excellent) apps for Windows or Mac.

Apart from that, I've stepped away from the idea that Sass files should be
handled by a server and that they should be in working order before they
are uploaded. Compiling during development handles that. If it doesn't
work, it doesn't compile and you don't want that to happen on a server when
someone uploads a modified file and your CSS gets borked because the
modification doesn't compile. Also, the authors of Sass (and even LESS and
consorts) never meant for those files to be compiled by a server, not on a
live site anyway.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-9340930.