| Issue 11: | sprite image editor | |
| 3 people starred this issue and may be notified of changes. | Back to list |
A huge issue with sprites is maintenance. What if one of the embedded images changes - it's a pain to regenerate the entire sprite. And it's critical not to change any of the other embedded images' positions so their CSS doesn't have to change. During sprite generation, we could add a comment to the PNG that contains the URL and bounding box (top-left, lower-right) of each embedded image. This shouldn't be too much extra data. Later, when changes were necessary, we could have a special spriteme image editor that would recognize each embedded image as a hotspot and let the user rearrange and modify the sprite. To avoid the size increase of the comment, have an option to store this in a separate manifest file that could be used later during editing.
Sep 19, 2009
#1
sergey.c...@gmail.com
Sep 22, 2009
(No comment was entered for this change.)
Summary:
sprite image editor
Sep 22, 2009
(No comment was entered for this change.)
Owner:
jaredhir...@yahoo.com
Nov 17, 2010
spriteutils project will include some work on sprite layout/metadata format for automated builds and more. If SpriteMe (or CoolRunnings to be exact) was able to output the results of spriting in this format (in addition to human-readable Export CSS page), the tool you're talking about could be used universally. Here's a sample of the format envisioned: https://github.com/andrewschaaf/spriteutils/blob/master/samples/sharingbuttons.json |