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 jlaba...@google.com On Mon, Jan 4, 2010 at 10:04 AM, BobV <b...@google.com> wrote: > On Sun, Jan 3, 2010 at 6:10 AM, dflorey <daniel.flo...@gmail.com> 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
