Re: Output ECMAScript 5 strict mode?

[Michael Zhou]

Thanks. Do you plan to pick up that change?

On Wednesday, April 6, 2016 at 5:38:37 PM UTC-4, Andrei Korzhevskii wrote:
>
> Back in the days as I remember, I overrid linker for that so it wraps gwt 
> code in aanonymous function call and inserts  "use strict;" into it
> Something like that: https://gwt-review.googlesource.com/#/c/7710
>
> On Thursday, April 7, 2016 at 12:25:33 AM UTC+3, Michael Zhou wrote:
>>
>> Bump. Anyone?
>>
>> On Sunday, March 27, 2016 at 4:01:05 PM UTC-4, Michael Zhou wrote:
>>>
>>> Is there a way to force GWT to output JS that is in ECMAScript 5 strict 
>>> mode (ie. with the "use strict;" directive)?
>>>
>>

-- 
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+unsubscr...@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-contrib] Can't run SourceMapTest in Eclipse

[Michael Zhou]

Thanks! Including gwt-dev.jar and gwt-user.jar does work.

On Wednesday, April 6, 2016 at 7:08:44 PM UTC-4, Roberto Lublinerman wrote:
>
> I am not sure what should be included. I use our internal setup that has 
> all those targets configured correctly already. In the open source build I 
> normally build the distributions and then inlcude gwt-dev.jar and 
> gwt-user.jar, IIRC.
>
> On Wed, Apr 6, 2016 at 2:24 PM, Michael Zhou  > wrote:
>
>> Got:
>> Loading inherited module 'com.google.gwt.sample.hello.Hello'
>>Loading inherited module 'com.google.gwt.user.User'
>>   Loading inherited module 'com.google.gwt.event.Event'
>>  Loading inherited module 'com.google.gwt.dom.DOM'
>> Loading inherited module 'com.google.gwt.safehtml.SafeHtml'
>>Loading inherited module 'com.google.gwt.http.HTTP'
>>   Loading inherited module 
>> 'com.google.gwt.xhr.XMLHttpRequest'
>>  Loading inherited module 
>> 'com.google.gwt.typedarrays.TypedArrays'
>> Loading inherited module 
>> 'com.google.gwt.useragent.UserAgent'
>>[ERROR] Line 26: Unable to load class 
>> 'com.google.gwt.useragent.rebind.UserAgentPropertyGenerator'
>> java.lang.ClassNotFoundException: 
>> com.google.gwt.useragent.rebind.UserAgentPropertyGenerator
>>
>> I think my classpath has included all the folders needed:
>> gwt-dev/core/super/
>> gwt-dev/core/test/
>> gwt-user/core/super/
>> gwt-user/core/src/
>> gwt-user/core/test-super/
>> gwt/user/core/test/
>> Hello/core/
>> gwt-dev/
>>
>> Found https://groups.google.com/forum/#!topic/repo-discuss/LpzJZv1GGvI 
>> but didn't see a solution there.
>>
>> -- 
>> 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/a43d2e44-5b20-4897-b234-9975b2130da3%40googlegroups.com
>>  
>> 
>> .
>> 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/35567590-ece0-4966-aa0e-95ddb6f0a7ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Can't run SourceMapTest in Eclipse

['Roberto Lublinerman' via GWT Contributors]

I am not sure what should be included. I use our internal setup that has
all those targets configured correctly already. In the open source build I
normally build the distributions and then inlcude gwt-dev.jar and
gwt-user.jar, IIRC.

On Wed, Apr 6, 2016 at 2:24 PM, Michael Zhou 
wrote:

