Re: [gwt-contrib] Using GWT libraries from J2CL

2017-05-31 Thread Anders Forsell
Ok, that sounds great! On Wednesday, May 31, 2017 at 10:43:23 PM UTC+2, Goktug Gokdogan wrote: > > J2CL doesn't require @JsType; JsType serves same purpose as in GWT. > > The likely steps required to make GWT library work with J2CL > (future-proofing) already described in multiple talks earlier

Re: [gwt-contrib] Using GWT libraries from J2CL

2017-05-31 Thread 'Goktug Gokdogan' via GWT Contributors
J2CL doesn't require @JsType; JsType serves same purpose as in GWT. The likely steps required to make GWT library work with J2CL (future-proofing) already described in multiple talks earlier but briefly; no JSNI/JSO, no GWT.create, no generators and no com.google.gwt.* references. This applies

[gwt-contrib] Using GWT libraries from J2CL

2017-05-31 Thread Anders Forsell
Hello, >From the small examples of J2CL examples I have seen, the Java classes have been annotated with @JsType. I understand that all Java code will be transpiled to ES6 JS classes with J2CL but can you refer/use other Java classes/libraries without adding specific annotations? More

Re: [gwt-contrib] Digest for google-web-tool...@googlegroups.com - 5 updates in 2 topics

2017-05-31 Thread Daniel Harezlak
OK, it looks like the frame boundaries can be crossed in Firefox which yields reality check : true whereas Chrome produces reality check : false. Thanks for the explanation. Beside the JSNI workaround one can also use jsinterop.base.Js.uncheckedCast() for such cases. -- You received this

[gwt-contrib] Re: Elemental2 1.0.0-beta-1 and casting behaves unexpectedly

2017-05-31 Thread Daniel Harezlak
OK, this this particular use case was explained here: https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/8lESs0WMHDM. Thank you Arnaud. On Wednesday, May 31, 2017 at 7:21:38 PM UTC+2, Daniel Harezlak wrote: > > Js.cast() also throws but Js.uncheckedCast() does not. Can

[gwt-contrib] Re: Elemental2 1.0.0-beta-1 and casting behaves unexpectedly

2017-05-31 Thread Daniel Harezlak
Js.cast() also throws but Js.uncheckedCast() does not. Can anyone elaborate? On Wednesday, May 31, 2017 at 12:06:08 PM UTC+2, gwtt...@gmail.com wrote: > > How about using jsinterop.base.Js.cast() for the casing instead? - see: >

Re: Code references between client/server/shared folders

2017-05-31 Thread Natan
If there are no visual classes, functionality will normally occur. Regarding your comment, javac will always be applied in all classes, regardless of what directory they are in. The classes destined to the sharing between client and server, it is sufficient to implement them without using any

Re: [gwt-contrib] Digest for google-web-toolkit-contributors@googlegroups.com - 5 updates in 2 topics

2017-05-31 Thread Arnaud TOURNIER
About the iframe instanceof problem, I think this is due to the fact that JavaScript prototypes do not cross frame boundaries (for security and privacy reasons). So even in JavaScript, the instanceof operator would not work. You can try this example : let frame =

[gwt-contrib] Re: Elemental2 1.0.0-beta-1 and casting behaves unexpectedly

2017-05-31 Thread Kirill Prazdnikov
Hi, I have the same issue and use the same JSNI hack It is interesting why GWT does runtime type checks for @JsType(isNative = true) ? Why is it reasonable ? -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group

[gwt-contrib] Re: Elemental2 1.0.0-beta-1 and casting behaves unexpectedly

2017-05-31 Thread gwttechg
How about using jsinterop.base.Js.cast() for the casing instead? - see: https://groups.google.com/forum/#!topic/Google-Web-Toolkit/0XGv7EhDFmc On Wednesday, May 31, 2017 at 7:23:20 AM UTC+1, Daniel Harezlak wrote: > > Hi, I have the following code using elemental2-dom: > > HTMLIFrameElement

How to add a GWT module to a dynamically created Iframe

2017-05-31 Thread Gourav Dhelaria
What's the best way to handle this scenario ? - Code wise have I would like to have 2 seperate GWT modules. Modules as defined in this page - Download both modules in a single download, as a js file. - Run one of the modules

[gwt-contrib] Re: Elemental2 1.0.0-beta-1 and casting behaves unexpectedly

2017-05-31 Thread Daniel Harezlak
The way to work around it is to use a native method: private static native HTMLDocument getHtmlDocument(HTMLIFrameElement frame) /*-{ return frame.contentDocument; }-*/; Is this required? On Wednesday, May 31, 2017 at 8:23:20 AM UTC+2, Daniel Harezlak wrote: > > Hi, I have the following

Re: [gwt-contrib] Re: Elemental2 source code on github

2017-05-31 Thread Julien Dramaix
I've enabled the issue tab. On Tue, May 30, 2017 at 11:04 PM Daniel Harezlak wrote: > Hi, it looks like issues are disabled for the > https://github.com/google/elemental2 project. > > > On Saturday, May 20, 2017 at 12:34:09 AM UTC+2, Julien Dramaix wrote: > >> >> If you

GWT module with Jsinterop exports but without an entry point is skipped during production compilation

2017-05-31 Thread Daniel Harezlak
Hi, For a module with Jsinterop exports to be compiled I need to create a dummy entry point, otherwise it is skipped. I have the generateJsInteropExports flag set. The module inherits only from com.google.gwt.user.User and elemental2.dom.Dom modules which I suppose do not have entry points of

[gwt-contrib] Elemental2 1.0.0-beta-1 and casting behaves unexpectedly

2017-05-31 Thread Daniel Harezlak
Hi, I have the following code using elemental2-dom: HTMLIFrameElement frame = (HTMLIFrameElement) DomGlobal.document. createElement("iframe"); HTMLDocument doc = (HTMLDocument) frame.contentDocument; //throws java.lang.ClassCastException The second line throws an exception although I am quite

[gwt-contrib] Re: Elemental2 source code on github

2017-05-31 Thread Daniel Harezlak
Hi, it looks like issues are disabled for the https://github.com/google/elemental2 project. On Saturday, May 20, 2017 at 12:34:09 AM UTC+2, Julien Dramaix wrote: > > If you have any questions/issues, feel free to open a bug in the github > project. > -- You received this message because you