SmartSprites

Writing to the original CSS files

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: 0.4.0
  • Component/s: None
  • Labels:
    None

Description

Currently, the modified version of CSS style sheets are written to new files, the original files being unmodified. It might be useful to introduce a "one-file" mode whereby all the additional rules get added to the original file, SmartSprites directive being also preserved there. One potential problem with this approach is that we'd need to detect and discard CSS properties added by SmartSprites, so that the style sheet doesnt get longer and longer after each SmartSprites run.

Issue Links

Activity

Hide
Stanisław Osiński added a comment -

Bumping priority.

Show
Stanisław Osiński added a comment - Bumping priority.
Hide
Kevin Vanderbeken added a comment -

This has never been an issue with our development - just some random musings....

We have a development process whereby the production mode of the site simply takes the -sprite.css files instead of the normal ones which only run when the a server environment set to development mode (local machines).

If someone doesn't separate out development modes in this way, perhaps this specified feature is useful.
I do however see a great deal of complexity in the task to discard the previously written properties, unless they are tagged on a line by line basis by a post compilation comment or something on each line which can been "seen" later on again when re-run. This increases file size though.

Our production sites have css combined and minified on first run automatically in production mode as well, so we could mitigate file size increases for extra comments i guess.

Thanks.

Show
Kevin Vanderbeken added a comment - This has never been an issue with our development - just some random musings.... We have a development process whereby the production mode of the site simply takes the -sprite.css files instead of the normal ones which only run when the a server environment set to development mode (local machines). If someone doesn't separate out development modes in this way, perhaps this specified feature is useful. I do however see a great deal of complexity in the task to discard the previously written properties, unless they are tagged on a line by line basis by a post compilation comment or something on each line which can been "seen" later on again when re-run. This increases file size though. Our production sites have css combined and minified on first run automatically in production mode as well, so we could mitigate file size increases for extra comments i guess. Thanks.
Hide
Stanisław Osiński added a comment -

Moving out of the 0.2.4 release.

Show
Stanisław Osiński added a comment - Moving out of the 0.2.4 release.
Hide
Stanisław Osiński added a comment -

Hi guys,

Question: what are the use cases on your side that require the ability to overwrite the original CSS files?

As pointed out by Kevin in the previous comment, depending on the exact requirements, implementation of this feature might be tricky. If I knew what your workflow was like, I could make this feature more useful. Until I get some feedback on this, I'm moving the feature to the 0.4.0 release.

Show
Stanisław Osiński added a comment - Hi guys, Question: what are the use cases on your side that require the ability to overwrite the original CSS files? As pointed out by Kevin in the previous comment, depending on the exact requirements, implementation of this feature might be tricky. If I knew what your workflow was like, I could make this feature more useful. Until I get some feedback on this, I'm moving the feature to the 0.4.0 release.

People

Vote (2)
Watch (1)

Dates

  • Created:
    Updated: