Friday, September 30, 2016

Re: Using Constants based on Environment

Ideally your build tool should put your environment into prod or dev mode and the GWT app shouldn't know/care about it. With Maven / Gradle / Ant you can use "resource filtering" to rewrite resources like property files while being copied to the output folder. 

In that case you would have

Config.properties:
key = ${key}

dev.properties:
key = devValue

prod.properties:
key = prodValue

and the build tool will replace ${key} with the value of one of the other two files before GWT will pick up config.properties.


Otherwise you might try (no idea if it works):

interface Config extends Constants {...}
interface DevConfig extends Config {...} -> create a file DevConfig.properties
interface ProdConfig extends Config {...} -> create a file ProdConfig.properties

and in Java code

Config config;
if ("dev".equals(System.getProperty("env")) {
  config = GWT.create(DevConfig.class);
} else if ("prod".equals(......)) {
  .....
}

Can't remember, but System.getProperty() might require GWT 2.8.


-- J.

--
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.

Troubleshooting compilation issues?

Any advice on how to trouble shoot code that runs fine in SDM but causes lockups when run in full compiled mode? Using the -draftCompile flag fixes it in compiled mode too. This suggests that something in the optimizations isn't playing nice with the code, but I'm at a bit of a loss for how to figure out what it is. I've observed the behavior on 2.8.0-RC2 & -RC3 (not sure about older versions).

Thanks in advance for any advice!

--
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 google crawler error undefined.cache.js

I was using this

APP_DIR=/var/lib/tomcat8/webapps/vizit/vizit; sudo  ln -s `ls $APP_DIR/*.cache.js | head -n 1` $APP_DIR/undefined.cache.js; ls -lt $APP_DIR/

On Fri, Sep 30, 2016 at 9:36 PM, Zied Hamdi <zhamdi@gmail.com> wrote:
Hi Thomas,

Thanks for the fast reply :), it's been a while we didn't exchange !

I tried set-property-fallback, but this means I have to migrate to a newer gwt version (2.7 or 2.8). The issue is that the compiler for those two versions stops unexpectedly without any error message (it only writes "linking succeeded"). In addition, when it succeeds in compilation, I can't run the app in standard mode : the compiler of the super-dev-mode triggers even if I launch the app in standard mode (and I need to see what happens with the production js)

With all these issues and because the bug is critical to fix as fast as possible, I decided to downgrade back to 2.6.1 where I don't have these unexpected compiling failure without errors ... :-/

Actually I need to find a solution for the 2.6.1 version (where set-property-fallback doesn't apply), I will have more time to understand what happens with the new GWT compilers when this bug will be workarounded...


On Friday, September 30, 2016 at 7:05:06 PM UTC+1, Thomas Broyer wrote:
Have you tried set-property-fallback?

--
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.



--
Vassilis Virvilis

--
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 google crawler error undefined.cache.js

Hi Thomas,

Thanks for the fast reply :), it's been a while we didn't exchange !

I tried set-property-fallback, but this means I have to migrate to a newer gwt version (2.7 or 2.8). The issue is that the compiler for those two versions stops unexpectedly without any error message (it only writes "linking succeeded"). In addition, when it succeeds in compilation, I can't run the app in standard mode : the compiler of the super-dev-mode triggers even if I launch the app in standard mode (and I need to see what happens with the production js)

With all these issues and because the bug is critical to fix as fast as possible, I decided to downgrade back to 2.6.1 where I don't have these unexpected compiling failure without errors ... :-/

Actually I need to find a solution for the 2.6.1 version (where set-property-fallback doesn't apply), I will have more time to understand what happens with the new GWT compilers when this bug will be workarounded...

On Friday, September 30, 2016 at 7:05:06 PM UTC+1, Thomas Broyer wrote:
Have you tried set-property-fallback?

--
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.

GWT google crawler error undefined.cache.js

Have you tried set-property-fallback?

--
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.

GWT google crawler error undefined.cache.js


I have a GWT application http://islamart.tn which fails on google crawling : The 'fetch as google' feature fails with a 'partial' status saying that it can't find undefined.cache.js

After some research, I found that this js is the app js when the user.agent is not recognized

I therefore changed my

UserAgentPropertyGenerator.UserAgent

enum value for gecko to recgnize google bot:

 gecko1_8("return (ua.indexOf('Googlebot') || ua.indexOf('gecko') != -1 || docMode >= 11);");  

In my core GWT module I naturally added the line :

<property-provider name="user.agent" generator="fr.onevu.vume.client.common.UserAgentPropertyGenerator"/>  

I installed 'Chrome UA spoofer" to emulate the Googlebot user.agent request, and what happened is that now I have a warning at startup saying that the runtime value safari is different than the compile time gecko_18

I still see some checking runtime code in the generated js

{$stackDepth_0=stackIndex_0-1;return 'gecko1_8'}$stackDepth_0=stackIndex_0-1;return 'unknown'}  

