Google Web Toolkit: July 2018

Tuesday, July 31, 2018

Re: GWT behaves differently in Chrom vs Firefox

Michael:

I appreciate you sharing the information. I never considered Gradle to build, may be it's time.

Thank You

--Velu

On Monday, July 30, 2018 at 3:47:30 PM UTC-4, Michael Joyner wrote:

tasks.withType(org.wisepersist.gradle.plugins.gwt.AbstractGwtActionTask) {

args "-noincremental"

}

gwt {

logLevel = 'INFO'

maxHeapSize = "2048M";

gwtVersion='2.8.2'

modules 'xxx

//src += files("build/generated/source/apt/main");

compiler {

//ea = false //enable assert statements for testing result conditions

strict = true;

style = "OBF";

//style = "PRETTY";

//style = "DETAILED";

localWorkers = 4;

}

superDev {

noPrecompile = true;

failOnError = false;

bindAddress = "0.0.0.0";

}

eclipse {

addGwtContainer = true;

}

}

On Mon, Jul 30, 2018 at 3:44 PM, Velusamy Velu <kool...@gmail.com> wrote:
Michael & David

After clearing the TEMP folder and clearing the compiler caches at localhost:9876 that error message disappeared.

Thanks a lot

Velusamy K. Velu
614-321-9649

On Mon, Jul 30, 2018 at 3:18 PM Jens <jens.ne...@gmail.com> wrote:

Hi Michael: I tried this by Windows > Preferences > General > Workspace > Build and unchecked the "Build automatically" option. It didn't help. Am I doing the right thing? Is there any other option?

GWT SuperDevMode has its own cache that you can clear by visiting the SuperDevMode page (localhost:9876) and hit the small clean button at the bottom. Once you have done that SDM starts from scratch and compiles everything again.

-- J.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/IYcu87xv4RA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT behaves differently in Chrom vs Firefox

Jens:

Thank you, it helped.

--Velu

On Monday, July 30, 2018 at 3:18:12 PM UTC-4, Jens wrote:

Hi Michael: I tried this by Windows > Preferences > General > Workspace > Build and unchecked the "Build automatically" option. It didn't help. Am I doing the right thing? Is there any other option?

GWT SuperDevMode has its own cache that you can clear by visiting the SuperDevMode page (localhost:9876) and hit the small clean button at the bottom. Once you have done that SDM starts from scratch and compiles everything again.

-- J.

Monday, July 30, 2018

Re: GWT behaves differently in Chrom vs Firefox

tasks.withType(org.wisepersist.gradle.plugins.gwt.AbstractGwtActionTask) {

args "-noincremental"

}

