I'm working on an app where we decided to create CSS resources under the 
source tree as usual, but only setting properties that affect layout, like 
display, float, sizing, positioning, etc.  The look of the app is under 
control of design-oriented folks that aren't GWT-savvy, who want to be able 
to adjust things like colors, backgrounds, etc., without having to 
recompile and retest. Their CSS files are located in the war directory.

Currently, our source-tree-based CSS uses all @external class names, and we 
then pull in the war-based CSS files via RequestBuilder, and inject them 
into the app. I've provided the design folks with a list of the class names 
that we apply in the GWT code, and a map of where they are used, so that 
they can set their colors, etc.

I think that there might be a way to use the compiled CSSResource artifacts 
on the server side, by requesting a servlet instead of a plain CSS file, 
and then processing the CSS files the way the compiler does, but at 
runtime. That way I can use class name obfuscation, and all the nice things 
like @def and @eval. (I might end up using a servlet or JSP anyway, in 
order to ensure that the war CSS files don't try to set certain properties, 
but it would be nice if I could also use the resource processing logic.)

But, before I venture down that road, I figured I'd see if that is indeed 
possible, and if anyone has tried that, or has found an alternative way to 
defer the CSS until runtime.

-- 
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].
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to