> One option is to get source-map support improved > directly in Eclipse/IntelliJ, so that the Javascript-based developer > tools are not used, rather, the IDEs connect to the Browsers via > remote debugging protocols, but the SourceMap/indexing/navigation is > done by Eclipse/IntelliJ. >
A shameless plug: this is anyway what SDBG does already now... Blink's remote debugging protocol has no idea what a sourcemap is, aside from one little string hint telling me what is the name of the sourcemap file associated with script XYZ (which is btw very useful as it saves me from fetching the huge GWT JS output and scanning //# sourceMappingURL=). All the sourcemap parsing and indexing is happening in Eclipse. Of course it is another topic that as of now, SDBG still only supports Chrome. -- 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/fb484556-ef5c-43de-aaaf-cd55856837be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
