jebaird@souders.org left a comment on my blog about extending spriteme.com with a drag and drop interface. I really like open source projects but I think SpriteWizard has a different scope than spriteme.org. So I thought I would explain the thought process behind SpriteWizard's design, and why its different than any of the other css generators out there.
Modify existing css is the biggest time issue when it comes to sprites. When using sprite generators like spriteme.com and http://spritegen.website-performance.org/ the process to developing a sprite seems to me to flow like this

• design
• slice
• html + css with sliced images
• create sprite
• modify design css with sprite css

---
if you have additions with the sprite you have to start back at html css and run it through the sprite genertator.

I don't like to have that extra step to maintain/create a sprite, the way I designed spritewizard was to skip the the middle step. And who better to deside how to layout your sprite than you.  The way I envision the sprite design process to work with spritewizard is as follows

• design
• slice
• html+css
• upload slices to spritewizard and customize css selectors to match the html

---
if you need to make changes to the sprite just upload new images. 

I feel that skipping the middle step with creating the design with the sliced images saves a lot of time. If i have the sprite creation process wrong or if you do it differently give your input .