and have other reasons
1. debugging speed reason
2. Is it possible to hire someone who is willing to use GWT?
lofid...@gmail.com 于2021年3月4日周四 下午6:46写道：
> ... and in the beginning everything is small and fast but you'll see the
> same problem (also with pure JS or any other technologies) if you
agree.
Cheers.
lofid...@gmail.com 于2021年3月4日周四 下午6:46写道：
> ... and in the beginning everything is small and fast but you'll see the
> same problem (also with pure JS or any other technologies) if you build one
> huge app...
>
> This is similar to the backend problem... Monolith vs. Microservice
In fact, We just did it like you're saying, every project composes with a
different maven module.
But , one difference is , the final output material is one xxx.nocache.js .
the sense may cause build speed too slowly.
Could you describe " separate the project (Maven, etc) in smaller projects
and
... and in the beginning everything is small and fast but you'll see the
same problem (also with pure JS or any other technologies) if you build one
huge app...
This is similar to the backend problem... Monolith vs. Microservice -->
Monolith UI vs. Micro UI...
lofid...@gmail.com schrieb am
Thanks for the information!
Why don't you just separate the project (Maven, etc) in smaller projects
and integrate them just in the HTML files DOM / ScriptInjector?
So in general you could build many Micro UIs (many JS files) in GWT and
integrate them in one HTML DOM or put them together
For the client/GWT Maven info see:
https://jitpack.io/#CherokeeLanguage/gwt-oauth2
For the server side I'm using com.google.api-client:google-api-client
On Thu, Mar 4, 2021 at 2:18 AM Luca Morettoni wrote:
> is there a maven package with that patch or you have included directly the
>