> Got:
> Loading inherited module 'com.google.gwt.sample.hello.Hello'
>Loading inherited module 'com.google.gwt.user.User'
>   Loading inherited module 'com.google.gwt.event.Event'
>  Loading inherited module 'com.google.gwt.dom.DOM'
> Loading inherited module 'com.google.gwt.safehtml.SafeHtml'
>Loading inherited module 'com.google.gwt.http.HTTP'
>   Loading inherited module
> 'com.google.gwt.xhr.XMLHttpRequest'
>  Loading inherited module
> 'com.google.gwt.typedarrays.TypedArrays'
> Loading inherited module
> 'com.google.gwt.useragent.UserAgent'
>[ERROR] Line 26: Unable to load class
> 'com.google.gwt.useragent.rebind.UserAgentPropertyGenerator'
> java.lang.ClassNotFoundException:
> com.google.gwt.useragent.rebind.UserAgentPropertyGenerator
>
> I think my classpath has included all the folders needed:
> gwt-dev/core/super/
> gwt-dev/core/test/
> gwt-user/core/super/
> gwt-user/core/src/
> gwt-user/core/test-super/
> gwt/user/core/test/
> Hello/core/
> gwt-dev/
>
> Found https://groups.google.com/forum/#!topic/repo-discuss/LpzJZv1GGvI
> but didn't see a solution there.
>
> --
> 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/a43d2e44-5b20-4897-b234-9975b2130da3%40googlegroups.com
> 
> .
> 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/CAC7T7gm1ocX9bLL-Syg6uirzva7LEv9P7Px9H%2BOfPSuJKQGsMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Output ECMAScript 5 strict mode?

[Andrei Korzhevskii]

Back in the days as I remember, I overrid linker for that so it wraps gwt 
code in aanonymous function call and inserts  "use strict;" into it
Something like that: https://gwt-review.googlesource.com/#/c/7710

On Thursday, April 7, 2016 at 12:25:33 AM UTC+3, Michael Zhou wrote:
>
> Bump. Anyone?
>
> On Sunday, March 27, 2016 at 4:01:05 PM UTC-4, Michael Zhou wrote:
>>
>> Is there a way to force GWT to output JS that is in ECMAScript 5 strict 
>> mode (ie. with the "use strict;" directive)?
>>
>

-- 
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+unsubscr...@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: Output ECMAScript 5 strict mode?

[Michael Zhou]

Bump. Anyone?

On Sunday, March 27, 2016 at 4:01:05 PM UTC-4, Michael Zhou wrote:
>
> Is there a way to force GWT to output JS that is in ECMAScript 5 strict 
> mode (ie. with the "use strict;" directive)?
>

-- 
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+unsubscr...@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-contrib] Can't run SourceMapTest in Eclipse

[Michael Zhou]

Got:
Loading inherited module 'com.google.gwt.sample.hello.Hello'
   Loading inherited module 'com.google.gwt.user.User'
  Loading inherited module 'com.google.gwt.event.Event'
 Loading inherited module 'com.google.gwt.dom.DOM'
Loading inherited module 'com.google.gwt.safehtml.SafeHtml'
   Loading inherited module 'com.google.gwt.http.HTTP'
  Loading inherited module 
'com.google.gwt.xhr.XMLHttpRequest'
 Loading inherited module 
'com.google.gwt.typedarrays.TypedArrays'
Loading inherited module 
'com.google.gwt.useragent.UserAgent'
   [ERROR] Line 26: Unable to load class 
'com.google.gwt.useragent.rebind.UserAgentPropertyGenerator'
java.lang.ClassNotFoundException: 
com.google.gwt.useragent.rebind.UserAgentPropertyGenerator

I think my classpath has included all the folders needed:
gwt-dev/core/super/
gwt-dev/core/test/
gwt-user/core/super/
gwt-user/core/src/
gwt-user/core/test-super/
gwt/user/core/test/
Hello/core/
gwt-dev/

Found https://groups.google.com/forum/#!topic/repo-discuss/LpzJZv1GGvI but 
didn't see a solution there.

-- 
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/a43d2e44-5b20-4897-b234-9975b2130da3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: nocache file timestamp is not changing after compiles

[Vassilis Virvilis]

This is a known problem for 2.7

I think it is fixed for 2.8

https://github.com/gwtproject/gwt/issues/9108

So far I am touching the nocache.js after deployment as a workaround
(otherwise all clients have to to Shift+Reload to get the changes and then
there is the fun with the different caching behavior per browser).

I think this kind of bugs warrant a 2.7.x release. Death by paper cut is
what comes to mind. I mean it's not really important but it causes pain in
a surprising manner.


On Wed, Apr 6, 2016 at 10:59 PM, Mike Warne  wrote:

> Hi,
> I am having an issue where my nocache.js file timestamp seems to be locked
> to the GWT.xml module file timestamp.
> So it is difficult to see changes when the app is deployed.
>
>
> I am using the GWT plugin for eclipse, with GWT 2.7.2.0
> I noticed there was a bug fix for this in the GWT project.
>
> Is this fix included in this version of GWT?
>
> Sorry if this is the wrong forum for this, but I though someone here might
> have faced this issue also..
>
> Thanks,
> Mike.
>
> --
> 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+unsubscr...@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+unsubscr...@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.

nocache file timestamp is not changing after compiles

[Mike Warne]

Hi,
I am having an issue where my nocache.js file timestamp seems to be locked 
to the GWT.xml module file timestamp.
So it is difficult to see changes when the app is deployed.


I am using the GWT plugin for eclipse, with GWT 2.7.2.0
I noticed there was a bug fix for this in the GWT project. 

Is this fix included in this version of GWT?

Sorry if this is the wrong forum for this, but I though someone here might 
have faced this issue also..

Thanks,
Mike.

-- 
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+unsubscr...@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 no longer working with Chrome 49

['Daniel Kurka' via GWT Users]

About production issue: Are you sure about this? It's less likely to happen 
in production since many clinit calls will have been stripped by the 
compiler, but its probably still going to happen.

About development: Is there actually a global try catch in your code or is 
this even something else? I am not really familiar with the old GWT linkers 
anymore and how they outputted code.

On Wednesday, April 6, 2016 at 4:47:45 PM UTC+2, TazmanianD wrote:
>
> Thanks so much for the response! You say "all modern versions of GWT". I 
> don't suppose you can be more specific? The 2.8 version hasn't been 
> released yet and we can't upgrade to pre-release versions. We can probably 
> give the beta version a try just to see if it does fix our problem. Is this 
> problem fixed in 2.7? We've been waiting for 2.8 before undertaking the 
> upgrade but it sounds like we need to jump to 2.7 now.
>
> Fortunately for us, this isn't (apparently) a production issue for us yet 
> so we're not in an emergency mode but I gather others may not be so lucky. 
> I posted a reply to a question in the Chrome forum where someone was using 
> GWT 1.6 and upgrading may be even harder for this. I don't suppose you have 
> any other advice for anyone else who may stumble across this and not have 
> an immediate path to upgrade?
>

-- 
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+unsubscr...@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-contrib] Re: Proposal for making Object literals more intuitive to define

[Paul Stockley]

This is the only way you can create a true object literal equivalent in 
JsInterop (i.e. no prototype other than Object) 

The following is as close as you can get to say { prop1 : 1 }

JsType(isNative=true, namespace=JsPackage.GLOBAL, name="Object")
class SomeLiteral() {
   int prop1
}

SomeLiteral o= new SomeLiteral ();

o.prop1 = 1;



On Wednesday, April 6, 2016 at 9:05:49 AM UTC-4, Thomas Broyer wrote:
>
> This has nothing to do with an "Object literal".

-- 
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/de8196f5-e5d8-4687-87e4-bdee0a375941%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT no longer working with Chrome 49

[TazmanianD]

Thanks so much for the response! You say "all modern versions of GWT". I 
don't suppose you can be more specific? The 2.8 version hasn't been 
released yet and we can't upgrade to pre-release versions. We can probably 
give the beta version a try just to see if it does fix our problem. Is this 
problem fixed in 2.7? We've been waiting for 2.8 before undertaking the 
upgrade but it sounds like we need to jump to 2.7 now.

Fortunately for us, this isn't (apparently) a production issue for us yet 
so we're not in an emergency mode but I gather others may not be so lucky. 
I posted a reply to a question in the Chrome forum where someone was using 
GWT 1.6 and upgrading may be even harder for this. I don't suppose you have 
any other advice for anyone else who may stumble across this and not have 
an immediate path to upgrade?

-- 
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+unsubscr...@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-contrib] Proposal for making Object literals more intuitive to define

[Thomas Broyer]

This has nothing to do with an "Object literal".

-- 
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/70c2ab44-ed05-46ad-8bd0-89bcd3795bc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Proposal for making Object literals more intuitive to define

[Paul Stockley]