but those files are very large, and I don't know from which classes they are generated.

Additionally, I had to fall back to the version 2.6.1 since compilation with 2.8.0RC2 and 2.7.0 don't finish the job (for some reasons I don't have the time to investigate now)

Any ideas please?...

I need an answer to one of these questions :

  • How to personalize the runtime user agent check generated code ?
  • How to make googlebot use the gecko_18 version of my app ? 

p.s : I posted this message on http://stackoverflow.com/questions/39796166/gwt-application-crawler-error-undefined-cache-js

--
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.

Using Constants based on Environment

Hi,

I have a client side configuration file Config.properties, in which I store some client properties for the application.

I use this file as:

Config.properties:
key = xyz


Config.java:
public interface Config
 
extends Constants {

 
String key();
}


Now, I want to have 2 versions of this, for dev and production environments.

I differentiate between the environments using the custom properties in different *.gwt.xml files:
<set-property name="env" value="dev"/>
<set-property name="env" value="prod"/>

How can I use 2 versions of the properties (Config_dev.properties and Config_prod.properties) file mapped to the same Java class (Config.java).

I tried doing it with localization (via setting locale property), but I get other localization stuff with it that I don't need.

Thanks,
Harsh

--
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 2.8 RC2 with Polymer : Creating custom element using JsInterop

Well, Vaadin's gwt-polymer-elements have moved to JsInterop 1.0: https://github.com/vaadin/gwt-polymer-elements

On Friday, September 30, 2016 at 3:56:30 PM UTC+2, GAURAV GUPTA wrote:
Thanks Thomas for quick response, do you see any example using GWT elements to create custom elements using Polymer.

Regards,
Gaurav

On Friday, 30 September 2016 17:46:41 UTC+5:30, Thomas Broyer wrote:
JsExport has been replaced by JsType, JsConstructor, JsMethod and JsProperty; see https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0 (link comes from 2.8 beta release notes)

--
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 and Oracle


On Friday, September 30, 2016 at 3:03:33 PM UTC+2, Eric Nissan wrote:
Hey just curious, does Oracle contribute to GWT at all?  I know they are in a battle with Google over Java (android), but one would think they could put that aside and contribute as GWT really does encourage Java usage.

If they ever contributed to GWT, that was undercover ;-)

No, Oracle has been pushing JavaFX for building so-called RIAs; it's a different programming and deployment model, that's going to fail miserably (like Silverlight, and Java applets and web start before them) but well, they're short-sighted and have deep pockets so… (just like they've been pushing J2ME for years after feature phones were almost dead and replaced with iOS and Android smartphones; are about to ship "project jigsaw" in Java 9 when almost everybody turned their back on OSGi, and are only just starting to look at what Java EE could like in the cloud-oriented world we live in for a few years now)

--
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.

GWT 2.8.0 RC3 is here!




-------- Forwarded Message --------
Subject: [gwt-contrib] GWT 2.8.0 RC3 is here!
Date: Thu, 29 Sep 2016 07:54:46 -0700 (PDT)
From: 'Daniel Kurka' via GWT Contributors <google-web-toolkit-contributors@googlegroups.com>
Reply-To: google-web-toolkit-contributors@googlegroups.com
To: GWT Contributors <google-web-toolkit-contributors@googlegroups.com>


Hi all,

I just build the GWT 2.8.0 RC3 and pushed it to maven central. The complete SDK is also available from here.

Please start testing and let us know if you run into any trouble and file bugs.

We are planing to release this as GWT 2.8.0 if we do not here about any serious issues within the next two weeks. The release notes for RC3 will be made available shortly after this notice.

