Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

['Goktug Gokdogan' via GWT Contributors]

This is a known issue that we will address.

On Thu, Jun 1, 2017 at 12:37 PM, Marcin Okraszewski 
wrote:

> Hi,
> First of all, thanks for working on this.
>
> I have some doubt if *Array* really work on *double* indexes? I know in
> JS every number is floating point, but still, indexes are logically
> integers, it would be more natural to work with integers here. Moreover,
> JsArrayLike interface is using int for interfaces, so it is even not
> consistent in this respect.
>
> I mean for instance those methods of *Array*:
>
>   public native *double *indexOf(T obj, *double *fromIndex);
>
>   public native *double *indexOf(T obj);
>
>
> While in *JsArrayLike *
>
>   default T getAt(*int* index)
>
>   default *int *getLength()
>
>
> Marcin
>
> --
> 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/54f5d447-6dff-
> 4289-a619-1d4a57204c1e%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/CAN%3DyUA1ZKQaAWxi6rcKA4DMPqZ1NETr%3DtS5T07%2BJk0UY4BfeYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Marcin Okraszewski]

Hi,
First of all, thanks for working on this.

I have some doubt if *Array* really work on *double* indexes? I know in JS 
every number is floating point, but still, indexes are logically integers, 
it would be more natural to work with integers here. Moreover, JsArrayLike 
interface is using int for interfaces, so it is even not consistent in this 
respect. 

I mean for instance those methods of *Array*:

  public native *double *indexOf(T obj, *double *fromIndex);

  public native *double *indexOf(T obj);


While in *JsArrayLike *

  default T getAt(*int* index) 

  default *int *getLength() 


Marcin

-- 
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/54f5d447-6dff-4289-a619-1d4a57204c1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Daniel Harezlak]

Hi,
I just tested it and the asFunction method needs the @JsOverlay annotation 
for this to compile. After the modification the code works as expected. 
Thanks!

On Tuesday, May 9, 2017 at 11:32:47 PM UTC+2, Julien Dramaix wrote:
>
> I forgot to mention: as a workaround, you can create your own JsFunction 
> callback and cast it to Function:
> @JsFunction
> interface MyJsFunction {
>   void onInvoke();
>   
>   default Function asFunction() {
> return (Function) this;
>   }
> }
>

-- 
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/4c1bf366-8504-4bc6-83fa-eea2f13c2a85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Daniel Harezlak]

Hi, where did the URL class go? Previously I had it under elemental2.URL.

-- 
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/1cab3cb5-ec09-4912-a20a-87d725b32133%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Predrag Remark]

Great !

-- 
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/609deddf-92bb-4f71-99a9-11cb637168c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Lars]

Looks like the jsinterop generator in on the way :-) 

https://github.com/google/jsinterop-generator

-- 
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/c91ac4cc-848f-4728-8c12-fd690cbb8fc6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

['Goktug Gokdogan' via GWT Contributors]

>  Is it predicated on reaching a certain quality level

Yes. It needs to be at a point that we can comfortable commit to maintain
in the longer term since it will be very like a base for compatibility
across different libraries / APIs.
We have some rough corners that we already aware and we hope to discover
more as developers play with different APIs.

On Thu, May 11, 2017 at 7:11 AM, Paul Stockley  wrote:

> Do you have a general idea for how long the Beta phase will take? Is it
> predicated on reaching a certain quality level?
>
> On Tuesday, May 9, 2017 at 6:06:12 PM UTC-4, Goktug Gokdogan wrote:
>>
>> BTW, if you are using elemental2, keep in mind that these are beta
>> releases to get feedback and APIs will keep changing until we finalize it.
>> So be prepared for breakages in releases until we do the final release cut.
>>
>> On Tue, May 9, 2017 at 2:32 PM, Julien Dramaix 
>> wrote:
>>
>>> I forgot to mention: as a workaround, you can create your own JsFunction
>>> callback and cast it to Function:
>>> @JsFunction
>>> interface MyJsFunction {
>>>   void onInvoke();
>>>
>>>   default Function asFunction() {
>>> return (Function) this;
>>>   }
>>> }
>>>
>>> On Tue, May 9, 2017 at 9:37 AM Julien Dramaix 
>>> wrote:
>>>
 > I believe it's due to how they're declared in the Closure externs:
 onreadystatechange and onerror: https://github.com/go
 ogle/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172d
 f3f/externs/browser/w3c_xml.js#L393-L403
 vs all the other callbacks: https://github.com/
 google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2cca
 ac747722b/externs/browser/html5.js#L2828-L2862

 Yes, the externs use the Function object as type instead of using a
 function type like {function():any}.
 We'll fix that for the next version.

 On Tue, May 9, 2017 at 6:02 AM Thomas Broyer  wrote:

>
>
> On Tuesday, May 9, 2017 at 2:02:40 PM UTC+2, Daniel Harezlak wrote:
>>
>>
>>
>> On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:
>>>
>>>
>>>
>>> On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:

 HI, what are the replacements for elemental2.Global.window and
 similar in this new release?

>>>
>>> elemental2.DomGlobal.window (in elemental2-dom dependency)
>>>
>> Thanks!
>>
>> Another inconsistency with the previous release of elemental2 which
>> broke my code is the use of elemental2.core.Function for the
>> onreadystatechange field in the elemental2.dom.XMLHttpRequest type
>> which prevents providing the function as a lambda. Other function fields 
>> in
>> the mentioned type (e.g. onprogress or onloadstart) seem to keep the
>> functional interface semantics. Is this intended or is it an oversight?
>>
>
> I believe it's due to how they're declared in the Closure externs:
> onreadystatechange and onerror: https://github.com/go
> ogle/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172d
> f3f/externs/browser/w3c_xml.js#L393-L403
> vs all the other callbacks: https://github.com/
> google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2cca
> ac747722b/externs/browser/html5.js#L2828-L2862
>
>
> --
> 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-contributor
> s+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contrib
> utors/e1331a22-74f7-4648-b76b-0a2fb43a2dfc%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/ms
>>> gid/google-web-toolkit-contributors/CABb_3%3D52vj1gbcf_MPq5U
>>> iThib3y0w4nDQHs0Bu8Sb6Ubg5Tyw%40mail.gmail.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+unsubsc

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Paul Stockley]

Do you have a general idea for how long the Beta phase will take? Is it 
predicated on reaching a certain quality level?

On Tuesday, May 9, 2017 at 6:06:12 PM UTC-4, Goktug Gokdogan wrote:
>
> BTW, if you are using elemental2, keep in mind that these are beta 
> releases to get feedback and APIs will keep changing until we finalize it. 
> So be prepared for breakages in releases until we do the final release cut.
>
> On Tue, May 9, 2017 at 2:32 PM, Julien Dramaix  > wrote:
>
>> I forgot to mention: as a workaround, you can create your own JsFunction 
>> callback and cast it to Function:
>> @JsFunction
>> interface MyJsFunction {
>>   void onInvoke();
>>   
>>   default Function asFunction() {
>> return (Function) this;
>>   }
>> }
>>
>> On Tue, May 9, 2017 at 9:37 AM Julien Dramaix > > wrote:
>>
>>> > I believe it's due to how they're declared in the Closure externs:
>>> onreadystatechange and onerror: 
>>> https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
>>> vs all the other callbacks: 
>>> https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
>>>  
>>> Yes, the externs use the Function object as type instead of using a 
>>> function type like {function():any}.
>>> We'll fix that for the next version.
>>>
>>> On Tue, May 9, 2017 at 6:02 AM Thomas Broyer >> > wrote:
>>>


 On Tuesday, May 9, 2017 at 2:02:40 PM UTC+2, Daniel Harezlak wrote:
>
>
>
> On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:
>>
>>
>>
>> On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:
>>>
>>> HI, what are the replacements for elemental2.Global.window and 
>>> similar in this new release?
>>>
>>
>> elemental2.DomGlobal.window (in elemental2-dom dependency) 
>>
> Thanks!
>
> Another inconsistency with the previous release of elemental2 which 
> broke my code is the use of elemental2.core.Function for the 
> onreadystatechange field in the elemental2.dom.XMLHttpRequest type 
> which prevents providing the function as a lambda. Other function fields 
> in 
> the mentioned type (e.g. onprogress or onloadstart) seem to keep the 
> functional interface semantics. Is this intended or is it an oversight?
>

 I believe it's due to how they're declared in the Closure externs:
 onreadystatechange and onerror: 
 https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
 vs all the other callbacks: 
 https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
  

 -- 
 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/e1331a22-74f7-4648-b76b-0a2fb43a2dfc%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/CABb_3%3D52vj1gbcf_MPq5UiThib3y0w4nDQHs0Bu8Sb6Ubg5Tyw%40mail.gmail.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/28a7edbf-d518-4bb0-939d-a421880872b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Ignacio Baca Moreno-Torres]

I see, thanks!

On Wednesday, May 10, 2017 at 9:28:30 AM UTC+2, Thomas Broyer wrote:
>
> It was declared as function(number) not long ago: 
> https://github.com/google/closure-compiler/commit/91500d4cd57a608a442ba7466eb015e9ad40afcf
> So next version of jsinterop JARs should have it right.

-- 
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/dd3ad2b6-c1e4-4113-867a-16896327aef6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Thomas Broyer]

It was declared as function(number) not long ago: 
https://github.com/google/closure-compiler/commit/91500d4cd57a608a442ba7466eb015e9ad40afcf
So next version of jsinterop JARs should have it right.

-- 
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/8a9cb623-2a93-4ebb-bec8-b4234d47a38d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Ignacio Baca Moreno-Torres]

