> And I'd like to put a reference on the instruction to load the custom > colors file (at least in a source, or maybe in the KitchenSink class, > keeping it commented). > Or for this I could derive a KitchenSinkDarkColors class, but many > things inside KitchenSink are private, what do you think on move them > to protected ? This could be useful to show how nes colors are on all > components ... but again it's not a problem.
Ahh, I see - you want to show people not only how to use a different color scheme, but what every single component will look like in a different color scheme, which is why you want to put this in the kitchen sink demo. That makes sense. Why not use a startup property for this purpose? Loading a new Theme after the default has been loaded takes a noticeable amount of time (something like 500ms IIRC), so make sure that your code only runs if the startup property specifies to do so. And I haven't started the check parameters values in wtk components ... This can definitely wait until 1.3.1, as those are more maintenance release items.
