On Thursday, September 8, 2016 at 3:00:36 PM UTC+2, Ahmad Bawaneh wrote: > > Hi > Is there any plans or suggestions for the UiBinder alternatives since > UiBinder will be removed from GWT 3.0? >
*might* be removed would be more accurate. Let me repeat one more time: development on GWT 3.0 has not started yet, not even discussions and preliminary plans (except that Google has been working on J2Cl and GWT 3.0 will be based on it, and that brings many changes to the way you'll develop); nobody knows yet what GWT 3.0 will or won't be (except that it won't have GWT.create() anymore: no more generators, no more deferred binding) And again, there are reasons why GWT 2.x won't be discontinued as soon as GWT 3.x will be released. and i wonder why such cool feature should be removed instead of being > updated to match the new changes? > It has to do with "resource driven" (or "non-java-source driven") code generation. When code is generated based on Java code, it can be done with an annotation processor. But when code is generated based on a non-Java resource, "something" has to trigger the code generation whenever the resource changes; and in the case of UiBinder (and I18N's Constants/Messages, and ClientBundle), the code is generated based on *both* the ui.xml and the Java (so it needs to run as an annotation processor to easily get access to the Java model, but be triggered when the ui.xml changes –and the .java not). It's only/mostly a "problem" of tooling (mostly during development). Far from being insurmontable though. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
