Re: [gwt-contrib] JSInterop & @JsProperty overriding name

2015-08-11 Thread 'Goktug Gokdogan' via GWT Contributors
>From your description if looks like you are trying following: interface SomeJsInteface { @JsProperty String getName(); } class SomeObject implements SomeJsInterface { public String name; public String getName() { return name; } } Making name field 'public' here is not really a solution. W

Re: [gwt-contrib] JSInterop & @JsProperty overriding name

2015-08-09 Thread Ümit Seren
One more issue that came up. I have a @JsType interface and @JsProperty fields and a class that implements it with public fields and getters/setters. This works fine in DevMode and when compiling with draftCompile = true However as soon as I do a normal production compile the fields get obfus

Re: [gwt-contrib] JSInterop & @JsProperty overriding name

2015-07-30 Thread 'Goktug Gokdogan' via GWT Contributors
Most of the direction changes are presented and discussed in the contributor group but it is not well formed as a document. Before 2.8, the document will be updated with the latest info. This is still a work in progress, we are making sure what will be available with jsinterop will be inline with

Re: [gwt-contrib] JSInterop & @JsProperty overriding name

2015-07-30 Thread Paul Stockley
Is there a better idea of exactly what Js Interop will look like when 2.8 is released. The document referenced above was last updated on Sept 2014. >From this proposal, what will and wont make it into 2.8. This whole area has become very confusing with all the changes in direction that seem to b

Re: [gwt-contrib] JSInterop & @JsProperty overriding name

2015-07-30 Thread Ümit Seren
ok sorry, forget what I said. It actually works fine, when I take the approach that is described in the google docs. On Thursday, July 30, 2015 at 11:49:26 AM UTC+2, Ümit Seren wrote: > > Thanks for the heads up. > > One additional question. I am trying to wrap a 3rd javascript library that

Re: [gwt-contrib] JSInterop & @JsProperty overriding name

2015-07-30 Thread Ümit Seren
Thanks for the heads up. One additional question. I am trying to wrap a 3rd javascript library that is relying on `hasOwnProperty` to check if the object contains a specific property. As far as I can tell the @JsProperty will create a property using `defineProperty`. Is there any way how to

Re: [gwt-contrib] JSInterop & @JsProperty overriding name

2015-07-29 Thread 'Goktug Gokdogan' via GWT Contributors
On Tue, Jul 28, 2015 at 8:36 AM, Ümit Seren wrote: > I started to play around with JSInterop and GWT 2.8.0-SNAPSHOT. > > Primarily I was following these documentation: > > > https://docs.google.com/document/d/1tir74SB-ZWrs-gQ8w-lOEV3oMY6u6lF2MmNivDEihZ4/edit# > > However I ran into some issues re

[gwt-contrib] JSInterop & @JsProperty overriding name

2015-07-29 Thread Ümit Seren
I started to play around with JSInterop and GWT 2.8.0-SNAPSHOT. Primarily I was following these documentation: https://docs.google.com/document/d/1tir74SB-ZWrs-gQ8w-lOEV3oMY6u6lF2MmNivDEihZ4/edit# However I ran into some issues regarding properties that don’t follow Java bean style conventio