I think once 2.8 is out the door we should definitely pursue setting up
some projects to tackle the things that won't be in J2CL. This will really
help a lot to alleviate many peoples fears, especially those with large
projects that use Widgets, UiBinder etc.
There has been a lot of vague
Sorry, I didn't mean to keep a big "monolithic" project like we have now
(I'm +1000 on modularization!), it can very well be a new "project", built
separately, released at a different pace, etc.
My point was that it could be kept under the "GWT Project" umbrella, rather
than a "third party"
I think creating a new project is a good opportunity to start bundling
things out of GWT-SDK as agreed on in the initial roadmap.
On Thu, Apr 28, 2016 at 12:27 AM, Thomas Broyer wrote:
> No need to create a new project; that can live in GWT proper BUT will only
> be
No need to create a new project; that can live in GWT proper BUT will only be
supported by community members (i.e. not Google)
--
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
As a GXT developer at Sencha, we are keenly aware of the community's
concerns around the future of things like Widget, UiBinder, etc. and how
GWT 3 might upend the apple-cart. GWT 3 is still very far away and its
plans very nebulous. It's far too early to talk specifics, but I assure
you
I am assuming that Google isn't really interested in Widgets and UiBinder
for J2CL given their usage of GWT in inbox etc. I could be wrong. Assuming
I am not, I would like to investigate starting up some community projects
for Widget and Uibinder support. These won't be trivial to replace so we
I can't speak for J2CL's timelines, as it is an internal project at this
time. However, it has been stated that it will support GWT's JRE emulation
and JsInterop out of the box, and the expectation is that it will simply be
a transpiler and won't support generators (suggested that projects move