In my opinion as someone still evaluating the software (and who hasn't bought yet), you should be concentrating on making the program work well: import fast, fix the speed of "detailed image info", display 20D raw files correctly, implement versioning/stacks, make a copy of the original before editing, etc.

The UI of PicaJet is quite good. Skinning the program won't improve the UI or make the problem spots any less problematic. I would be shocked if anybody is using PicaJet solely because it looks different from the competitors!

What about some people who doesn't care about skins. You should add this answer to your questionnary. (How do you use it ? What do I have to do to answer to the questionnary ?)

Personnaly, I do not care about skins (and do not use them). I agree totally whith Danwolfgang, it would be better to spend time and efforts to improve capabilities, add more features, repair some bugs (if there is still some), support more IPTC fields, work on database, .... instead to try and create graphic works or graphic art.
What is the most important thing for an image software management ? skins ? hmmm. I'm not sure at all.
Yes, I agree, the sofware has to be pleasant to use. Isn't it the case now with default skin ?

Since I'm the one begging for an unskinned version, I probably have to explain my opinion a little more:

I like the user interface of PicaJet.

I don't like that I have to use a skin for the program. This is especially annoying since I like to change my Windows XP visual styles now and then. So PicaJet never matches my actual skin (aka visual style) I'm using with Windows XP.

When I have a lot of (serious) work to do (e.g. working with my photos), I almost always switch back to 'Windows Classic' since skins get somewhat annoying after you've used them for a while.

So if PicaJet would use standard Windows gui elements (dialog boxes, buttons etc.) it would automatically use the visual style selected for XP.

To make it clear, I'm not talking of the workspace. That's quite good as it is.

Take a look at MediaMonkey. They use skins for their app by default. But you are able to switch this off. Then it uses standard windows elements which in the style you've selected for windows.

I voted for "I don't care", but I suppose I care a bit. I use Window Blinds to suit my own UI tastes (generally minimal). I'd prefer the application match the look I choose - be it via Window Blinds or Windows own style choices.

PicaJet is a photo management program, browse the forums and there is a lot of things you'r users care about: better iptc support, easer editing (ala picasa) and so on - I say: focus about the things that matter first._________________HelgeH

Please, look at winamp 5. It supports skins, but the program for long time was buggy and now it works much more slowly than without skin support. I think it will be better if it has sympathetic, easy and above all FAST user interface. But color schemes of workspace solution is rather good.
Idea is to make able to select only main color by user, and all other colors and hue will be calculated automatically. (Such as in CSS: scrollbar-base-color)

I like the color shemes (as an option to the default system color) but I think "skin" is not, in any way, a feature that PicaJet 3.0 should implement.

The reason is simple: since Windows XP (and even with 98/Me with WindowBlinds) the system "skin" is really better and I really like to see all applications with the same theme. I don't use to purchase application that uses just the old style Windows 98/Me.

And Windows Vista (aero glass) is another major reason to make PicaJet system theme compatible.

I really hope to use PicaJet and all its great features with Windows Vista theme.

Finally, I read the Microsoft Windows Vista guideline (for developers) and I understand that the programmer should focus in functionality, using all system features, making his application integrated with Windows (system). So that's the way! System theme support!