Daniel,
on behalf of the GWT team
--
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/0314b8df-8e83-4721-b424-7adcdf13ca8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8 RC2 with Polymer : Creating custom element using JsInterop

Thanks Thomas for quick response, do you see any example using GWT elements to create custom elements using Polymer.

Regards,
Gaurav

On Friday, 30 September 2016 17:46:41 UTC+5:30, Thomas Broyer wrote:
JsExport has been replaced by JsType, JsConstructor, JsMethod and JsProperty; see https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0 (link comes from 2.8 beta release notes)

--
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.

GWT and Oracle

Hey just curious, does Oracle contribute to GWT at all?  I know they are in a battle with Google over Java (android), but one would think they could put that aside and contribute as GWT really does encourage Java usage.

--
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.

GWT 2.8 RC2 with Polymer : Creating custom element using JsInterop

JsExport has been replaced by JsType, JsConstructor, JsMethod and JsProperty; see https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0 (link comes from 2.8 beta release notes)

--
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.

GWT 2.8 RC2 with Polymer : Creating custom element using JsInterop

As in link here : https://vaadin.com/blog/-/blogs/using-polymer-elements-in-gwt-development

We are using JsExport annotation for creating and using/wrapping GWT element in polymer and  creating custom element. But I think 2.8 RC2 is missing JsExport. can you please provide me solution if we can built something like this using GWT 2.8. RC2?

Thanks,
Gaurav

--
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.

chrome 53 freezes my GWT 2.7 app

Debugging in Chrome is broken for me.
It consumes 100% cpu and hangs.
I use an old Chrome to work.

--
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.

Thursday, September 29, 2016

Re: chrome 53 freezes my GWT 2.7 app

Chrome 54 (Beta) works fine

On Monday, September 26, 2016 at 1:34:37 PM UTC-5, RT wrote:
The app was working fine for a year, and still works in IE and FireFox, but in Chrome 53 it seems to get frozen perhaps after a code splitting point. I can't debug because the Chrome tab is unresponsive.  Is anyone else having issues in Chrome 53?

--
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.

Wednesday, September 28, 2016

Re: CSS exception compiling 2.7.0 app

Make sure gwt-dev.jar is first in class path. Most likely some other libraries you are using are also using flute but with a different/older version than GWT.

-- J.

--
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: CSS exception compiling 2.7.0 app

Hello? Is anybody out there?

I have several GWT apps, I am having this issue with all of them, it's very freaky. The problem stems from one particular css file,  NativeHorizontalScrollbarTransparent.css, which has a defined attribute who's name includes a "_". I'm not a CSS guy, but this seems perfectly legal to me.

Changing this CSS file in the jar file fixes the issue, but that is a horrible solution, the parser appears to be broken(actually, the BNF used by the parser). The exception comes from the flute parser, and as I understand, the BNF does not include the "_", so I think flute is only doing what it knows to be right. So what's the deal? Why doesn't everybody see this issue? 


--
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 Maven project made with WebAppCreator don't work in devmode

I answered on SO: https://stackoverflow.com/a/39750766/116472

On Wednesday, September 28, 2016 at 3:51:20 PM UTC+2, Vit Vyaz wrote:

Hi, all


I have created a GWT project with maven configuration on this way:

webAppCreator -out HelloWorldGWT -templates sample,maven,readme ua.vitvyaz.hellowordgwt.HelloWorldGWT


I tried to run project on devmode:

mvn gwt:devmode


But in the browser I got:

"HTTP ERROR 404


Problem accessing /HelloWorldGWT.html.

Reason: Not Found"

I looked, the directory WEB-INF was empty.


What is wrong in pom.xml? pom.xml:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

<!-- POM file generated with GWT webAppCreator -->
<modelVersion>4.0.0</modelVersion>
<groupId>ua.vitvyaz.hellowordgwt</groupId>
<artifactId>HelloWorldGWT</artifactId>
<packaging>war</packaging>
<version>1.0-SNAPSHOT</version>
<name>ua.vitvyaz.hellowordgwt.HelloWorldGWT</name>

<properties>

