This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi folks, I just wanted to know if there is work to integrate compass-style.org cause of the implementation of Blueprint CSS in SASS and reusing the components. It isn't possible to import the stuff, cause of the lack changing / adding another LoadPath. |
|
|
|
|
Hi Timur, I've had a quick look through what Compass offers (I knew of the project, but not of the specifics). From what I've gathered, they provide a bunch of additional Sass functions and provide a command line tool for scaffolding up a new site and choosing if you want blueprint (and options for blueprint). From what I can tell you could just bring in their Sass files and Blueprint manually. Now, there's a good chance that I'm:
So at the moment, I don't see that we would be adding scaffolding and setup capabilities at the moment, but, if what you're asking for is just one small bit of what Compass does I'd appreciate some extra information so we can evaluate if it's something we could add. John-Daniel
|
|
|
|
|
For example Compass has an amazing tool to create and manage automatically sprite images, directly from the SCSS. Sprite images permit a cleaner markup, fewer HTTP requests, smaller file sizes and saves bandwidth. In front-end development this is a good practice. And for websites with a lot of traffic, this technique is highly recommended. But the disadvantage of sprites is that it takes much time to do them (in addition of the associated CSS). For me this is the reason why I prefer to use Compass instead of the integrated compiler of Web Workbench.
|
|
|
|
|
Compass is a framework around SASS. It provides some good built-in mixins for styling, etc. I mostly use it for the blueprint support. |
|
|
|
|
Hi, I would also like to register my interest in being able to use the compass compile command as opposed to the sass compile command. The problem with the Sass compiler is this: Usually access to compass mixins is gained by adding something like @import "compass" or @import "compass/css3" to the top of your scss file. However, the sass compiler doesn't understand this and doesn't know where to access the compass mixins. There might be some way around this, but we're trying to integrate both sass and compass into our workflow. We would like all of our designers to be able to use both of these tools with as few barriers to entry as possible. As it is now, Web Workbench gets us halfway there. Please let me know if you decide to add this functionality. Thanks, Josh |
|
|
|
|
It's also the main raison why we are still using the Compass Compiler in my compagny.
@Josh: In the meantime, maybe you could copy paste some of the mixins you are needing in your scss files. You should find some of them here: https://github.com/chriseppstein/compass/tree/stable/frameworks/compass/stylesheets/compass. But it's less convenient. By the way Compass make Sass very powerfull and effective. So I also hope you will plan to integrate it in a next Web Workbench version (I think it would make this plugin even more attractive than it already is). Thanks, |
|
|
|
|
Hi, +1 for compass integration in ww |
|
|
|
|
+1 for compass support from me as well. I was just about to pay for the pro version when I realized I had subconsciously misread "sass and compass" instead of "sass and less." No point in buying the extension as much as I would love to have it if I'm going to be running compass in a shell or fiddling with build events or custom msbuild tasks, etc... Integrated compass support is crucial. |
|
|
|
|
+1 for Compass support |
|
|
|
