I just want to chime in and let you know that in my case migrating away from GWT Material Design with UiBinder, JSNI and bundle resource in favor of JsInterop+Elemental 2 and the UI layer with Web Components/Polymer 2.0 took a couple of months.
There is a growing number of reusable web components at https://www.webcomponents.org/, with the Vaadin components like the vaadin-grid worth mentioning. In the end it made my architecture much better with a clear separation between the UI layer and the Model/Presenter (business logic) layers in Java. See more info in my G+ post: https://plus.google.com/+AndersForsell/posts/NpTm1Ga8eMM I am now looking forward to the benefits in using J2CL and hope that Google continues to be open and share their work with the open-source community. Anders On Monday, May 22, 2017 at 9:25:38 PM UTC+2, Learner Evermore wrote: > > > On Monday, May 22, 2017 at 2:55:01 PM UTC-4, stuckagain wrote: >> >> But sometimes it is a good moment to reflect on the choices that were >> made. With Java 8 support in place I have the tendency to do things >> different anyway. >> >> That is only possible if: > > a) You have complete control over the entire codebase above GWT > -OR- > b) You have complete control over the entire codebase above GWT except for > some libraries you use but that will address this internally. > -OR- > c) You have completely abstracted everything (GWT *and* any 3rd party > libraries) from the code you don't control. > > Case (a) can be plenty of work but is possible. > Case (b) could actually be less work than (a) but you may need to wait for > 3rd party libraries to catch up. Will GXT catch up, for example? > Case (c) does is plenty of work upfront and rarely done . > > There are those of us who fall into none of the above. We have built upon > GWT and have let others who build their solutions on top of our foundation > enjoy it too. Trouble is that, even if we decide to implement the bits > to-be-missing in GWT 3.0 ourselves, we can't. It isn't possible without > official (but non-existent) hooks into the compiler. That is for GWT RPC. > For widgets it is not possible for other reasons in a general case (but > does not directly hit me as we haven't allowed anyone else to use JSNI or > custom code generators- only foundation code uses a bit of JSNI where there > was no other choice and that's it). However, it is a great big challenge as > there are many GWT libraries out there that depend on this and that can't > work at all without multiple of those bits - some paid, some free. > > -- 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/a1e616a1-6c8e-4ab4-a831-f46dcc166061%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
