3 ms·
One interesting this is that all JS_ exports in their libraries have been removed. This kills support for things like GWT DevMode [0] among other plugins. Thi
by kyrra 13y ago
One interesting this is that all JS_ exports in their libraries have been removed. This kills support for things like GWT DevMode [0] among other plugins. This is good for security, bad for GWT.
[0] https://groups.google.com/forum/#!topic/Google-Web-Toolkit/QSEjbhhHB4g https://groups.google.com/forum/#!topic/Google-Web-Toolkit/Q...
- cromwellian 13y agoYes, we knew this was long in coming. Chrome is yanking similar support in NPAPI as well. That's why 2 years ago we started working on SuperDevMode. This happened a little quicker than we had planned, but some upcoming changes to the GWT compiler will make it an incremental compiler more like JavaC, and in SuperDevMode, compile/refresh should be much much quicker when that lands. On the IDE side, IntelliJ 13.0.2 can attach a debugger to Chrome and provide an in-IDE java debugging experience using source maps. Similar work is ongoing from James Nelson for the Eclipse plugin. Firefox recently added support for column number support in stack traces, so eventually, Java IDE debugging using sourcemaps attached to Firefox JS debugger should be feasible. In the mean time, GWT developers who use Firefox will need to stick to Firefox ESRs.