<!-- Setting maven.compiler.source to something different to 1.8
needs that you configure the sourceLevel in gwt-maven-plugin since
GWT compiler 2.8 requires 1.8 (see gwt-maven-plugin block below) -->
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>

<!-- Don't let your Mac use a crazy non-standard encoding -->
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
</properties>

<dependencyManagement>
<dependencies>
<!-- ensure all GWT deps use the same version (unless overridden) -->
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt</artifactId>
<version>2.8.0-rc1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>

<dependencies>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-servlet</artifactId>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-dev</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.11</version>
<scope>test</scope>
</dependency>
</dependencies>

<build>
<!-- Output classes directly into the webapp, so that IDEs and "mvn process-classes" update them in DevMode -->
<outputDirectory>${project.build.directory}/${project.build.finalName}/WEB-INF/classes</outputDirectory>

<plugins>

<!-- GWT Maven Plugin-->
<plugin>
<groupId>net.ltgt.gwt.maven</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>1.0-rc-6</version>
<executions>
<execution>
<goals>
<goal>import-sources</goal>
<goal>compile</goal>
<goal>import-test-sources</goal>
<goal>test</goal>
</goals>
</execution>
</executions>
<configuration>
<moduleName>ua.vitvyaz.hellowordgwt.HelloWorldGWT</moduleName>
<moduleShortName>HelloWorldGWT</moduleShortName>
<failOnError>true</failOnError>
<!-- GWT compiler 2.8 requires 1.8, hence define sourceLevel here if you use
a different source language for java compilation -->
<sourceLevel>1.8</sourceLevel>
<!-- Compiler configuration -->
<compilerArgs>
<!-- Ask GWT to create the Story of Your Compile (SOYC) (gwt:compile) -->
<arg>-compileReport</arg>
<arg>-XcompilerMetrics</arg>
</compilerArgs>
<!-- DevMode configuration -->
<warDir>${project.build.directory}/${project.build.finalName}</warDir>
<classpathScope>compile+runtime</classpathScope>
<!-- URL(s) that should be opened by DevMode (gwt:devmode). -->
<startupUrls>
<startupUrl>HelloWorldGWT.html</startupUrl>
</startupUrls>
</configuration>
</plugin>

<!-- Skip normal test execution, we use gwt:test instead -->
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.17</version>
<configuration>
<skip>true</skip>
</configuration>
</plugin>

</plugins>
</build>
</project>

--
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: Window.open does nothing in windows mobile 10 (IEEdge)

Does anyone know if this has been fixed?

http://blog.daniel-kurka.de/2012/05/mobile-webkit-alert-dialog-breaks-touch.html

My problem is with MGWT. It fixes the above bug by using a deferred ScheduledCommand to fire MGWT events e.g. a TapEvent.This is causing me the problem in IEEdge mobile (not desktop) where if you do not call window.open in the context of a native event initiated by the user then the window.open call is ignored. I'm guessing the IEEdge mobile is not as clever as the desktop version and simply blocks all window.open calls if not in the context of a user initiated native event (a form of popup blocking)

I can fix MGWT by simply not deferring these fired events in IEEdge but would like to know if I can remove this fix for all safari permutations (specifically mobile webkit)

Any thoughts would be appreciated. 

On Tuesday, September 27, 2016 at 6:27:07 PM UTC+1, Paul wrote:
Thanks for suggestions. As far as I know you still cannot remote debug mobile IEEdge in visual studio 2015

Anyway I think I have the answer. For some reason if I call window.open in response to a click event or another native event like pointerdown then it works.

If I call window.open in response to a GWT fired event like TapEvent for example (I'm using MGWT which fires tap events when you get a pointerdown followed by a pointerup event) then window.open does not work! You get no error, the call is basically ignored.

Very strange. I'm still investigating.

Cheers
 
On Tuesday, September 27, 2016 at 11:35:49 AM UTC+1, Vassilis Virvilis wrote:
looks like a popup blocker issue... Does an alert command before window open() works? If yes then you don't have problem with the event but with open per se.

Mobile Chromium and mobile Safari have a developer mode with console - when connected to desktop computer. It needs some setup but a console may give a hint.

    Vassilis

On Tue, Sep 27, 2016 at 1:27 PM, Paul <paul....@kirona.com> wrote:
In a simple GWT test project it works. It must be something I'm doing with event capture. My application is complex so I'll have to try and workout what is stopping the window.open just for IEEdge on windows mobile10

IEEdge desktop is fine and so is chrome! Strange.... 


On Tuesday, September 27, 2016 at 10:52:31 AM UTC+1, Paul wrote:
Window.open("http://www.google.co.uk","_blank","")

....does nothing in windows mobile 10 (IEEdge) when running in GWT 2.7

Any ideas?

If I write a simple html page with the above javascript, then the browser happily opens the google page on a new tab.



--
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.



--
Vassilis Virvilis

--
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 2.8 SHNAPSHOT] missing stack trace for 'Should only call onDetach when the widget is attached to the browser's document'

