I think the best way is to provide styles in the module. This way you can easily restore the style or add โthemesโ to your controls.
I am doing a similar project which is posted on github ( http://github.com/markovuksanovic/gwt-styles ), so you can check this out. You can download the jar file, include it in your project and indicate in your xml module that you want to use this style .. sth like
<inherits name='gwt.theme.flick.Flick'/>
I would suggest you use the new module for your styles so you can easily switch between styles ... (just change the inherits tag). For example, if one of your widgets used the css class "my-widget", you would have a module "style" (or several modules) that would define this css class (in the css file) - this way you could several modules that implement this css class and switch between them will be as easy as changing the module name in the inherits tag. Thus, you will be beautifully separated code styles that will be independent of the technical implementation of widgets. If you have a few more questions, feel free to ask.
PS I forgot to mention above - pay close attention to how the style module (build.xml) is built, it's a little complicated. You can find more information on creating modules in the following folder http://developerlife.com/tutorials/?p=229
markovuksanovic
source share