I was skimming through my log, and noticed a few things that could be brought up here...

First is reusing the icon code for cursors. This is probably a good idea, and for even more reason than thought. One of the additional benefits would be nice fallback to CREATE assets, etc.

I'm fairly up on the various bits of code involved, and also cursor stuff, so definitely hit me up about it.

Oh... and a minor point... the XPM spec (what we use for our cursors currently) allows for the hot X and Y to be in the XPM file itself. I was looking at this a bit, as it would take the position hardcoding out of our source code that loads icons. The default routines don't give you X and Y, but I can add it easily. We probably could fold this in to the other cursor work with minimal effort.

Then there's the whole thing about multiple export. It's actually not to hard to do... and something I'm doing in the Icon Preview dialog. With just a little bit of tuning, that can be refactored to also support multiple-res export. This would be good for icons and cursors, and is very low-hanging fruit in that I can probably get it going in a day or so. Plus there've been enough user requests to make something like that worthwhile.

So... start thinking about how this could be done for the most effect with the least effort. Hitting cursors and icon needs would be the minimum. Roughing this out could help both the export and the preview.

Oh, and one of the other features I was looking at was adding librsvg rendering to the icon preview window. Again, I've done all the research on it and it will take only a small bit of coding (perhaps less than hooking in LittleCms took). I'm wondering if this might be useful as an option for the multi-export, in addition to the preview window.

Anyway, start thinking about all this. There's a lot we can do to combine a few simple things and end up with some powerful workflow tools. UI, command-line invocation and use cases of different types of users could all be helpful.