Generally GWT SDK is in maintenance mode which means there is no incentive 
to add new features to GWT. Most current work is done in the compiler, 
emulation and distangling code dependencies to eventually use maven/gradle 
instead of ant.

My main pain point with GWT today is actually CSS. CSS is moving pretty 
fast and GWT is stuck on an old Closure Stylesheets library. Beside that if 
you really just want to make a throw away prototype I think I would learn a 
different JS framework for making such prototypes because you simply have 
to type less code as in GWT with Java. But of course it also depends on the 
complexity of the prototype as well.


1. I remember GWT was in the process of splitting it into many 
(J2CL-compatible) submodules, but other than searching Maven Central, I can 
not find any list of them?


Many of them which are considered completed are available on github 
at https://github.com/orgs/gwtproject/repositories?language=&q=&sort=&type=all

Colin made a google sheet back in the days 
at 
https://docs.google.com/spreadsheets/d/1b1D9fEqRh5lZ8cqMJtYoc_25rfTRvsuJkTtS2vjgi3o/edit?gid=0#gid=0
 
but it might be outdated. I lost track about the status of not yet 
completed projects.


 

2. Is there any better way of integrating recent JavaScript libraries other 
than manually writing my own Elemental2 wrappers? I know Elemental2 
bindings are auto-generated from Closure, so I'm hoping that there may be 
some tools that could generate them at least from TypeScript as well. Not 
that there were not efforts [5]. My prototype would have to work with maps 
and although I see that gwt-ol [6] is still maintained, I'm wondering what 
would be my options if I have to integrate with, for example, Windy API?


Personally I just write JsInterop by hand because most of the time you 
don't need 100% of the API of a third party JS library. Generated code can 
also be a bit clunky as seen in elemental2 . Beside the generator you 
mentioned I don't know any other TS -> JsInterop generator. The one of 
Google is Closure externs -> JsInterop. 

 
 

3. J2CL seems to remain Google's internal toy, right?


Well you can use it but personally I think you are right, it won't be very 
popular outside google. 


-- J.

-- 
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 view this discussion visit 
https://groups.google.com/d/msgid/google-web-toolkit/45c1d045-2b10-4b43-9cc2-2680b3948219n%40googlegroups.com.

Reply via email to