Thanks for the hint. Any idea why the code server insists on using the xsiframe linker? 5 lines below your suggested fix there is even a check if the primary linker is a descendant of xsiframe.
01 септември 2014, понеделник, 23:00:15 UTC+3, John Stalcup написа: > > err, in master that would be > https://gwt.googlesource.com/gwt.git/+/master/dev/codeserver/java/com/google/gwt/dev/codeserver/Recompiler.java > > and line 327 > > > On Mon, Sep 1, 2014 at 12:58 PM, John Stalcup <sta...@google.com > <javascript:>> wrote: > >> you could try changing line 182 in Recompiler.java to register the "std" >> linker >> https://gwt.googlesource.com/gwt.git/+/2.5.1/dev/codeserver/java/com/google/gwt/dev/codeserver/Recompiler.java >> >> >> On Mon, Sep 1, 2014 at 2:43 AM, Ivan Markov <ivan....@gmail.com >> <javascript:>> wrote: >> >>> Ray, >>> >>> Using the xs linker seems like a bad idea, as it combines the >>> disadvantages of sso and the xsiframe: :) >>> (a) Like xsiframe, it injects <script> tags in the document body via >>> JavaScript, which makes these script tags uneditable via Chrome LiveEdit >>> (b) Like sso, it uses the Module Pattern to wrap all GWT code in a >>> function closure. I doubt that LiveEdit can replace the so-wrapped >>> functions, even if problem (a) was solved somehow. >>> >>> I think a better starting point would be the xsiframe linker, as it at >>> least does not use the Module Pattern (right?) so at least problem (b) is >>> gone. >>> >>> >>> 31 август 2014, неделя, 20:33:13 UTC+3, Ray Cromwell написа: >>>> >>>> Try using the xs linker instead. >>>> >>>> >>>> >>>> On Sun, Aug 31, 2014 at 10:15 AM, Ivan Markov <ivan....@gmail.com> >>>> wrote: >>>> >>>>> (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 google-web-toolkit-contributors+unsubscribe@ >>>>> googlegroups.com. >>>>> 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 >>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/033a0106-49a2-4d66-aed0-5ee07d515c4d%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com >>> <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/6d7bf5da-0ba5-48a1-b2f7-2dec9e74370b%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/6d7bf5da-0ba5-48a1-b2f7-2dec9e74370b%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/ffeaade4-ad02-4483-87e5-f1b9e0730a87%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
