[gwt-contrib] Re: ImmutableResourceBundle deprecated, move to ClientBundle
On Tue, Apr 14, 2009 at 9:02 AM, dflorey wrote: > Good news! Are there plans to consolidate ClientBundle and i18n > messages & constants? > It would be very nice to have a single bundle for all resources of a > widget to streamline the widget cusomization. As an interim step, look at GwtCreateResource. It's not particularly elegant, but it does allow for arbitrary consolidation of resources into a single interface. On a longer term, it wouldn't be too hard to incorporate the current I18N interfaces in ClientBundle. -- Bob Vawter Google Web Toolkit Team --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: ImmutableResourceBundle deprecated, move to ClientBundle
Good news! Are there plans to consolidate ClientBundle and i18n messages & constants? It would be very nice to have a single bundle for all resources of a widget to streamline the widget cusomization. On 14 Apr., 01:55, BobV wrote: > I've deprecated the public ImmutableResourceBundle interfaces in the > incubator project to encourage users to migrate to the ClientBundle > series of interfaces that are now part of GWT trunk. The IRB code in > the incubator project will not be removed for the foreseeable future, > but all future development will take place in trunk. > > A summary of the user-visible changes is in the following wiki page: > http://code.google.com/p/google-web-toolkit/wiki/ClientBundle#Migrati... > > ClientBundle and IRB can be compiled into the same module, however the > data-types are not generally interchangeable, nor will a hybrid > approach necessarily yield optimal results. If you have any > significant difficulties migrating your code base from > ImmutableResourceBundle to ClientBundle, let me know. > > -- > Bob Vawter > Google Web Toolkit Team --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