Question about OscilatorNode 
(https://github.com/google/closure-compiler/blob/c77ca197a1f6674e4c267a29a3643a86b61cf51d/externs/browser/w3c_audio.js)

This start method is translated as a "StartCallbackFunction start", should 
it not be translated as a method directly? This callback field cannot be 
called so it doesn't work.
/** @param {number=} when */
OscillatorNode.prototype.start = function(when) {};
Example usage here 
(https://github.com/ibaca/rxbreakout-gwt/blob/master/src/main/java/breakout/client/Breakout.java#L179).

On Wednesday, May 10, 2017 at 12:06:12 AM UTC+2, Goktug Gokdogan wrote:
>
> BTW, if you are using elemental2, keep in mind that these are beta 
> releases to get feedback and APIs will keep changing until we finalize it. 
> So be prepared for breakages in releases until we do the final release cut.
>
> On Tue, May 9, 2017 at 2:32 PM, Julien Dramaix  > wrote:
>
>> I forgot to mention: as a workaround, you can create your own JsFunction 
>> callback and cast it to Function:
>> @JsFunction
>> interface MyJsFunction {
>>   void onInvoke();
>>   
>>   default Function asFunction() {
>> return (Function) this;
>>   }
>> }
>>
>> On Tue, May 9, 2017 at 9:37 AM Julien Dramaix > > wrote:
>>
>>> > I believe it's due to how they're declared in the Closure externs:
>>> onreadystatechange and onerror: 
>>> https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
>>> vs all the other callbacks: 
>>> https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
>>>  
>>> Yes, the externs use the Function object as type instead of using a 
>>> function type like {function():any}.
>>> We'll fix that for the next version.
>>>
>>> On Tue, May 9, 2017 at 6:02 AM Thomas Broyer >> > wrote:
>>>


 On Tuesday, May 9, 2017 at 2:02:40 PM UTC+2, Daniel Harezlak wrote:
>
>
>
> On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:
>>
>>
>>
>> On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:
>>>
>>> HI, what are the replacements for elemental2.Global.window and 
>>> similar in this new release?
>>>
>>
>> elemental2.DomGlobal.window (in elemental2-dom dependency) 
>>
> Thanks!
>
> Another inconsistency with the previous release of elemental2 which 
> broke my code is the use of elemental2.core.Function for the 
> onreadystatechange field in the elemental2.dom.XMLHttpRequest type 
> which prevents providing the function as a lambda. Other function fields 
> in 
> the mentioned type (e.g. onprogress or onloadstart) seem to keep the 
> functional interface semantics. Is this intended or is it an oversight?
>

 I believe it's due to how they're declared in the Closure externs:
 onreadystatechange and onerror: 
 https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
 vs all the other callbacks: 
 https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
  

 -- 
 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/e1331a22-74f7-4648-b76b-0a2fb43a2dfc%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/CABb_3%3D52vj1gbcf_MPq5UiThib3y0w4nDQHs0Bu8Sb6Ubg5Tyw%40mail.gmail.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

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

['Goktug Gokdogan' via GWT Contributors]

BTW, if you are using elemental2, keep in mind that these are beta releases
to get feedback and APIs will keep changing until we finalize it. So be
prepared for breakages in releases until we do the final release cut.

On Tue, May 9, 2017 at 2:32 PM, Julien Dramaix 
wrote:

> I forgot to mention: as a workaround, you can create your own JsFunction
> callback and cast it to Function:
> @JsFunction
> interface MyJsFunction {
>   void onInvoke();
>
>   default Function asFunction() {
> return (Function) this;
>   }
> }
>
> On Tue, May 9, 2017 at 9:37 AM Julien Dramaix 
> wrote:
>
>> > I believe it's due to how they're declared in the Closure externs:
>> onreadystatechange and onerror: https://github.com/
>> google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a13381
>> 72df3f/externs/browser/w3c_xml.js#L393-L403
>> vs all the other callbacks: https://github.com/
>> google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2cc
>> aac747722b/externs/browser/html5.js#L2828-L2862
>>
>> Yes, the externs use the Function object as type instead of using a
>> function type like {function():any}.
>> We'll fix that for the next version.
>>
>> On Tue, May 9, 2017 at 6:02 AM Thomas Broyer  wrote:
>>
>>>
>>>
>>> On Tuesday, May 9, 2017 at 2:02:40 PM UTC+2, Daniel Harezlak wrote:



 On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:
>
>
>
> On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:
>>
>> HI, what are the replacements for elemental2.Global.window and
>> similar in this new release?
>>
>
> elemental2.DomGlobal.window (in elemental2-dom dependency)
>
 Thanks!

 Another inconsistency with the previous release of elemental2 which
 broke my code is the use of elemental2.core.Function for the
 onreadystatechange field in the elemental2.dom.XMLHttpRequest type
 which prevents providing the function as a lambda. Other function fields in
 the mentioned type (e.g. onprogress or onloadstart) seem to keep the
 functional interface semantics. Is this intended or is it an oversight?

>>>
>>> I believe it's due to how they're declared in the Closure externs:
>>> onreadystatechange and onerror: https://github.com/
>>> google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a13381
>>> 72df3f/externs/browser/w3c_xml.js#L393-L403
>>> vs all the other callbacks: https://github.com/
>>> google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2cc
>>> aac747722b/externs/browser/html5.js#L2828-L2862
>>>
>>>
>>> --
>>> 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/e1331a22-74f7-
>>> 4648-b76b-0a2fb43a2dfc%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/CABb_3%3D52vj1gbcf_
> MPq5UiThib3y0w4nDQHs0Bu8Sb6Ubg5Tyw%40mail.gmail.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/CAN%3DyUA06HZJf47%3DudrshQDxYyf53_QoHz_JZx3LfAUwsXWp%2B5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Julien Dramaix]

I forgot to mention: as a workaround, you can create your own JsFunction
callback and cast it to Function:
@JsFunction
interface MyJsFunction {
  void onInvoke();

  default Function asFunction() {
return (Function) this;
  }
}

On Tue, May 9, 2017 at 9:37 AM Julien Dramaix 
wrote:

> > I believe it's due to how they're declared in the Closure externs:
> onreadystatechange and onerror:
> https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
> vs all the other callbacks:
> https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
>
> Yes, the externs use the Function object as type instead of using a
> function type like {function():any}.
> We'll fix that for the next version.
>
> On Tue, May 9, 2017 at 6:02 AM Thomas Broyer  wrote:
>
>>
>>
>> On Tuesday, May 9, 2017 at 2:02:40 PM UTC+2, Daniel Harezlak wrote:
>>>
>>>
>>>
>>> On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:



 On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:
>
> HI, what are the replacements for elemental2.Global.window and
> similar in this new release?
>

 elemental2.DomGlobal.window (in elemental2-dom dependency)

>>> Thanks!
>>>
>>> Another inconsistency with the previous release of elemental2 which
>>> broke my code is the use of elemental2.core.Function for the
>>> onreadystatechange field in the elemental2.dom.XMLHttpRequest type
>>> which prevents providing the function as a lambda. Other function fields in
>>> the mentioned type (e.g. onprogress or onloadstart) seem to keep the
>>> functional interface semantics. Is this intended or is it an oversight?
>>>
>>
>> I believe it's due to how they're declared in the Closure externs:
>> onreadystatechange and onerror:
>> https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
>> vs all the other callbacks:
>> https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
>>
>>
>> --
>> 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/e1331a22-74f7-4648-b76b-0a2fb43a2dfc%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/CABb_3%3D52vj1gbcf_MPq5UiThib3y0w4nDQHs0Bu8Sb6Ubg5Tyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Julien Dramaix]

