Creating new ResourceGenerators is trivial, and requires no changes to GWT (one of the best features of ClientBundle). See TextResourceGenerator for an example.
Dan, I'm afraid you can't expect anyone from the GWT team to jump on this problem in Q1. We're saturated. On Sun, Jan 24, 2010 at 5:12 AM, dflorey <[email protected]> wrote: > Any news on this idea? It would be very nice to have Messages/ > Constants as available resource types to bundle all resources in one > place. > > > On Jan 4, 5:26 pm, John Tamplin <[email protected]> wrote: > > On Mon, Jan 4, 2010 at 11:24 AM, BobV <[email protected]> wrote: > > > On Mon, Jan 4, 2010 at 11:17 AM, dflorey <[email protected]> > wrote: > > > > The only show stopper I see right is that Messages/Contacts are not > > > > yet part of the ClientBundle, so I came up with something like this > > > > (copy&paste from branch source): > > > > > You can bridge them with a GwtCreateResource or add a new > > > ResourceGenerator type to ClientBundle that will make Messages / > > > Constants a first-class resource type. > > > > How hard would it be to allow a method returning some subtype of > > LocalizableResource in ClientBundle, and have the generated code just do > > GWT.create on it automatically? > > > > -- > > John A. Tamplin > > Software Engineer (GWT), Google > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
