#1 At: http://code.google.com/webtoolkit/doc/latest/DevGuideClientBundle.html#CssResourceCookbook
It says: External and legacy scopes In many cases, newly-developed CSS will need to be combined with external or legacy CSS. The @external at-rule can be used to suppress selector obfuscation while still allowing programmatic access to the selector name. Question: Why would anyone ever want obfuscation on? If I have a CSS selector ".myheader" wouldn't I always want to refer to it as: MyResources.INSTANCE.css().myheader()? #2 At: http://code.google.com/webtoolkit/doc/latest/DevGuideClientBundle.html#Selector_obfuscation_details It says: Strict scoping In the normal case, any class selectors that do not match String accessor functions is an error. This behavior can be disabled by adding a @NotStrict annotation to the CSS accessor method. Enabling @NotStrict behavior is only recommended for applications that are transitioning from external CSS files to CssResource. Even with CssResource isn't all the CSS stored in a separate CSS file? So far, CSS with GWT is a mystery to me. -- 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.
