Skip to content

Rewrote PR #1303 and added a test #1310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

Conversation

Raibaz
Copy link

@Raibaz Raibaz commented Jun 4, 2013

Changed width and height calculations according to @chriseppstein's comments and added a test that specifically tests the total width and height smart layout in a case with spacing.

(And also removed whitespace and pushed on master instead of stable)

This does not fix the "spacing on the edges" issue, but IMO is still better than having the smart layout not consider spacing.

if image
row = Compass::SassExtensions::Sprites::ImageRow.new(width + 2 * image.spacing)
else
row = Compass::SassExtensions::Sprites::ImageRow.new(width + 2 * @images[0].spacing)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would DRY this up a bit and calculate the width before calling ImageRow.new within the if statement.

@scottdavis
Copy link
Member

Tests are failing.
https://travis-ci.org/chriseppstein/compass/builds/7773247
ignore the sass_master gemfile tests

Mattia Tommasone added 2 commits June 6, 2013 17:43
@Raibaz
Copy link
Author

Raibaz commented Jun 14, 2013

How do I ignore the sass_master gemfile tests to make the tests pass?

@ghost ghost assigned chriseppstein Jul 23, 2013
@ghost ghost assigned scottdavis Dec 3, 2013
@chriseppstein
Copy link
Member

Scott has done a bunch of refactoring for the sprites and has extracted sprites to their own rubygem etc.

I'm closing this PR because there's been too much change since it was initially submitted. Sorry, We're going to do better going forward. Hopefully, someone can resubmit the change against 1.0. Features should be submitted to the master branch, bug fixes to the stable branch.

@chriseppstein
Copy link
Member

Should be on top of the changes coming in #1771.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants