Hi all,

I've talked several times about using a Webpack-like devserver instead of 
DevMode, and with a better experience (in most cases) than CodeServer. I 
had described it in more details in 
https://github.com/gwtproject/gwt/issues/9437#issuecomment-250926589

I spent some time this week-end to build a 
prototype: https://github.com/tbroyer/gwt-devserver

There are a few caveats with the current implementation:

   - maybe intercepts a bit too much, so most GWT-RPC calls won't work 
   (they require the gwt.codeserver.port system property on the server side 
   anyway to load the serialization policies from the CodeServer). It could 
   intercept only *.nocache.js requests but that would break some apps that 
   reference resources from the GWT modules' public path (such as themes) from 
   non-GWT resources; or it could only intercept requests for those resources, 
   but that requires more work.
   - loads modules only to get their rename-to; the CodeServer already does 
   that, but doesn't expose the information through public APIs.

If there's consensus, such a tool could be integrated into GWT proper and 
directly use CodeServer's API to share information; and completely replace 
DevMode.

One big advantages (IMO) over DevMode, or CodeServer with -launcherDir, is 
that it doesn't overwrite the *.nocache.js with the compile-on-load stub.
One big drawback is GWT-RPC requires the gwt.codeserver.port system 
property (which requires running the server on the same machine) or using a 
custom serialization policy loader. We could add a -launcherDir where we'd 
write the serialization policies (and only those, possibly also the public 
resources, but not the *.nocache.js stub!)

Feedback welcome!

-- 
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/925d5c77-153b-4e93-ab63-6a2f84a88b63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to