Thomas,
Yes, that is what I ended up doing at the end ....
After some more digging though, I realised there maybe a reason why the stack trace comes like that:

https://github.com/Putnami/putnami-gradle-plugin/issues/49

--
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.

Tuesday, September 27, 2016

Re: [GWT 2.8 SHNAPSHOT] missing stack trace for 'Should only call onDetach when the widget is attached to the browser's document'

How about setting a breakpoint at the throw line in Widget onDetach then?

--
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 2.8 SHNAPSHOT] missing stack trace for 'Should only call onDetach when the widget is attached to the browser's document'

Thanks Jens,
I have my  -style set to DETAILED for the SDM/Compiler, which should be more than enough.  When I do F1 in Chrome Dev Tools, I see these options checked:

Enable JavaScript source maps
Enable CSS source maps



On Tuesday, September 27, 2016 at 11:19:13 AM UTC-7, Jens wrote:
Have you accidentally disabled source map support in Chrome Dev Tools settings? 

If nothing helps and to get your issue solved you can use -style PRETTY as SDM parameter. As far as I know  -XmethodNameDisplayMode ABBREVIATED is only used when setting a break point and looking at the call stack but not when printing stack traces to console.

-- J.

--
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 2.8 SHNAPSHOT] missing stack trace for 'Should only call onDetach when the widget is attached to the browser's document'

Have you accidentally disabled source map support in Chrome Dev Tools settings? 

If nothing helps and to get your issue solved you can use -style PRETTY as SDM parameter. As far as I know  -XmethodNameDisplayMode ABBREVIATED is only used when setting a break point and looking at the call stack but not when printing stack traces to console.

-- J.

--
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 2.8 SHNAPSHOT] missing stack trace for 'Should only call onDetach when the widget is attached to the browser's document'

Paul,
Thanks for reaching out. I only need the stack trace in SDM for now, and I am using the latest GWT 2.8-SNAPSHOT. 
I know about the -XmethodNameDisplayMode flag and tried all its options to no avail, which makes me think that the issue is somewhere else ...

I googled the exception root, and it seems to come from:

java.lang.IllegalStateException: Should only call onDetach when the widget is attached to the browser's document
at com.google.gwt.user.client.ui.Widget.onDetach


When you look at c.g.g.user.client.ui.Widget.onDetach(), one could question if it is really all that necessary to throw exception when the widget is not attached (instead of just do nothing), but that is beyond the point.

The real issue is that SDM (or Chrome Version 53.0.2785.116 m) fails to map the stack trace back to Java sources, making it impossible to trace issues like that. The obfuscated stack trace is not even clickable and i do not understand how it maps back to Java to do this manually . I can see all of my, generated and GWT source codes in the Chrome/Sources tab,  which makes me believe that all source maps are available to the SDM server.

Thanks!













On Tuesday, September 27, 2016 at 6:05:37 AM UTC-7, Paul Stockley wrote:
Is this in a production build or SDM? In SDM you can pass the flag -XmethodNameDisplayMode ABBREVIATED. Then in chrome you will see class/method names in the call stack

On Monday, September 26, 2016 at 5:24:25 PM UTC-4, Hristo Stoyanov wrote:
Hi all,
I wonder if anyone can help me figure out what is causing this - I am getting java.lang.IllegalStateException: Should only call onDetach when the widget is attached to the browser's document . See below. I suspect this is a GWT exception of some kind, but the stack trace is obfuscated and I can not figure out where the problem is. I tried installing my exception handler with no success - the stack trace is still useless:

 Console.log("Exception logger INSTALLED!!!");
        GWT.setUncaughtExceptionHandler(e -> {
            GWT.log("Unhandled exception", e);
 });

