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 logical
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 f
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 JsF
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+uns
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 visi
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-w
> 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 t
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 w
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
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" gr
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
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: a
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 b
> 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/b
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 simi
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
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 Go
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-toolk
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 unsubscri
>
> 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
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
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 abou
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 Objec
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 jsin
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,
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 'v
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
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 i
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 discus
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 G
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
31 matches
Mail list logo
