My question deals with CssResource and more generally ClientBundle. CssResource's generator considers that CSS sheets are part of the application's source code and thus they are internal and not external. Although it provides many powerful language extensions, minification, optimization and several other very interesting things, a constraint on the project on which I work forbids me to use then because one of our requirements is to have external CSS sheets in order to get the application be really easily customizable.
I know that there is the @external rule that serves to tell to the generator that it has to ignore the property and thus use the external provided one, but it's quite boring to redefine for each widget all CSS sheets just to mean that I want it to ignore all their properties. In addition to the fact that CSS files must be internal, they contain GWT specific expressions (typically @external, @ref, @if...) that are unknown by web designers. All that makes that you need to recompile application each time you change a CSS property. I'm facing this problem with CellTables from the 2.1.0-rc1 release. Most GWT widget don't use obfuscation and CssResources and are good for us, but I noticed that all new widgets seem to use CssResource and from what I understood, the aim is to have all widgets use CssResource mechanism in the future (maybe I'm wrong). I think that using another generator that skips all this processing and only returns the method name could be a not too bad solution. I would like to know whether somebody would have a better solution to this problem. I believe I'm not the only one facing it but I've found no thread in this group talking about that. Although I read ClientBundle's doc page, I may have misunderstood or missed something. Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
