Thomas gets it all correct. I just want to add one thing: If you are happy with the current GWT stack (uibinder + widget ...), stay with it. As I mentioned during the key notes, the GWT 2.8 will be a long maintenance release and you have now everything you need to do a great web app.
Don't try to already migrate an existing application to something that is not there yet. On Mon, Nov 16, 2015 at 1:51 PM Thomas Broyer <[email protected]> wrote: > > > On Monday, November 16, 2015 at 1:28:16 PM UTC+1, stuckagain wrote: >> >> Thanks for all the feedback. But it does not put my mind at rest right >> now. >> >> It would have been much better if GWT 2.8 would have provided at >> least the basis for the future of GUI development - because that was one of >> its main selling points for me. >> >> I understand why element/widget/uibinder are going away, but right now >> there is no low-level alternative that would allow a less painful migration >> later on. >> >> I am not expecting a 100% backward compatibility with 3.0, but at least >> some certainty that the code rewrites will be limited or easy, if we >> restrain from using certain technologies. The only certainty we have right >> now is that GWT 3.0 will compile Java into JavaScript, and all the rest >> will change or will just disappear assuming that there will be 3rd party >> extensions. >> >> If GWT does not offer a basis for widget and UI development then there >> will be multiple incompatible GUI libraries or frameworks that will make it >> difficult to mix. >> > > Web Components to the rescue? > As I just wrote above, Web Components can be written in Java with > JsInterop, and can be consumed quite easily with GWT too (whether the > component was written with GWT or not). > I know that answer won't satisfies you as you have to deal with ancient > IEs, but Google has no such need, and has, over the past year(s?), > expressed its will to simply stop supporting them in GWT altogether (Vaadin > and Sencha were those asking for keeping support in); so they won't invest > in such backwards-compatibility (I'm talking about browser here). > > >> I could take the approach of JsInterop with AngularJS, but Angular 2,x is >> also not going to offer backward compatibility. So I solve one problem and >> end up with another one. >> >> I guess I will be trying UiBinder with GQuery and not rely on Widget for >> my project. The UiBinder might disappear, but we are using mostly plain >> HTML and Bootstrap styles. So we are only interested in binding events. The >> UiBinder templates will be easy to migrate later on. >> >> Any idea what is going on with Singular ? Is it also abandoned or will it >> finally appear after GWT 2.8 is final ? >> > > My impression was that they're waiting for J2CL (but I have absolutely no > insight) > > -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/02a9f89b-1420-4289-be10-f8094decdfe7%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/02a9f89b-1420-4289-be10-f8094decdfe7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7mi3zxByYB2BK2o3M8e-adO-zgOLnG7inqd_RDo4kVcA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
