> About GWT generators not being supported anymore, does this include the
> ClientBundle? The generators I overridden (*AbstractResourceGenerator*)
> is heavily used in ClientBundle (like for TextResource etc..), and I didn't
> think they were going to remove that.
>
All stuff that is based o
Hi,
Thanks for the reply :). Yes that's the solution I selected, it's just sad
that it won't work "magically" (and require adding a line in resources),
but I guess it's not that bad. I didn't think about the code pruning
issues, good catch.
About GWT generators not being supported anymore, doe
> Is there a solution to tell GWT that my ClientBundle needs to be refreshed
> at every compilation?
>
No. Also your solution defeats any code pruning because of the generated
switch statements that references all the component templates that might or
might not be used by a given application.
Hi,
I'm currently working on a GWT 2.8/Vue.JS integration.
To make it easy to use I had the idea of automatically finding the
Components views, a little like ui.xml in GWT user.
So my idea is this:
I created my own *AbstractResourceGenerator* called
*VueTemplateStoreGenerator*. It generates a