Would it be possible add support for JsType(literal=true). I am not 
proposing this would work according to the future object literal spec. It 
would just be the equivalent of JsType(isNative=true, 
namespace=JsPackage.GLOBAL, name="Object), I think this would make the code 
a lot more intuitive to follow and express the intention more clearly.

-- 
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/df578eb3-44fb-486e-bb08-483d306a2df0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT no longer working with Chrome 49

['Daniel Kurka' via GWT Users]

Hi,

Chrome 49 enabled lots of ES6 features, 
see: http://v8project.blogspot.de/2016/01/v8-release-49.html

Part of this is the so called sloppy function hosting.

A simple example:


ES5 (old semantics)

ES2015 (new semantics)

Code

try {

 function foo() {

   foo=function(){};

   console.log('hello');

 }

} catch(e) { }

foo(); // overwrites behavior

foo(); // no-op

try {

 function foo() {

   foo=function(){};

   console.log('hello');

 }

} catch(e) { }

foo(); // does not overwrite

foo();

Output

hello

hello

hello


The problem here is the presence of the try catch block and that semantics 
have changed here.
We investigated this a few months back and all modern versions of GWT 
should not be impacted.

So my first recommendation would be to upgrade to GWT 2.8-beta1 and see if 
the issue still exists for you.
 


On Tuesday, April 5, 2016 at 9:38:28 PM UTC+2, TazmanianD wrote:
>
> I'm duplicating a comment I made in the Chrome group but I thought I 
> should cross-post it here as well. We're using GWT 2.5.0 and we're 
> suddenly experiencing massive errors as well although fortunately for us, 
> they only seem to be affecting our development env and not production.
>
> In our case, what I've discovered is that the static initializers for 
> *some* classes are being executed repeatedly. This is fatal for enums as 
> the enum values are recreated each time and they're supposed to be 
> singletons. The result is that EnumMaps for those enums don't work at all. 
> In debugging the code, I found that when the static initializer function 
> reassigns itself to the null function, this works in the function but when 
> the function returns, the function pointer is reset back to where it was 
> originally pointing. This means that next time the initializer is executed, 
> instead of it being a no-op, it runs again. I almost wonder if there's some 
> sort of scope confusion and the function assignment is assigning to the 
> wrong or duplicate function.
>
> And another thing I'll note is that we have soft-permutations enabled in 
> our dev env and when we disable those and generate separate permutations, 
> the problem goes away. I don't see how that can explain what I saw in my 
> debugger but I thought it was worth mentioning.
>
> Unfortunately my attempts at reducing the problem to a simple case have 
> totally failed as when I delete too much, the problem seems to disappear. 
> This unfortunately makes my report here not terribly useful but maybe 
> others can chime in if their seeing the same thing.
>
> But let me try to summarize with some pseudo-code (a simple example like 
> this does *not* exhibit the problem):
>
>
> class MyEnum {
>   static {
> Window.alert("Static Initializer");
>   }
>
>   public void foo() {...}
> }
>
>
> MyEnum instance = new MyEnum();
> instance.foo();
>
> -- When this code is run the alert "Static Initializer" is displayed twice 
> (or more if you have additional usages)
>
> --- Get's compiled into (approximately):
>
> var instance = $clinit$MyEnum(), new MyEnum();
> $clinit$MyEnum(), instance.foo();
>
> function $clinit$MyEnum() {
>   $clinit$MyEnum() = nullFunction; // Disables the static initializer so 
> it doesn't run again
>   $wnd.alert("Static Initializer");
> }
>
> -- What I see in the Chrome debugger is that when $clinit$MyEnum is 
> assigned to the nullFunction, the watch immediately reflects this. However 
> the moment you step back out of the function, the value of "$clinit$MyEnum" 
> returns to the original function.
>

-- 
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+unsubscr...@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.

Building widgets with ElementBuilderFactory + GQuery

[maticpetek]

Hi,
   We are building our one GUI component, which are "basic HTML + CSS3 + 
GQuery". We want this technology to be compatible with GWT 3.0 (base on 
current informations). Because basic HTML is only DIV structure + img / 
input, we are search for simple html template builder. 
And ElementBuilderFactory looks as good candidate. Any information / 
feeling  - will this class survive transformation on GWT 3.0? It doesn't 
look like to be link on Widget system. 
Thank you,
  Regards,
 Matic

-- 
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+unsubscr...@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.