What John said. There are a few difficult design problems in doing this properly -- i.e., with no overhead for those just using plain CSS, nor for those using CssResource/ClientBundle "themes". I am confident the problem is soluble, though.
On Mon, Jan 4, 2010 at 10:21 AM, John LaBanca <[email protected]> wrote: > We definitely plan to use ClientBundles to provide default stylings for all > widgets, but we haven't really talked about how to go about doing that yet. > Ideally, we want to use ClientBundles without breaking apps that are > already using the existing CSS style themes. > > We could add ClientBundles to all widgets to serve as a default style, and > we can also provide a DeferredBinding to an "Unstyled" ClientBundle for each > widget. If a user inherits one of the existing CSS style themes, the > Standard/Chrome/Dark.gwt.xml files will inherit the Unstyled deferred > binding, thus disabling the ClientBundles for backway compatibility. > > Thanks, > John LaBanca > [email protected] > > > > On Mon, Jan 4, 2010 at 10:04 AM, BobV <[email protected]> wrote: > >> On Sun, Jan 3, 2010 at 6:10 AM, dflorey <[email protected]> wrote: >> > It would be great if the new ClientBundle would be used to style all >> > gwt widgets. >> >> I think John probably has some ideas here. >> >> > (btw: Why is it called ClientBundle and not ResourceBundle as it >> > bundles up different resources...) >> >> To avoid the conflict with java.util.ResourceBundle. >> >> -- >> Bob Vawter >> Google Web Toolkit Team >> > > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
