On Sat, Apr 17, 2021 at 7:45 PM [email protected] < [email protected]> wrote:
> During development, > with "SuperDevMode"+"Jetty" and "Google Plugin for Eclipse", > GWT client-side code compilation (including the nocache.js files) is done > at runtime by DevMode. > > Any other scenario demands that we, > separately compile the GWT client-side code, > separately run a servlet, > separately deploy the GWT code to the server (both client-side and > server-side), > separately run GWT CodeServer, > then run a browser, > then genearate the CodeServer link etc. > The complexity difference is obvious. > It's not obvious because the 6 steps you listed are not 6 manually executed steps. Let's look at them: (1) You can start servlets and CodeServer with one click. (2) Compiling the GWT client code happens automatically on refreshing the browser page. As Thomas said, it has been like this since GWT 2.7 (3) You don't need to deploy to the server - at least in Eclipse (and probably IntelliJ too) you can run a Jetty server inside Eclipse and have it use the Eclipse-compiled classpath. (4) You do need to run a browser - but that's always required in every scenario. (5) I don't know what you mean by "generate the CodeServer link" - you just point your browser at your servlet Jetty server and everything just works. The only practical difference with the planned change is that you need to configure a servlet engine, and it then runs in two separate processes instead of one. But you can still initiate those two processes with a single click if that's important to you. Paul -- 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/CAGHNWNJVaOOgZMPr0AbBxg1exzsVvQYfUn-PQsLop0iGuyN6rw%40mail.gmail.com.