gwt {

logLevel = 'INFO'

maxHeapSize = "2048M";

gwtVersion='2.8.2'

modules 'xxx

//src += files("build/generated/source/apt/main");

compiler {

//ea = false //enable assert statements for testing result conditions

strict = true;

style = "OBF";

//style = "PRETTY";

//style = "DETAILED";

localWorkers = 4;

}

superDev {

noPrecompile = true;

failOnError = false;

bindAddress = "0.0.0.0";

}

eclipse {

addGwtContainer = true;

}

On Mon, Jul 30, 2018 at 3:44 PM, Velusamy Velu <kool.velu@gmail.com> wrote:

Michael & David

After clearing the TEMP folder and clearing the compiler caches at localhost:9876 that error message disappeared.

Thanks a lot

Velusamy K. Velu
614-321-9649

On Mon, Jul 30, 2018 at 3:18 PM Jens <jens.nehlmeier@gmail.com> wrote:

Hi Michael: I tried this by Windows > Preferences > General > Workspace > Build and unchecked the "Build automatically" option. It didn't help. Am I doing the right thing? Is there any other option?

GWT SuperDevMode has its own cache that you can clear by visiting the SuperDevMode page (localhost:9876) and hit the small clean button at the bottom. Once you have done that SDM starts from scratch and compiles everything again.

-- J.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/IYcu87xv4RA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT behaves differently in Chrom vs Firefox

Michael & David

After clearing the TEMP folder and clearing the compiler caches at localhost:9876 that error message disappeared.

Thanks a lot

Velusamy K. Velu

614-321-9649

On Mon, Jul 30, 2018 at 3:18 PM Jens <jens.nehlmeier@gmail.com> wrote:

Hi Michael: I tried this by Windows > Preferences > General > Workspace > Build and unchecked the "Build automatically" option. It didn't help. Am I doing the right thing? Is there any other option?

GWT SuperDevMode has its own cache that you can clear by visiting the SuperDevMode page (localhost:9876) and hit the small clean button at the bottom. Once you have done that SDM starts from scratch and compiles everything again.

-- J.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/IYcu87xv4RA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT behaves differently in Chrom vs Firefox

We use Gradle here and we turn off SDM incremental when needed from there.

On Mon, Jul 30, 2018 at 2:58 PM, Velusamy Velu <kool.velu@gmail.com> wrote:

Hi Michael: I tried this by Windows > Preferences > General > Workspace > Build and unchecked the "Build automatically" option. It didn't help. Am I doing the right thing? Is there any other option?

Thanks
Velu

On Tuesday, July 24, 2018 at 11:08:00 AM UTC-4, Michael Joyner wrote:
Is this in SDM mode? If yes, try turning off incremental compilations.

On Mon, Jul 23, 2018 at 9:43 PM, Velusamy Velu <kool...@gmail.com> wrote:
Friends:

I have an application written using GWT 2.8.2 framework and it behaves differently. The snippet of the GWT code in question is here -
(ReferenceError) : L_g_g$ is not defined

for (int j = 1; j < nodes.size(); j++) { Node previousNode = nodes.get(j - 1); Node currentNode = nodes.get(j); int indexFrom = previousNode.getIndex(); int indexTo = currentNode.getIndex(); if (!connectionMatrix[indexFrom][indexTo]) { connectionMatrix[indexFrom][indexTo] = true; connectionMatrix[indexTo][indexFrom] = true; contributed = true; BondTriple bondTriple = new BondTriple(indexFrom, indexTo);

The last line of the above code snippet is the Culprit. It works as expected in FireFox, in Chrome however, it throws "L_g_g$ is not defined" error. In debugger mode I found that L_g_g$ refers to the BondTriple as highlighted here > BondTriple bondTriple = new BondTriple(indexFrom, indexTo);

This code has been thoroughly unit tested and every functionality was verified. The fact that it works in Firefox but fails in Chrome baffles me even more. BondTriple defined as below. I'm using non-primitive attributes to check for null. Have anyone ran into a situation like this? I'm having hard time figuring out what could be wrong. Your help will be greatly appreciated.

public class BondTriple implements Jsonable { private Integer start; private Integer finish; private Integer bondType; private Shape connector; public BondTriple(Integer start, Integer finish) { this.start = start; this.finish = finish; } ...

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT behaves differently in Chrom vs Firefox

Hi Michael: I tried this by Windows > Preferences > General > Workspace > Build and unchecked the "Build automatically" option. It didn't help. Am I doing the right thing? Is there any other option?

GWT SuperDevMode has its own cache that you can clear by visiting the SuperDevMode page (localhost:9876) and hit the small clean button at the bottom. Once you have done that SDM starts from scratch and compiles everything again.

-- J.

Re: GWT behaves differently in Chrom vs Firefox

Hi Michael: I tried this by Windows > Preferences > General > Workspace > Build and unchecked the "Build automatically" option. It didn't help. Am I doing the right thing? Is there any other option?

Thanks

Velu

On Tuesday, July 24, 2018 at 11:08:00 AM UTC-4, Michael Joyner wrote:

Is this in SDM mode? If yes, try turning off incremental compilations.

On Mon, Jul 23, 2018 at 9:43 PM, Velusamy Velu <kool...@gmail.com> wrote:
Friends:

I have an application written using GWT 2.8.2 framework and it behaves differently. The snippet of the GWT code in question is here -
(ReferenceError) : L_g_g$ is not defined

for (int j = 1; j < nodes.size(); j++) { Node previousNode = nodes.get(j - 1); Node currentNode = nodes.get(j); int indexFrom = previousNode.getIndex(); int indexTo = currentNode.getIndex(); if (!connectionMatrix[indexFrom][indexTo]) { connectionMatrix[indexFrom][indexTo] = true; connectionMatrix[indexTo][indexFrom] = true; contributed = true; BondTriple bondTriple = new BondTriple(indexFrom, indexTo);

The last line of the above code snippet is the Culprit. It works as expected in FireFox, in Chrome however, it throws "L_g_g$ is not defined" error. In debugger mode I found that L_g_g$ refers to the BondTriple as highlighted here > BondTriple bondTriple = new BondTriple(indexFrom, indexTo);

This code has been thoroughly unit tested and every functionality was verified. The fact that it works in Firefox but fails in Chrome baffles me even more. BondTriple defined as below. I'm using non-primitive attributes to check for null. Have anyone ran into a situation like this? I'm having hard time figuring out what could be wrong. Your help will be greatly appreciated.

public class BondTriple implements Jsonable { private Integer start; private Integer finish; private Integer bondType; private Shape connector; public BondTriple(Integer start, Integer finish) { this.start = start; this.finish = finish; } ...

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Tuesday, July 24, 2018

Re: GWT 2.8b1: "runAsyncCallback7 is not a function" - compiler error with GWT.runAsync(...)?

We were also getting this issue when we migrated it to 2.8.2. With the upgrade, we had to define a custom linker name instead of overloading the "xsiframe" name like we were doing in 2.7. We thought that was enough but then this error occurred. The fix was to basically replicate this deferred binding that GWT had defined in CrossSiteIframeLinker.gwt.xml, but for our custom linker name.

<replace-with class="com.google.gwt.core.client.impl.ScriptTagLoadingStrategy">
  <when-type-is
    class="com.google.gwt.core.client.impl.AsyncFragmentLoader.LoadingStrategy" />
  <any>
    <when-linker-added name="custom_linker" />
  </any>
</replace-with>

On Wednesday, May 25, 2016 at 10:57:24 AM UTC-7, clou...@gmail.com wrote:

I did add a custom linker in order to get HTTPS sort of working for SDM debugging. A very simple class derived from CrossSiteIframeLinker and only overriding getJsDevModeRedirectHookPermitted(...). No custom linker was used previously.

Feels like a regression to me... I guess I'd need to check what linker was used in GWT 2.5 and which is used during SDM, as the issue didn't manifest in either place (only in production).

Re: GWT behaves differently in Chrom vs Firefox

clear your temp folder, sdm puts lots of stuff there and sometimes it gets corrupted and you get these kind of errrors.

On 24 Jul 2018, 18:53 +0200, Velusamy Velu <kool.velu@gmail.com>, wrote:

Hi Michael

I appreciate your recommendation. Yes it's in SDM mode. I don't have the luxury to try your suggestion right away due to my travel. Will try it on my return.

I did suspect something to the effect of a cache behind this. Hence I tried clearing and rebuilding, it failed yet. Nothing helped so far.

On Tue, Jul 24, 2018, 11:08 AM Michael Joyner <michael@newsrx.com> wrote:

Is this in SDM mode? If yes, try turning off incremental compilations.

On Mon, Jul 23, 2018 at 9:43 PM, Velusamy Velu <kool.velu@gmail.com> wrote:

Friends:

I have an application written using GWT 2.8.2 framework and it behaves differently. The snippet of the GWT code in question is here -

(ReferenceError) : L_g_g$ is not defined

for (int j = 1; j < nodes.size(); j++) { Node previousNode = nodes.get(j - 1); Node currentNode = nodes.get(j); int indexFrom = previousNode.getIndex(); int indexTo = currentNode.getIndex(); if (!connectionMatrix[indexFrom][indexTo]) { connectionMatrix[indexFrom][indexTo] = true; connectionMatrix[indexTo][indexFrom] = true; contributed = true; BondTriple bondTriple = new BondTriple(indexFrom, indexTo);

The last line of the above code snippet is the Culprit. It works as expected in FireFox, in Chrome however, it throws "L_g_g$ is not defined" error. In debugger mode I found that L_g_g$ refers to the BondTriple as highlighted here > BondTriple bondTriple = new BondTriple(indexFrom, indexTo);

This code has been thoroughly unit tested and every functionality was verified. The fact that it works in Firefox but fails in Chrome baffles me even more. BondTriple defined as below. I'm using non-primitive attributes to check for null. Have anyone ran into a situation like this? I'm having hard time figuring out what could be wrong. Your help will be greatly appreciated.

public class BondTriple implements Jsonable { private Integer start; private Integer finish; private Integer bondType; private Shape connector; public BondTriple(Integer start, Integer finish) { this.start = start; this.finish = finish; } ...

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/IYcu87xv4RA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT behaves differently in Chrom vs Firefox

Hi Michael

I appreciate your recommendation. Yes it's in SDM mode. I don't have the luxury to try your suggestion right away due to my travel. Will try it on my return.

I did suspect something to the effect of a cache behind this. Hence I tried clearing and rebuilding, it failed yet. Nothing helped so far.

On Tue, Jul 24, 2018, 11:08 AM Michael Joyner <michael@newsrx.com> wrote:

Is this in SDM mode? If yes, try turning off incremental compilations.

On Mon, Jul 23, 2018 at 9:43 PM, Velusamy Velu <kool.velu@gmail.com> wrote:
Friends:

I have an application written using GWT 2.8.2 framework and it behaves differently. The snippet of the GWT code in question is here -
(ReferenceError) : L_g_g$ is not defined

for (int j = 1; j < nodes.size(); j++) { Node previousNode = nodes.get(j - 1); Node currentNode = nodes.get(j); int indexFrom = previousNode.getIndex(); int indexTo = currentNode.getIndex(); if (!connectionMatrix[indexFrom][indexTo]) { connectionMatrix[indexFrom][indexTo] = true; connectionMatrix[indexTo][indexFrom] = true; contributed = true; BondTriple bondTriple = new BondTriple(indexFrom, indexTo);

The last line of the above code snippet is the Culprit. It works as expected in FireFox, in Chrome however, it throws "L_g_g$ is not defined" error. In debugger mode I found that L_g_g$ refers to the BondTriple as highlighted here > BondTriple bondTriple = new BondTriple(indexFrom, indexTo);

This code has been thoroughly unit tested and every functionality was verified. The fact that it works in Firefox but fails in Chrome baffles me even more. BondTriple defined as below. I'm using non-primitive attributes to check for null. Have anyone ran into a situation like this? I'm having hard time figuring out what could be wrong. Your help will be greatly appreciated.

public class BondTriple implements Jsonable { private Integer start; private Integer finish; private Integer bondType; private Shape connector; public BondTriple(Integer start, Integer finish) { this.start = start; this.finish = finish; } ...

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/IYcu87xv4RA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.