> You can start servlets and CodeServer with one click. Indeed, but don't ignore that this requires more setup work, which is not making the overall process simpler. It is extra steps which we are unhappy to embrace.
> Compiling the GWT client code happens automatically on refreshing the browser page. As Thomas said, it has been like this since GWT 2.7 We know that and our recipe relies very much on this, as I expect you have already figured out. > 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. Again, this is an extra step which we are unhappy to embrace. > You do need to run a browser - but that's always required in every scenario. Indeed, but I am more referring to browser URL with CodeServer parameters which is usually created by drag-drop of some CodeServer bookmark. Again, an extra step which we are unhappy having to embrace. > 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. I am referring to browser URL with CodeServer parameters which is usually created by drag-drop of some CodeServer bookmark. Again, an extra step which we are unhappy having to embrace. Finally: We are unhappy having to setup more than one processes, even though all could be probably run with a single click. Besides, with DevMode having been around since birth of GWT and probably one of GWT's best selling points, our recipe relies very much on it and removing it will have an impact to our development workflow. Also, you don't seem to be suggesting any replacement for DevMode, which is another negative part of your approach in my view. We prefer having to adjust the classpath as demonstrated in the example at https://github.com/gwtproject/gwt/issues/9720 until we reach a dead end, at which point we will have to switch to a CodeServer based recipe, even though I doubt this will happen. Overall, I am getting the feeling that you are trying to push everyone to move away from DevMode to ease the GWT maintenance pains but this is not acceptable by us and probably by many other teams worldwide relying on DevMode based recipes. Therefore, I don't see any reason not to keep DevMode as it is today and direct users wanting to take advantage of features not supported by Jetty to use CodeServer instead. Please let's forget removal of DevMode as it won't keep everyone happy. On Sunday, 18 April 2021 at 23:30:26 UTC+1 Paul Robinson wrote: > 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/bbf47e78-25c5-4b49-9e50-3ebed00d05a4n%40googlegroups.com.
