(Background: I'm trying to further shorten the edit-compile-debug cycle by playing with hot-code swapping of recompiled JavaScript in Chrome (via Eclipse / SDBG))
GWT 2.7.0-SNAPSHOT, SDM mode, xsiframe linker (obviously), playing with LiveEdit from within Chromedevtools initially: - Editing "<module>.nocache.js" works - However editing "<module>-0.js" does not work (big surprise) Problem 1: I think the "sourceURL=<module>-0.js" line at the end of the script should be present only if CrossSiteIframeLinker is running in "non-pretty / production" mode. In pretty mode, where the <script> tag src attribute is directly modified to point to the CAGFG...AB.cache.js permutation this is probably just bringing confusion, no? Unfortunately, fixing Problem 1 alone did not enable LiveEdit. I think another issue (let's call it Problem 2) is that the xsiframe linker is creating the <iframe> & <script> tags dynamically using JavaScript DOM manipulations. There is some evidence on the internet that editing scripts injected that way is not supported. I was thinking of solving Problem 2 by just switching to the sso (SingleScriptLinker) linker, but then: (a) It is still not supported in SuperDevMode - https://code.google.com/p/google-web-toolkit/issues/detail?id=7722 (b) By looking at the source, it seems it is wrapping all the generated GWT code in enclosing functions, which are then called at the end of the script block. I don't think LiveEdit will be re-evaluating these, so this wrapping has to go somehow... Any ideas? -- 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/033a0106-49a2-4d66-aed0-5ee07d515c4d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
