Might it be an idea if the @ClassName annotation allows for an array of
String value's (currently not possible)?
This could solve the problems described above I think. Example:
public interface WidgetStyle extends CssResource {
@ClassName({"Bla", "General"})
String bla(); {
}
General will then be a class name with common style rules defined in his
own file.
you use the file in in the ClientBundle counterpart:
@Source({ "BlaStyle.css", "GeneralStyle.cass" })
WidgetStyle widgetStyle();
You only get a lot of small css files...
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/xc1o7bJFTXQJ.
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.