> I believe it's due to how they're declared in the Closure externs:
onreadystatechange and onerror:
https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
vs all the other callbacks:
https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862

Yes, the externs use the Function object as type instead of using a
function type like {function():any}.
We'll fix that for the next version.

On Tue, May 9, 2017 at 6:02 AM Thomas Broyer  wrote:

>
>
> On Tuesday, May 9, 2017 at 2:02:40 PM UTC+2, Daniel Harezlak wrote:
>>
>>
>>
>> On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:
>>>
>>>
>>>
>>> On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:

 HI, what are the replacements for elemental2.Global.window and similar
 in this new release?

>>>
>>> elemental2.DomGlobal.window (in elemental2-dom dependency)
>>>
>> Thanks!
>>
>> Another inconsistency with the previous release of elemental2 which broke
>> my code is the use of elemental2.core.Function for the onreadystatechange
>> field in the elemental2.dom.XMLHttpRequest type which prevents providing
>> the function as a lambda. Other function fields in the mentioned type (e.g.
>> onprogress or onloadstart) seem to keep the functional interface
>> semantics. Is this intended or is it an oversight?
>>
>
> I believe it's due to how they're declared in the Closure externs:
> onreadystatechange and onerror:
> https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
> vs all the other callbacks:
> https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
>
>
> --
> 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/e1331a22-74f7-4648-b76b-0a2fb43a2dfc%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/CABb_3%3D6wNB25OWdgjbJrYk8vpozWqaNz7XtBa3K6rgn-3fq2ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Thomas Broyer]

On Tuesday, May 9, 2017 at 2:02:40 PM UTC+2, Daniel Harezlak wrote:
>
>
>
> On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:
>>
>>
>>
>> On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:
>>>
>>> HI, what are the replacements for elemental2.Global.window and similar 
>>> in this new release?
>>>
>>
>> elemental2.DomGlobal.window (in elemental2-dom dependency) 
>>
> Thanks!
>
> Another inconsistency with the previous release of elemental2 which broke 
> my code is the use of elemental2.core.Function for the onreadystatechange 
> field in the elemental2.dom.XMLHttpRequest type which prevents providing 
> the function as a lambda. Other function fields in the mentioned type (e.g. 
> onprogress or onloadstart) seem to keep the functional interface 
> semantics. Is this intended or is it an oversight?
>

I believe it's due to how they're declared in the Closure externs:
onreadystatechange and 
onerror: 
https://github.com/google/closure-compiler/blob/8ac08c03cd695b84f8a79ac3a1338172df3f/externs/browser/w3c_xml.js#L393-L403
vs all the other 
callbacks: 
https://github.com/google/closure-compiler/blob/b85c29855a714cae446f61c8a7b2ccaac747722b/externs/browser/html5.js#L2828-L2862
 