This is happening with Errai 4 SNAPSHOT randomly, but if I figure out the stack trace I can get better understanding of what is going on. How do I get the stack trace ? How do I verify that the gwt Code server has all source maps it needs???

Thanks

================================================================================================================================

Current content widget vanished or changed. Not delivering pageHiding event to HomePage.
ErraiConsoleLogHandler.java:87 14:11:26 WARNING [DefaultNavigatingContainer] Got invalid page name "AboutPage". Redirecting to default page.
ErraiConsoleLogHandler.java:87 java.lang.IllegalStateException: Should only call onDetach when the widget is attached to the browser's document
at Unknown.nC_g$(myApp-0.js@8:16163)
at Unknown.TC_g$(myApp-0.js@9:16405)
at Unknown._C_g$(myApp-0.js@9:16452)
at Unknown.kLf_g$(myApp-0.js@9:47908)
at Unknown.WBe_g$(myApp-0.js@18:37314)
at Unknown.aCe_g$(myApp-0.js@14:37371)
at Unknown.nCe_g$(myApp-0.js@14:37481)
at Unknown.ZPj_g$(myApp-0.js@8:114529)
at Unknown.ZBe_g$(myApp-0.js@36:37344)
at Unknown.WPj_g$(myApp-0.js@16:114507)
at Unknown.aOj_g$(myApp-0.js@17:113981)
at Unknown.iAi_g$(myApp-0.js@3:88783)
at Unknown.jAi_g$(myApp-0.js@15:88755)
at Unknown.y2i_g$(myApp-0.js@32:98783)
at Unknown.A2i_g$(myApp-0.js@17:98822)
at Unknown.c6i_g$(myApp-0.js@45:99823)
at Unknown._5i_g$(myApp-0.js@10:99802)
at Unknown.KAi_g$(myApp-0.js@32:88955)
at Unknown.L6i_g$(myApp-0.js@16:100106)
at Unknown.B7i_g$(myApp-0.js@54:100343)
at Unknown.AJj_g$(myApp-0.js@225:112594)
at Unknown.PDj_g$(myApp-0.js@30:110774)
at Unknown.QDj_g$(myApp-0.js@8:110787)
at Unknown.SDj_g$(myApp-0.js@8:110800)
at Unknown.FDj_g$(myApp-0.js@10:110638)
at Unknown.Sii_g$(myApp-0.js@261:83179)
at Unknown.lambda_0_g$(myApp-0.js@27:96)

--
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: Window.open does nothing in windows mobile 10 (IEEdge)

Thanks for suggestions. As far as I know you still cannot remote debug mobile IEEdge in visual studio 2015

Anyway I think I have the answer. For some reason if I call window.open in response to a click event or another native event like pointerdown then it works.

If I call window.open in response to a GWT fired event like TapEvent for example (I'm using MGWT which fires tap events when you get a pointerdown followed by a pointerup event) then window.open does not work! You get no error, the call is basically ignored.

Very strange. I'm still investigating.

Cheers
 
On Tuesday, September 27, 2016 at 11:35:49 AM UTC+1, Vassilis Virvilis wrote:
looks like a popup blocker issue... Does an alert command before window open() works? If yes then you don't have problem with the event but with open per se.

Mobile Chromium and mobile Safari have a developer mode with console - when connected to desktop computer. It needs some setup but a console may give a hint.

    Vassilis

On Tue, Sep 27, 2016 at 1:27 PM, Paul <paul....@kirona.com> wrote:
In a simple GWT test project it works. It must be something I'm doing with event capture. My application is complex so I'll have to try and workout what is stopping the window.open just for IEEdge on windows mobile10

IEEdge desktop is fine and so is chrome! Strange.... 


On Tuesday, September 27, 2016 at 10:52:31 AM UTC+1, Paul wrote:
Window.open("http://www.google.co.uk","_blank","")

....does nothing in windows mobile 10 (IEEdge) when running in GWT 2.7

Any ideas?

If I write a simple html page with the above javascript, then the browser happily opens the google page on a new tab.



--
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.



--
Vassilis Virvilis

--
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.