Alex, it took a few engineer-days for us to declare in JsInterop what we need
from HTML API (in a really big project including DOM, events, WebGL, input,
network).
There is no blocker of using it today, if u want of course.
"Official" Google public annotations is useful to make a "standard" or
I think you misinterpreted "overhead to make it available outside".
On Tue, Oct 11, 2016 at 6:38 PM, Alex White wrote:
> On Wednesday, October 12, 2016 at 9:59:40 AM UTC+10, Goktug Gokdogan wrote:
>>
>> Elemental 2 is based on a generator and the generator is in active
>> development and constan
On Wednesday, October 12, 2016 at 9:59:40 AM UTC+10, Goktug Gokdogan wrote:
>
> Elemental 2 is based on a generator and the generator is in active
> development and constantly changing. I don't think it is feasible to get
> any contributions at this stage. Since we cannot get contributions and
>
Elemental 2 is based on a generator and the generator is in active
development and constantly changing. I don't think it is feasible to get
any contributions at this stage. Since we cannot get contributions and
there is an overhead to make it available outside, we chose to release it
after more mat
>
>
> Elemental 2 is a completely new project that is being developed internally
> by Google, but their intention is to publish it as open source once the
> maturity of the code matches their internal threshold.
>
>
>
Just curious if this is still going to see the light of day? What's the
point
Looking at #9365, it looks like this is to enable Java collections to be
used in an API that is exposed to JS. The JS code could then use the
collections using a subset of the Java API. As apposed to making the Java
Collections look like native Java arrays for example.
On Friday, June 17, 2016
Because Double, Boolean can now be used to get raw primitive numbers
and booleans as object references, the basic JS collections will work
out of the box.
The Elemental1 collections had one additional benefit in the sense
that there were pure-JRE implementations of interfaces. I don't think
Elemen
Elemental2 is purely generated; doesn't have handrolled collection/json
APIs. It uses closure extern files so you can investigate what will be
available checking here:
https://github.com/google/closure-compiler/tree/master/externs
On Fri, Jun 17, 2016 at 8:18 AM, Thomas Broyer wrote:
>
>
> On F
On Friday, June 17, 2016 at 4:15:00 PM UTC+2, Paul Stockley wrote:
>
> The question I have is more general. What will the scope of Elemental 2
> be? Will it include collections and json support like elemental or will it
> be just an interface to browser API's?
>
With https://github.com/gwtproj
The question I have is more general. What will the scope of Elemental 2 be?
Will it include collections and json support like elemental or will it be
just an interface to browser API's?
On Thursday, June 16, 2016 at 4:28:08 PM UTC-4, Ray Cromwell wrote:
>
>
> With these kinds of purely code gen
With these kinds of purely code generated APIs, I'd say trying to consume
it during development is not very useful. Every small change can lead to a
radical change in hundreds of interfaces output, so your app would likely
to be broken frequently, and with big migration costs each time. It makes
se
Elemental is not secret, it is not ready yet...
Stay tuned, in few days we should push an experimental version of elemental
using JsInterop new specification.
- Julien
On Thu, Jun 16, 2016 at 1:13 PM Leif Åstrand wrote:
> Elemental 2 is a completely new project that is being developed internal
12 matches
Mail list logo