-- 
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/e1331a22-74f7-4648-b76b-0a2fb43a2dfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Daniel Harezlak]

On Tuesday, May 9, 2017 at 1:03:41 PM UTC+2, Thomas Broyer wrote:
>
>
>
> On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:
>>
>> HI, what are the replacements for elemental2.Global.window and similar 
>> in this new release?
>>
>
> elemental2.DomGlobal.window (in elemental2-dom dependency) 
>
Thanks!

Another inconsistency with the previous release of elemental2 which broke 
my code is the use of elemental2.core.Function for the onreadystatechange 
field in the elemental2.dom.XMLHttpRequest type which prevents providing 
the function as a lambda. Other function fields in the mentioned type (e.g. 
onprogress or onloadstart) seem to keep the functional interface semantics. 
Is this intended or is it an oversight?

-- 
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/38ba78bf-4169-420d-9c41-034db9bafd61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Thomas Broyer]

On Tuesday, May 9, 2017 at 1:03:00 PM UTC+2, Daniel Harezlak wrote:
>
> HI, what are the replacements for elemental2.Global.window and similar in 
> this new release?
>

elemental2.DomGlobal.window (in elemental2-dom dependency) 

-- 
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/267a51d4-072e-4492-989a-8860c1daafae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Daniel Harezlak]

HI, what are the replacements for elemental2.Global.window and similar in 
this new release?

-- 
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/51b6fa49-b782-4f7e-9311-e812c8139433%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Thomas Broyer]

Elemental 1 won't be retired until we have a replacement for elemental.json and 
possibly "lightweight collections". Could possibly be as easy as moving them to 
their own project.

-- 
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/f48bfdc8-0fda-4ec0-9c9e-af8d79c0b091%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Jens]

>
> Is this still true for elemetal2? I use JsInterop to define DTOs, they 
> area easy and clean, but collections are still a small problem, if 
> elemental solve this will be awesome, but not sure if this is going to be 
> true. New union types can be influenced to be used easily in the JVM too if 
> this is true (I mean, that elemental2 should take care of collections in 
> the browser and the server).
>

So far elemental2 does not do any magic. It is just JsInterop for browser 
APIs. IMHO it is fine that elemental2 is small and focused. Anything else 
should be developed in separate projects.

-- J.

-- 
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/8b63f6fa-9aea-4f08-80e6-ee3f211b733e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Ignacio Baca Moreno-Torres]

