Add Compass components? about jointswp HOT 6 CLOSED

I haven't dove into Compass too much, but I would LOVE to see how you have implemented it. I'm sure a lot of people would find it useful.

from jointswp.

Please see my branch "Add Compass CSS3" here: https://github.com/mrscharf/JointsWP/tree/Add-Compass-CSS3

Basically, only the CSS3 files have been added. Alot of the fancy stuff is in ruby, so Compass would need to be installed on the developer's system for that. Also some of the layout helpers could interfere with Foundation, so those are probably best left out anyway. The CSS3 scss files are pretty straightforward though and save time when doing stuff like making rounded corners, adding font faces, shadows or opacity. Not everything has been tested out yet, so feel free to give it a whirl.

from jointswp.

I really like those, in fact, Joints used to have a Scss file for "Mixins", but I removed it a few versions ago as many of them seemed dated. I'm trying to wrap my head around the best way to do this, as I don't want people getting confused and thinking this includes ALL of the Compass features.

EDIT 1/23/14 - Joints still currently has a mixin.scss file.

from jointswp.

I'd argue against explicitly adding compass support for now. You can't use libsass w/ compass yet.

sass/libsass#82

from jointswp.

I'm not sure why it's necessary to include the Compass files? Maybe I'm missing something, but if I want to use Compass I can just import my locally installed copy.

from jointswp.

This is why I love GitHub - allows everyone to voice their opinion/suggestions on the project.

I tend to agree with Josh and Zane. I see the benefit of having them baked in, as you wouldn't have to add them later. However, as Zane noted, most people would probably prefer to use their own local copy. Also, as Scharf noted, some of the features may conflict.

Joints will continue to use a mixin.scss for any custom mixins.

from jointswp.