Enabling compass sprite classes to be output as placeholders

[superbland]

Currently this code:

@import "site/*.png";
@include all-site-sprites;

Produces an output that contains a list of classes relating to the background image and positions that can be extended. Since the recent addition of placeholders and the move to prevent extending from within media directives, it will be impossible to extend these classes without potentially having massive amounts of duplicate code within the media query.

Using placeholders instead of classes (or allowing a choice) would mean that a mixin containing sprite css could be included without unnecessary duplication.

[silvenon]

Unfortunately, Sass doesn't seem to be able to extend placeholders beyond the @media block (and probably classes too, I haven't tried it yet). Nevertheless, it's a great suggestion, I'll implement it when I find the time.

Yeah, there will be a choice, the default will be class for backwards compatibility.

[aaronjensen]

+1

[silvenon]

I forgot about this... Don't count on me because I don't use Compass anymore.

[scottdavis]

Well that is sad news

[silvenon]

Probably not permanently, it's just because it's so messy in its current state. I'll see if I'll go on a fixing spree later.

[morewry]

In the meantime, a workaround option for using placeholder classes with Compass sprites https://gist.github.com/morewry/4151748

[scottdavis]

So are you advocating that the default be placeholders? this is a pretty simple change just need to get the option of those pushing for it.

[morewry]

Placeholders as the default? Maybe; don't feel strongly about which the default should be. Opting for placeholders instead of classes? Yes, I'd like to see that option.

[scottdavis]

Anyone feel like doing a pull request?

[aaronjensen]

Is there a decision on how it should be done? I like the idea of placeholders by default but that would be a breaking change for many. It probably makes more sense to do classes by default for the @include all-site-sprites; but placeholders by default for @import "site/*.png"; since maybe people aren't using the initial class that the import creates other than via mixin?

[scottdavis]

Its ok to do a breaking change with a new version release (0.13). So I'm ok setting placeholders to default. The framework functions and mixins would need to be updated along with the content.erb in the sprite importer folder, and all the test files.

[lucasconstantino]

Any news on this?

[morewry]

https://gist.github.com/morewry/6613650 (different from before) done using sprite-map and sprite-names. So far as I know still no config option that will change behavior of @include all-site-sprites, but perhaps someone else will know differently.

[scottdavis]

Probably get to it this weekend I've set aside some time to work on compass

Sent from my iPhone

On Oct 4, 2013, at 3:32 PM, Lucas Constantino Silva notifications@github.com wrote:

Any news on this?

—
Reply to this email directly or view it on GitHub.

[chriseppstein]

Its ok to do a breaking change with a new version release (0.13).

Nope. not ok. We can deprecate in 0.13 and break in the next release. It's never ok to break an API without first deprecating the usage that will break.