Elemental 1 has this goal 
(http://www.gwtproject.org/articles/elemental.html):
>
> Elemental also includes high-performance collections and a new JSON 
> library. These libraries work equally well in a browser or in a server 
> (JVM) environment.

Is this still true for elemetal2? I use JsInterop to define DTOs, they area 
easy and clean, but collections are still a small problem, if elemental 
solve this will be awesome, but not sure if this is going to be true. New 
union types can be influenced to be used easily in the JVM too if this is 
true (I mean, that elemental2 should take care of collections in the 
browser and the server).

On Thursday, April 13, 2017 at 10:53:30 PM UTC+2, Goktug Gokdogan wrote:
>
> jsinterop.base doesn't try to replace elemental, just provide methods that 
> would normally require special syntax in js. You can find Object.keys in 
> the related elemental class (JsObject)
>
> On Thu, Apr 13, 2017 at 1:42 PM, Ignacio Baca Moreno-Torres <
> ign...@bacamt.com > wrote:
>
>> Hi, a question about JsPropertyMap.
>>
>> It does not have a keys() method, ideally using Object.keys, this is on 
>> purpose?
>> And, the unique method to obtain the keys is the forEach method, but 
>> current implementation iterates over all properties wich might be 
>> dangerous, why this method do not use Object.keys or isOwnProperty? 
>>
>> Thanks!
>>
>> On Friday, April 7, 2017 at 1:57:44 AM UTC+2, Roberto Lublinerman wrote:
>>>
>>> We relaxed restriction checking to allow void return type from getters. 
>>>
>>> Cl is up for review:
>>> https://gwt-review.googlesource.com/#/c/18020/
>>>
>>>
>>>
>>> On Thu, Apr 6, 2017 at 3:17 PM, Jens  wrote:
>>>
 Hmm, I have just built gwt head from source and used the above jars but 
 SDM tells me:

  Errors in jsinterop/base/Js.java
  [ERROR] Line 56: JsProperty 'void Js.debugger()' should have a 
 correct setter or getter signature.


 Can anyone confirm?


 -- J.

 -- 
 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/d460f0fb-6519-4eab-869b-4838e51077ad%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/7aae33f9-32af-4c40-9c15-81860a109fa6%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/2c165fa1-629f-4654-9e92-c4e57b79b1b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

['Goktug Gokdogan' via GWT Contributors]

jsinterop.base doesn't try to replace elemental, just provide methods that
would normally require special syntax in js. You can find Object.keys in
the related elemental class (JsObject)

On Thu, Apr 13, 2017 at 1:42 PM, Ignacio Baca Moreno-Torres <
igna...@bacamt.com> wrote:

> Hi, a question about JsPropertyMap.
>
> It does not have a keys() method, ideally using Object.keys, this is on
> purpose?
> And, the unique method to obtain the keys is the forEach method, but
> current implementation iterates over all properties wich might be
> dangerous, why this method do not use Object.keys or isOwnProperty?
>
> Thanks!
>
> On Friday, April 7, 2017 at 1:57:44 AM UTC+2, Roberto Lublinerman wrote:
>>
>> We relaxed restriction checking to allow void return type from getters.
>>
>> Cl is up for review:
>> https://gwt-review.googlesource.com/#/c/18020/
>>
>>
>>
>> On Thu, Apr 6, 2017 at 3:17 PM, Jens  wrote:
>>
>>> Hmm, I have just built gwt head from source and used the above jars but
>>> SDM tells me:
>>>
>>>  Errors in jsinterop/base/Js.java
>>>  [ERROR] Line 56: JsProperty 'void Js.debugger()' should have a
>>> correct setter or getter signature.
>>>
>>>
>>> Can anyone confirm?
>>>
>>>
>>> -- J.
>>>
>>> --
>>> 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/ms
>>> gid/google-web-toolkit-contributors/d460f0fb-6519-4eab-869b-
>>> 4838e51077ad%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/7aae33f9-32af-
> 4c40-9c15-81860a109fa6%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/CAN%3DyUA3vLMGtC6nogMtNGtQX2gv_juQoe0wgMs4aMK908s48WA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Ignacio Baca Moreno-Torres]

Hi, a question about JsPropertyMap.

It does not have a keys() method, ideally using Object.keys, this is on 
purpose?
And, the unique method to obtain the keys is the forEach method, but 
current implementation iterates over all properties wich might be 
dangerous, why this method do not use Object.keys or isOwnProperty? 

Thanks!

On Friday, April 7, 2017 at 1:57:44 AM UTC+2, Roberto Lublinerman wrote:
>
> We relaxed restriction checking to allow void return type from getters. 
>
> Cl is up for review:
> https://gwt-review.googlesource.com/#/c/18020/
>
>
>
> On Thu, Apr 6, 2017 at 3:17 PM, Jens > 
> wrote:
>
>> Hmm, I have just built gwt head from source and used the above jars but 
>> SDM tells me:
>>
>>  Errors in jsinterop/base/Js.java
>>  [ERROR] Line 56: JsProperty 'void Js.debugger()' should have a 
>> correct setter or getter signature.
>>
>>
>> Can anyone confirm?
>>
>>
>> -- J.
>>
>> -- 
>> 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/d460f0fb-6519-4eab-869b-4838e51077ad%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/7aae33f9-32af-4c40-9c15-81860a109fa6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

['Roberto Lublinerman' via GWT Contributors]

We relaxed restriction checking to allow void return type from getters.

