Author: b...@google.com
Date: Thu May 21 06:43:38 2009
New Revision: 5451

Modified:
    wiki/CssResource.wiki

Log:
Edited wiki page through web user interface.

Modified: wiki/CssResource.wiki
==============================================================================
--- wiki/CssResource.wiki       (original)
+++ wiki/CssResource.wiki       Thu May 21 06:43:38 2009
@@ -3,7 +3,7 @@

  <wiki:toc max_depth="2" />

-See also the CssResourceCookbook
+See also the CssResourceCookbook and StyleInjector.

  =Goals=

@@ -236,11 +236,10 @@
      .hookClass{} /* Empty and stripped, but left for future expansion */
  }}}
    * The function just returns the CSS class name, but verifies that the  
CSS class exists in the stylesheet.
-    * _TODO_: Add an @external annotation to allow a "binding" to a  
site-wide css file
-  * No typos.
+  * Accessing class names through the interface ensures that there can be  
no typos in code that consumes the CssResource.
    * For obfuscation, we'll use a Adler32 checksum of the source css file  
expressed in base36 as a prefix (7 chars). The developer can override this  
with the `CssResource.obfuscationPrefix` deferred-binding property.
      * `<set-configuration-property name="CssResource.obfuscationPrefix"  
value="empty" />` can be used for minimal-length selector names, but this  
is only recommended when the GWT module has total control over the page.
-  * The `...@external` at-rule can be used to selectively disable obfuscation  
for named selectors; see below for additional detail.
+  * The `...@external` at-rule can be used to selectively disable obfuscation  
for named selectors; see [#External_and_legacy_scopes additional detail].

  = Unplanned use cases =

@@ -576,4 +575,4 @@
    * Other meta-classes
      * @Opacity
      * @RoundedCorners
-      * Can we generalize the meta-classes into an extensible Java  
provider API?
+      * Can we generalize the meta-classes into an extensible Java  
provider API?
\ No newline at end of file

--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---

Reply via email to