[gwt-contrib] Translated to null.nullField when using JsInterop @JsType

2014-06-30 Thread 田传武
Hello, The newest @JsType feature is really very fascinating, and works in most cases. The only issue i found was the wrong null.nullField javascript output. the compile command: java -cp xxx com.google.gwt.dev.Compiler -war xxx -XnoclassMetadata -XnocheckCasts -XjsInteropMode JS

Re: [gwt-contrib] Translated to null.nullField when using JsInterop @JsType

2014-06-30 Thread 'Ray Cromwell' via GWT Contributors
Can you post the full source for CollaborativeOperation? My guess is the UserID and SessionID fields are being proven by the compiler to be uninstantiated types. Are userId/sessionId simple Strings, or some other type? . On Mon, Jun 30, 2014 at 8:18 AM, 'Daniel Kurka' via GWT Contributors

[gwt-contrib] Dropping IE8 support in useragent-less GWT

2014-06-30 Thread 'Goktug Gokdogan' via GWT Contributors
We are planning to drop support for IE8 if the application doesn't inherit c.g.gwt.useragent.UserAgent and hence not have browser permutations. Nearly all of today's apps inherit User so they will not be affected by this change. In the future more apps will only inherit Core however they

Re: [gwt-contrib] Translated to null.nullField when using JsInterop @JsType

2014-06-30 Thread 田传武
Hi Ray, Here is the source for CollaborativeOperation: https://github.com/goodow/realtime-operation/blob/master/src/main/java/com/goodow/realtime/operation/impl/CollaborativeOperation.java the final project which depends on realtime-operation: https://github.com/goodow/realtime-store (Using the

Re: [gwt-contrib] Translated to null.nullField when using JsInterop @JsType

2014-06-30 Thread 田传武
Hi Daniel, I just tried the code you provided, unfortunately, the explicit class cast workaround does not solve this issue. The translated javascript code is the same as before. Thanks! On Monday, June 30, 2014 11:18:12 PM UTC+8, Daniel Kurka wrote: I have seen this happening before when

[gwt-contrib] Re: Dropping IE8 support in useragent-less GWT

2014-06-30 Thread Colin Alworth
Sounds great, but is there a reason that we're now starting at IE9+ and not IE10+, thus giving us typed arrays, web workers, web sockets, etc? I only ask because the kind of case where you are giving up User (and Widget, RPC, Timer, and other fairly high-level apis) seems to suggest that you

Re: [gwt-contrib] Re: Dropping IE8 support in useragent-less GWT

2014-06-30 Thread 'Goktug Gokdogan' via GWT Contributors
On Mon, Jun 30, 2014 at 8:46 PM, Colin Alworth niloc...@gmail.com wrote: Sounds great, but is there a reason that we're now starting at IE9+ and not IE10+, thus giving us typed arrays, web workers, web sockets, etc? I only ask because the kind of case where you are giving up User (and Widget,