Cl is up for review:
https://gwt-review.googlesource.com/#/c/18020/



On Thu, Apr 6, 2017 at 3:17 PM, Jens  wrote:

> Hmm, I have just built gwt head from source and used the above jars but
> SDM tells me:
>
>  Errors in jsinterop/base/Js.java
>  [ERROR] Line 56: JsProperty 'void Js.debugger()' should have a
> correct setter or getter signature.
>
>
> Can anyone confirm?
>
>
> -- J.
>
> --
> 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/d460f0fb-6519-
> 4eab-869b-4838e51077ad%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/CAC7T7g%3DWL%2BNy5%2BSpQ4H9Xrho-3hMRs8fO68C9bxwUZzkTi20_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Ignacio Baca Moreno-Torres]

Yep, same problem here https://github.com/ibaca/dndfiles-gwt. BUT! if you 
compile GWT do not fails, only throws this error the codeserver.

Anyway, good work! independent libs and specially base lib are really good 
news! thanks.

On Friday, April 7, 2017 at 12:17:57 AM UTC+2, Jens wrote:
>
> Hmm, I have just built gwt head from source and used the above jars but 
> SDM tells me:
>
>  Errors in jsinterop/base/Js.java
>  [ERROR] Line 56: JsProperty 'void Js.debugger()' should have a 
> correct setter or getter signature.
>
>
> Can anyone confirm?
>
>
> -- J.
>

-- 
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/9f680d8d-722a-4675-8eed-0e8d32c4e733%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Julien Dramaix]

good catch! It's a bug in GWT. Roberto is fixing it and will propose a
patch for that.


On Thu, Apr 6, 2017 at 3:17 PM Jens  wrote:

> Hmm, I have just built gwt head from source and used the above jars but
> SDM tells me:
>
>  Errors in jsinterop/base/Js.java
>  [ERROR] Line 56: JsProperty 'void Js.debugger()' should have a
> correct setter or getter signature.
>
>
> Can anyone confirm?
>
>
> -- J.
>
> --
> 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/d460f0fb-6519-4eab-869b-4838e51077ad%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/CABb_3%3D67CuAEYB6gKfX7tSoRGCtGfCL0QTn%3D9ZoLDArec__bbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Jens]

Hmm, I have just built gwt head from source and used the above jars but SDM 
tells me:

 Errors in jsinterop/base/Js.java
 [ERROR] Line 56: JsProperty 'void Js.debugger()' should have a correct 
setter or getter signature.


Can anyone confirm?


-- J.

-- 
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/d460f0fb-6519-4eab-869b-4838e51077ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Ali Jalal]

Thank you guys for this great work.

On Thu, Apr 6, 2017 at 8:44 AM, Predrag Remark 
wrote:

> Great news ! Thanks Julien.
>
> --
> 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/fd8651a8-84fa-
> 4d5d-a7b7-0c31494a21a0%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/CAMNmzoK-HvD73iaAd6G2w7GnotSxvaVFpfF9VeTP7R4xaqoCTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Predrag Remark]

Great news ! Thanks Julien.

-- 
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/fd8651a8-84fa-4d5d-a7b7-0c31494a21a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[Alain Ekambi]

DOPE !

On 5 April 2017 at 23:46, James Nelson  wrote:

> Huzzah!!
>
> I'll be taking this for a spin on my week off; see if I can make custom
> elements completely hack free (at long last)!
>
> Many thanks good sirs.
>
> --
> 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/1ce76a70-bb1d-
> 42a6-adc4-8bc31526644d%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Alain Ekambi

Co-Founder

Ahomé Innovation Technologies

http://www.ahome-it.com/ 

-- 
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/CAGw%3D_tx%3DQzwu93aM8uq99MoqO_bwM7-1P4Cc%2BKdoj1hqT7j9eg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

[James Nelson]

Huzzah!!

I'll be taking this for a spin on my week off; see if I can make custom 
elements completely hack free (at long last)!

Many thanks good sirs.

-- 
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/1ce76a70-bb1d-42a6-adc4-8bc31526644d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.