Open GoogleCodeExporter opened 9 years ago
CSS itself can probably be used to get position coordinates for the sprite - as
sprites are not used without CSS.
It's probably worth treating each sprite element as an image in itself in the
interface and display it's boundaries on sprite preview image (I went and
created it
as separate request #65). In this case, it will be easier to just have "upload
new
version" next to each image so user can upload from desktop or point at the URL
to
replace this portion of the sprite with new version.
Original comment by sergey.c...@gmail.com
on 20 Sep 2009 at 2:20
Original comment by stevesou...@gmail.com
on 22 Sep 2009 at 7:43
Original comment by stevesou...@gmail.com
on 22 Sep 2009 at 5:27
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.j
son
Original comment by sergey.c...@gmail.com
on 17 Nov 2010 at 6:27
Original issue reported on code.google.com by
stevesou...@gmail.com
on 1 Sep 2009 at 5:54