Re: [gwt-contrib] Re: Elemental 2?

['Julien Dramaix' via GWT Contributors]

Yes I'm currently working on Elemental2 and other intersting stuffs around
JsInterop. It's a bit to early to communicate something right now. But you
can expect to have more news in one or two months.

Julien

On Thu, Nov 19, 2015 at 7:04 PM Goktug Gokdogan  wrote:

> We have been actively working on a JsInterop generator and Elemental 2.0
> in the last month or so.
> We will make a separate Elemental release and yes that will be J2CL ready.
> However I don't expect it to be released before the next quarter. Also
> having other tools that are investigating the same problem and coming with
> its own solutions usually helps us to learn new stuff.
>
> (adding dramaix@, as he is the one who is actively working on this and
> might provide some feedback as well)
>
> On Thu, Nov 19, 2015 at 2:35 AM, Bademus l.  wrote:
>
>> Hello,
>> Excellent question!
>> Please let me put my 2cents:
>> I'm interested in Chrome Extension API for GWT, it also can be easily
>> generated from Chrome's IDL.
>>
>> On Thursday, November 19, 2015 at 10:39:20 AM UTC+1, Rene Hangstrup
>> Møller wrote:
>>>
>>> Hi
>>>
>>> A year ago I tried to write a tool for generating JsInterop classes from
>>> WebIDL, I abandoned the project because there was no good solution for
>>> method overloading and constructors back then. I know others have attempted
>>> the same.
>>>
>>> It looks like the new JsInterop spec solves those problems, so i was
>>> considering reviving that project, but I don't want to waste the time if
>>> Elemental 2 is going to be released within the next couple of months.
>>>
>>> I guess it should be possible to release it as a separate project that
>>> can be used from GWT 2.8 and the in the far future J2CL.
>>>
>>> Any chance that Elemental 2 will be available shortly or should I build
>>> my own?
>>>
>>> Best regards
>>> Rene
>>>
>>> --
>> 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/9d50d507-f79a-4596-a259-a14213f37875%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/CABXeq2Qe46G2ZcJHvSwMRnsWd4Ycw3fFf5R2OV6x9HcgNHQ5ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Cannot build GWT anymore locally

[Christian Nzhie]

ok, thank for getting us informations.

On Monday, November 2, 2015 at 10:15:42 AM UTC+1, Jens wrote:
>
> GWT tools repository has been migrated from Google Code to Github.
>
> You now need to pull https://github.com/gwtproject/tools
>
> -- 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/4758170c-385c-4637-a70a-c75c109a1b4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Jsinterop and Angular2

[Paul Stockley]

I think you will have a hard time using Angular 2 with GWT as it stands. I 
asked questions about supporting some of the more advanced features used by 
Angular2 such as decorators and they are not supported. In addition, you 
would have to take the output from GWT and run it through babel or a 
typescript compiler. 

On Friday, November 20, 2015 at 4:32:53 AM UTC-5, Chris Hane wrote:
>
> I read the presentation from the recent conference on Jsinterop and 
> Angular1.  I'm about to start a new project and am going to use Angular2. 
>  I wanted to ping the group to see if anyone has done something similar for 
> Angular2  with java/gwt before I start.  Hopefully many of the same 
> concepts apply to A2.  I'm just now starting to play with Jsinterop - so 
> it's all new to me right now.
>
> Thanks,
> Chris
>

-- 
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/fbc7c8d8-ff39-4574-8bb0-79fd3657d6c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental 2?

[Stephen Haberman]

> Meanwhile I will revive my own generator project.

I'll take the opportunity to hop on a soapbox, but the "closed
source/eventually open source" model is a curious trend that I think I've
only seen in the GWT community (are their other examples?)...

Musing, it probably stems from Google setting the example with GWT itself,
where historically a lot happened internally before being mirrored
externally, but it happens a bit for non-Google-GWT projects as well, like
the repackaging of GPE, which was closed during initial development
(although the result is great, and I really appreciate it), Singular, which
is still closed during initial development, now Elemental2. I dunno, I find
it curious.

E.g. with Singular, it's like it's being developed like the next Apple
phone; we have to be secret about it, not say anything, so we can have an
awesome keynote where we surprise the world with how awesome it is.

Granted, I'm sure those keynotes are very fun, but I guess I don't
understand, wtf, why not just open source things from day 1? IMO the best
case scenario, and most likely, is that you're going to attract early
adopters who will a) give you feedback to validate approaches/etc and b)
give you free work by tracking down bugs and committing patches.

Keeping things closed source "until they're ready", IMO, stifles the
potential contributor/committer pool that's needed for the long term health
of an open source project.

I suppose the risk is people writing a 100k LOC production app on a pre-1.0
project, and then they bitch about changes...but hopefully lots of
disclaimers and 0.x release points would help mitigate that...

Anyway, that is my soapbox. Or one of them, I guess. :-P Of course, we're
all getting this work for free, so everyone is free to do what they please,
and I will be very excited and thankful for both Elemental2/Singular when
they are available to us.

So please don't read this as "bah, that is dumb", but just as "gentle nudge
towards open sourcing sooner, if that's okay, thanks!". :-)

- Stephen



On Fri, Nov 20, 2015 at 6:14 AM, Rene Hangstrup Møller 
wrote:

> Thanks for the update.
> Looking forward to seeing what you have been cooking up.
> Meanwhile I will revive my own generator project.
>
> /Rene
>
> Den fredag den 20. november 2015 kl. 11.05.44 UTC+1 skrev Julien Dramaix:
>>
>> It's a bit too early to answer to this question with absolute certainty
>> but I don't think I can guarantee the full backward compatibility with the
>> first version of elemental.
>>
>> --
> 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/98a1cb61-aafa-4c80-9c0d-f1a1d4e6bd1d%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/CANnRKuVpyh6DJouKm7se%3D%2B219%3D4imq9tPCE1-BY8GomSsc11Wg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental 2?

[Julien Dramaix]

It's a bit too early to answer to this question with absolute certainty but 
I don't think I can guarantee the full backward compatibility with the 
first version of elemental.

On Friday, November 20, 2015 at 10:50:26 AM UTC+1, James Horsley wrote:
>
> Thanks for the update Julien. Do you know if Elemental2 will be at all 
> backwards compatible with Elemental1? I was trying to decide on whether to 
> use the Elemental1 interfaces for something I'm working on.
>
> On Fri, Nov 20, 2015 at 9:32 AM 'Julien Dramaix' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com > wrote:
>
>> Yes I'm currently working on Elemental2 and other intersting stuffs 
>> around JsInterop. It's a bit to early to communicate something right now. 
>> But you can expect to have more news in one or two months.
>>
>> Julien
>>
>> On Thu, Nov 19, 2015 at 7:04 PM Goktug Gokdogan > > wrote:
>>
>>> We have been actively working on a JsInterop generator and Elemental 2.0 
>>> in the last month or so.
>>> We will make a separate Elemental release and yes that will be J2CL 
>>> ready.
>>> However I don't expect it to be released before the next quarter. Also 
>>> having other tools that are investigating the same problem and coming with 
>>> its own solutions usually helps us to learn new stuff.
>>>
>>> (adding dramaix@, as he is the one who is actively working on this and 
>>> might provide some feedback as well)
>>>
>>> On Thu, Nov 19, 2015 at 2:35 AM, Bademus l. >> > wrote:
>>>
 Hello,
 Excellent question! 
 Please let me put my 2cents: 
 I'm interested in Chrome Extension API for GWT, it also can be easily 
 generated from Chrome's IDL.

 On Thursday, November 19, 2015 at 10:39:20 AM UTC+1, Rene Hangstrup 
 Møller wrote:
>
> Hi
>
> A year ago I tried to write a tool for generating JsInterop classes 
> from WebIDL, I abandoned the project because there was no good solution 
> for 
> method overloading and constructors back then. I know others have 
> attempted 
> the same.
>
> It looks like the new JsInterop spec solves those problems, so i was 
> considering reviving that project, but I don't want to waste the time if 
> Elemental 2 is going to be released within the next couple of months.
>
> I guess it should be possible to release it as a separate project that 
> can be used from GWT 2.8 and the in the far future J2CL.
>
> Any chance that Elemental 2 will be available shortly or should I 
> build my own?
>
> Best regards
> Rene
>
> -- 
 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/9d50d507-f79a-4596-a259-a14213f37875%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/CABXeq2Qe46G2ZcJHvSwMRnsWd4Ycw3fFf5R2OV6x9HcgNHQ5ZQ%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/9069ea83-8229-46b6-8e1b-cb94f3eebe4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental 2?

[Rene Hangstrup Møller]

Thanks for the update.
Looking forward to seeing what you have been cooking up.
Meanwhile I will revive my own generator project.

/Rene

Den fredag den 20. november 2015 kl. 11.05.44 UTC+1 skrev Julien Dramaix:
>
> It's a bit too early to answer to this question with absolute certainty 
> but I don't think I can guarantee the full backward compatibility with the 
> first version of elemental.
>
>

-- 
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/98a1cb61-aafa-4c80-9c0d-f1a1d4e6bd1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Error compiling with trunk and guava-gwt-18.0.jar

[Jens]

You need to use Guava from their master branch or a SNAPSHOT build. Guava 
will do a new release as soon das GWT 2.8 has been released.

-- 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/f4b173cd-5c9d-4939-9de3-fb4d064ce25d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Error compiling with trunk and guava-gwt-18.0.jar

[John Huss]

I built GWT trunk locally today and I'm trying to compile my app that uses 
Java 8 lambdas along with guava-gwt-18.0,jar.  When I compile I get an 
error thrown because of guava:

 [java]Tracing compile failure path for type 
'com.google.common.collect.GwtPlatform'

 [java]   [ERROR] Errors in 
'jar:file:/Users/john/repos/styleware-net/Salondata/lib/guava-gwt-18.0.jar!/com/google/common/collect/super/com/google/common/collect/GwtPlatform.java'

 [java]  [ERROR] Line 38: *The method createFrom(T[], int) is 
undefined for the type Array*

 [java][ERROR] Aborting compile due to errors in some input files

 [java] Java Result: 1



For reference, this previously DID compile with an older version of GWT 
that I built in late January.


Thanks,

John

-- 
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/77dd538c-88c7-4cb7-906e-93c90c0da024%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Elemental 2?

['Goktug Gokdogan' via GWT Contributors]

No worries :)

On Fri, Nov 20, 2015 at 10:27 AM, Stephen Haberman <
stephen.haber...@gmail.com> wrote:

> Hi Goktug,
>
> That's all true, thanks for providing a counter data point. You're right,
> the JsInterop design docs/etc. were all out in the open from day 1, which I
> thought was pretty exiting.
>
> I definitely can't take any credit for providing useful feedback, but I
> enjoyed seeing the thoughts and process from the community.
>
> So, apologies for the sweeping statement.
>
> - Stephen
>
>
>
> On Fri, Nov 20, 2015 at 11:58 AM, 'Goktug Gokdogan' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> Singular is not a Google project and not being developed internally. It
>> is Daniel's personal project and as fas as I know it is already in the open
>> source.
>>
>> We don't have anything to share for Elemental yet. We are talking with
>> other teams, thinking about alternatives etc. Also when we release, it will
>> not be part of GWT-SDK so there is going be extra work to move the
>> development outside; which doesn't make sense at this stage.
>>
>> The big things we recently developed for GWT, JsInterop and SuperDevMode
>> and they were all open source from day one.
>>
>> On Fri, Nov 20, 2015 at 5:34 AM, Stephen Haberman <
>> stephen.haber...@gmail.com> wrote:
>>
>>> > Meanwhile I will revive my own generator project.
>>>
>>> I'll take the opportunity to hop on a soapbox, but the "closed
>>> source/eventually open source" model is a curious trend that I think I've
>>> only seen in the GWT community (are their other examples?)...
>>>
>>> Musing, it probably stems from Google setting the example with GWT
>>> itself, where historically a lot happened internally before being mirrored
>>> externally, but it happens a bit for non-Google-GWT projects as well, like
>>> the repackaging of GPE, which was closed during initial development
>>> (although the result is great, and I really appreciate it), Singular, which
>>> is still closed during initial development, now Elemental2. I dunno, I
>>> find it curious.
>>>
>>> E.g. with Singular, it's like it's being developed like the next Apple
>>> phone; we have to be secret about it, not say anything, so we can have an
>>> awesome keynote where we surprise the world with how awesome it is.
>>>
>>> Granted, I'm sure those keynotes are very fun, but I guess I don't
>>> understand, wtf, why not just open source things from day 1? IMO the best
>>> case scenario, and most likely, is that you're going to attract early
>>> adopters who will a) give you feedback to validate approaches/etc and b)
>>> give you free work by tracking down bugs and committing patches.
>>>
>>> Keeping things closed source "until they're ready", IMO, stifles the
>>> potential contributor/committer pool that's needed for the long term health
>>> of an open source project.
>>>
>>> I suppose the risk is people writing a 100k LOC production app on a
>>> pre-1.0 project, and then they bitch about changes...but hopefully lots of
>>> disclaimers and 0.x release points would help mitigate that...
>>>
>>> Anyway, that is my soapbox. Or one of them, I guess. :-P Of course,
>>> we're all getting this work for free, so everyone is free to do what they
>>> please, and I will be very excited and thankful for both
>>> Elemental2/Singular when they are available to us.
>>>
>>> So please don't read this as "bah, that is dumb", but just as "gentle
>>> nudge towards open sourcing sooner, if that's okay, thanks!". :-)
>>>
>>> - Stephen
>>>
>>>
>>>
>>> On Fri, Nov 20, 2015 at 6:14 AM, Rene Hangstrup Møller <
>>> rhmol...@gmail.com> wrote:
>>>
 Thanks for the update.
 Looking forward to seeing what you have been cooking up.
 Meanwhile I will revive my own generator project.

 /Rene

 Den fredag den 20. november 2015 kl. 11.05.44 UTC+1 skrev Julien
 Dramaix:
>
> It's a bit too early to answer to this question with absolute
> certainty but I don't think I can guarantee the full backward 
> compatibility
> with the first version of elemental.
>
> --
 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/98a1cb61-aafa-4c80-9c0d-f1a1d4e6bd1d%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 

Re: [gwt-contrib] Re: Elemental 2?

['Goktug Gokdogan' via GWT Contributors]

Singular is not a Google project and not being developed internally. It is
Daniel's personal project and as fas as I know it is already in the open
source.

We don't have anything to share for Elemental yet. We are talking with
other teams, thinking about alternatives etc. Also when we release, it will
not be part of GWT-SDK so there is going be extra work to move the
development outside; which doesn't make sense at this stage.

The big things we recently developed for GWT, JsInterop and SuperDevMode
and they were all open source from day one.

On Fri, Nov 20, 2015 at 5:34 AM, Stephen Haberman <
stephen.haber...@gmail.com> wrote:

> > Meanwhile I will revive my own generator project.
>
> I'll take the opportunity to hop on a soapbox, but the "closed
> source/eventually open source" model is a curious trend that I think I've
> only seen in the GWT community (are their other examples?)...
>
> Musing, it probably stems from Google setting the example with GWT
> itself, where historically a lot happened internally before being mirrored
> externally, but it happens a bit for non-Google-GWT projects as well, like
> the repackaging of GPE, which was closed during initial development
> (although the result is great, and I really appreciate it), Singular, which
> is still closed during initial development, now Elemental2. I dunno, I
> find it curious.
>
> E.g. with Singular, it's like it's being developed like the next Apple
> phone; we have to be secret about it, not say anything, so we can have an
> awesome keynote where we surprise the world with how awesome it is.
>
> Granted, I'm sure those keynotes are very fun, but I guess I don't
> understand, wtf, why not just open source things from day 1? IMO the best
> case scenario, and most likely, is that you're going to attract early
> adopters who will a) give you feedback to validate approaches/etc and b)
> give you free work by tracking down bugs and committing patches.
>
> Keeping things closed source "until they're ready", IMO, stifles the
> potential contributor/committer pool that's needed for the long term health
> of an open source project.
>
> I suppose the risk is people writing a 100k LOC production app on a
> pre-1.0 project, and then they bitch about changes...but hopefully lots of
> disclaimers and 0.x release points would help mitigate that...
>
> Anyway, that is my soapbox. Or one of them, I guess. :-P Of course, we're
> all getting this work for free, so everyone is free to do what they please,
> and I will be very excited and thankful for both Elemental2/Singular when
> they are available to us.
>
> So please don't read this as "bah, that is dumb", but just as "gentle
> nudge towards open sourcing sooner, if that's okay, thanks!". :-)
>
> - Stephen
>
>
>
> On Fri, Nov 20, 2015 at 6:14 AM, Rene Hangstrup Møller  > wrote:
>
>> Thanks for the update.
>> Looking forward to seeing what you have been cooking up.
>> Meanwhile I will revive my own generator project.
>>
>> /Rene
>>
>> Den fredag den 20. november 2015 kl. 11.05.44 UTC+1 skrev Julien Dramaix:
>>>
>>> It's a bit too early to answer to this question with absolute certainty
>>> but I don't think I can guarantee the full backward compatibility with the
>>> first version of elemental.
>>>
>>> --
>> 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/98a1cb61-aafa-4c80-9c0d-f1a1d4e6bd1d%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/CANnRKuVpyh6DJouKm7se%3D%2B219%3D4imq9tPCE1-BY8GomSsc11Wg%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 

Re: [gwt-contrib] Re: Elemental 2?

[Stephen Haberman]

Hi Goktug,

That's all true, thanks for providing a counter data point. You're right,
the JsInterop design docs/etc. were all out in the open from day 1, which I
thought was pretty exiting.

I definitely can't take any credit for providing useful feedback, but I
enjoyed seeing the thoughts and process from the community.

So, apologies for the sweeping statement.

- Stephen



On Fri, Nov 20, 2015 at 11:58 AM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Singular is not a Google project and not being developed internally. It is
> Daniel's personal project and as fas as I know it is already in the open
> source.
>
> We don't have anything to share for Elemental yet. We are talking with
> other teams, thinking about alternatives etc. Also when we release, it will
> not be part of GWT-SDK so there is going be extra work to move the
> development outside; which doesn't make sense at this stage.
>
> The big things we recently developed for GWT, JsInterop and SuperDevMode
> and they were all open source from day one.
>
> On Fri, Nov 20, 2015 at 5:34 AM, Stephen Haberman <
> stephen.haber...@gmail.com> wrote:
>
>> > Meanwhile I will revive my own generator project.
>>
>> I'll take the opportunity to hop on a soapbox, but the "closed
>> source/eventually open source" model is a curious trend that I think I've
>> only seen in the GWT community (are their other examples?)...
>>
>> Musing, it probably stems from Google setting the example with GWT
>> itself, where historically a lot happened internally before being mirrored
>> externally, but it happens a bit for non-Google-GWT projects as well, like
>> the repackaging of GPE, which was closed during initial development
>> (although the result is great, and I really appreciate it), Singular, which
>> is still closed during initial development, now Elemental2. I dunno, I
>> find it curious.
>>
>> E.g. with Singular, it's like it's being developed like the next Apple
>> phone; we have to be secret about it, not say anything, so we can have an
>> awesome keynote where we surprise the world with how awesome it is.
>>
>> Granted, I'm sure those keynotes are very fun, but I guess I don't
>> understand, wtf, why not just open source things from day 1? IMO the best
>> case scenario, and most likely, is that you're going to attract early
>> adopters who will a) give you feedback to validate approaches/etc and b)
>> give you free work by tracking down bugs and committing patches.
>>
>> Keeping things closed source "until they're ready", IMO, stifles the
>> potential contributor/committer pool that's needed for the long term health
>> of an open source project.
>>
>> I suppose the risk is people writing a 100k LOC production app on a
>> pre-1.0 project, and then they bitch about changes...but hopefully lots of
>> disclaimers and 0.x release points would help mitigate that...
>>
>> Anyway, that is my soapbox. Or one of them, I guess. :-P Of course, we're
>> all getting this work for free, so everyone is free to do what they please,
>> and I will be very excited and thankful for both Elemental2/Singular when
>> they are available to us.
>>
>> So please don't read this as "bah, that is dumb", but just as "gentle
>> nudge towards open sourcing sooner, if that's okay, thanks!". :-)
>>
>> - Stephen
>>
>>
>>
>> On Fri, Nov 20, 2015 at 6:14 AM, Rene Hangstrup Møller <
>> rhmol...@gmail.com> wrote:
>>
>>> Thanks for the update.
>>> Looking forward to seeing what you have been cooking up.
>>> Meanwhile I will revive my own generator project.
>>>
>>> /Rene
>>>
>>> Den fredag den 20. november 2015 kl. 11.05.44 UTC+1 skrev Julien Dramaix:

 It's a bit too early to answer to this question with absolute certainty
 but I don't think I can guarantee the full backward compatibility with the
 first version of elemental.

 --
>>> 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/98a1cb61-aafa-4c80-9c0d-f1a1d4e6bd1d%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
>> 

Re: [gwt-contrib] Re: Elemental 2?

['Ray Cromwell' via GWT Contributors]

Another thing to consider is that J2CL was developed as a 'bake off', in
which multiple prototypes and designs were discussed/looked at (compile
from Java with JDT, compile from bytecode, compile using Javac APIs,
writing parser by hand, etc) It would have been a bit premature to release
any of them as they were all known ahead of time to be throwaways.

I have a hacky Elemental2 prototype (which is not the official one that
Julien is working on), if you want to take it and play around.



On Fri, Nov 20, 2015 at 10:30 AM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> No worries :)
>
> On Fri, Nov 20, 2015 at 10:27 AM, Stephen Haberman <
> stephen.haber...@gmail.com> wrote:
>
>> Hi Goktug,
>>
>> That's all true, thanks for providing a counter data point. You're right,
>> the JsInterop design docs/etc. were all out in the open from day 1, which I
>> thought was pretty exiting.
>>
>> I definitely can't take any credit for providing useful feedback, but I
>> enjoyed seeing the thoughts and process from the community.
>>
>> So, apologies for the sweeping statement.
>>
>> - Stephen
>>
>>
>>
>> On Fri, Nov 20, 2015 at 11:58 AM, 'Goktug Gokdogan' via GWT Contributors
>>  wrote:
>>
>>> Singular is not a Google project and not being developed internally. It
>>> is Daniel's personal project and as fas as I know it is already in the open
>>> source.
>>>
>>> We don't have anything to share for Elemental yet. We are talking with
>>> other teams, thinking about alternatives etc. Also when we release, it will
>>> not be part of GWT-SDK so there is going be extra work to move the
>>> development outside; which doesn't make sense at this stage.
>>>
>>> The big things we recently developed for GWT, JsInterop and SuperDevMode
>>> and they were all open source from day one.
>>>
>>> On Fri, Nov 20, 2015 at 5:34 AM, Stephen Haberman <
>>> stephen.haber...@gmail.com> wrote:
>>>
 > Meanwhile I will revive my own generator project.

 I'll take the opportunity to hop on a soapbox, but the "closed
 source/eventually open source" model is a curious trend that I think I've
 only seen in the GWT community (are their other examples?)...

 Musing, it probably stems from Google setting the example with GWT
 itself, where historically a lot happened internally before being mirrored
 externally, but it happens a bit for non-Google-GWT projects as well, like
 the repackaging of GPE, which was closed during initial development
 (although the result is great, and I really appreciate it), Singular, which
 is still closed during initial development, now Elemental2. I dunno, I
 find it curious.

 E.g. with Singular, it's like it's being developed like the next Apple
 phone; we have to be secret about it, not say anything, so we can have an
 awesome keynote where we surprise the world with how awesome it is.

 Granted, I'm sure those keynotes are very fun, but I guess I don't
 understand, wtf, why not just open source things from day 1? IMO the best
 case scenario, and most likely, is that you're going to attract early
 adopters who will a) give you feedback to validate approaches/etc and b)
 give you free work by tracking down bugs and committing patches.

 Keeping things closed source "until they're ready", IMO, stifles the
 potential contributor/committer pool that's needed for the long term health
 of an open source project.

 I suppose the risk is people writing a 100k LOC production app on a
 pre-1.0 project, and then they bitch about changes...but hopefully lots of
 disclaimers and 0.x release points would help mitigate that...

 Anyway, that is my soapbox. Or one of them, I guess. :-P Of course,
 we're all getting this work for free, so everyone is free to do what they
 please, and I will be very excited and thankful for both
 Elemental2/Singular when they are available to us.

 So please don't read this as "bah, that is dumb", but just as "gentle
 nudge towards open sourcing sooner, if that's okay, thanks!". :-)

 - Stephen



 On Fri, Nov 20, 2015 at 6:14 AM, Rene Hangstrup Møller <
 rhmol...@gmail.com> wrote:

> Thanks for the update.
> Looking forward to seeing what you have been cooking up.
> Meanwhile I will revive my own generator project.
>
> /Rene
>
> Den fredag den 20. november 2015 kl. 11.05.44 UTC+1 skrev Julien
> Dramaix:
>>
>> It's a bit too early to answer to this question with absolute
>> certainty but I don't think I can guarantee the full backward 
>> compatibility
>> with the first version of elemental.
>>
>> --
> You received this message because you are subscribed to the Google
> Groups "GWT Contributors" group.
> To unsubscribe from this group and stop 

Re: [gwt-contrib] Re: Error compiling with trunk and guava-gwt-18.0.jar

['Goktug Gokdogan' via GWT Contributors]

I would expect the RCs to work, the patch is already in the trunk for a
while.

On Fri, Nov 20, 2015 at 2:25 PM, Thomas Broyer  wrote:

>
>
> On Friday, November 20, 2015 at 4:45:15 PM UTC+1, Jens wrote:
>>
>> You need to use Guava from their master branch or a SNAPSHOT build. Guava
>> will do a new release as soon das GWT 2.8 has been released.
>>
>
> Oh, I thought 19.0-rc2 (or even 19.0-rc1) was enough.
>
> --
> 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/8dfabed8-011b-4b7f-bb42-41acca24d72b%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%3DyUA0hR6V_mXss6aF9bCEu73A0x_319NTCa7%2BVC_xxHjXiQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Error compiling with trunk and guava-gwt-18.0.jar

[Thomas Broyer]

On Friday, November 20, 2015 at 4:45:15 PM UTC+1, Jens wrote:
>
> You need to use Guava from their master branch or a SNAPSHOT build. Guava 
> will do a new release as soon das GWT 2.8 has been released.
>

Oh, I thought 19.0-rc2 (or even 19.0-rc1) was enough.

-- 
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/8dfabed8-011b-4b7f-bb42-41acca24d72b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Error compiling with trunk and guava-gwt-18.0.jar

[Jens]

They have reverted the Array fix in the release branch of Guava 19 as they 
want it to be GWT 2.6 / 2.7 compatible. Guava 20+ will require GWT 2.8+

See GWT notes: https://github.com/google/guava/wiki/Release19

-- 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/0cce1652-5a81-4648-9759-a1f9a419758e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: New JsInterop document

['Goktug Gokdogan' via GWT Contributors]

dramaix@ is writing such a tool; that's how we are planning to generate
Elemental2.

On Fri, Nov 20, 2015 at 7:56 PM, Slava Pankov  wrote:

> And it would be nice to generate java code with new jsinterop annotations
> based on typescript d.ts files. Dart team is going to implement such tool,
> probably it can be adopted for GWT as well:
> https://github.com/dart-lang/sdk/issues/24874
>
>
> On Thursday, November 19, 2015 at 10:15:35 AM UTC-8, Goktug Gokdogan wrote:
>>
>> Instead of JsArray, you can use Object[] or JsType[] (will be ready by
>> 2.8), instead of Integer, you can Double (in 2.8 release, Double exactly
>> maps to number in javascript).
>>
>> On Thu, Nov 19, 2015 at 6:22 AM, Paul Stockley 
>> wrote:
>>
>>> We wrote our own RPC mechanism that is based entirely on JSON, mainly
>>> for performance reasons on mobile. The client works with JS Overlay
>>> representation of the server DTO objects. We have a tool that automatically
>>> generates the JSO's, Looking at the new interop spec's it would be really
>>> nice for the client and server to work with the same Java DTO objects. I
>>> can see how most of it could work with the new system. However, we handle
>>> Java object representations for ints, doubles, booleans and also
>>> enumerations by generating code in the JSO's such as :
>>>
>>> public class ContractDoJSO extends PersistentDataObjectBaseJSO {
>>>
>>>protected ContractDoJSO() {}
>>>
>>>
>>> public final native ContractType getContractTypeDv() /*-{
>>>
>>>return (this.contractTypeDv == null) ? null : 
>>> @com.ocs.shared.businesslogic.contract.ContractType::valueOf(Ljava/lang/String;)(this.contractTypeDv);
>>>
>>> }-*/;
>>>
>>>
>>> public final native void setContractTypeDv(ContractType v) /*-{ 
>>> this.contractTypeDv = (v == null) ? null : 
>>> v...@com.ocs.shared.businesslogic.contract.ContractType::name()(); }-*/;
>>>
>>>
>>> public final native java.lang.Integer getPreferredEmployerId() /*-{
>>>
>>>   return (this.preferredEmployerId == null) ? null : 
>>> @java.lang.Integer::valueOf(I)(this.preferredEmployerId);
>>>
>>> }-*/;
>>> public final native void setPreferredEmployerId(java.lang.Integer v) /*-{
>>>
>>>  this.preferredEmployerId = (v == null) ? null : 
>>> v...@java.lang.Integer::intValue()();
>>>
>>> }-*/;
>>>
>>>
>>> In addition, if the DTO's contain arrays the client code has to access
>>> them using the JsArray class rather than the java collection API. Do you
>>> think there is some way to have a single representation using the new
>>> Interop mechanism?
>>>
>>>
>>> On Friday, October 23, 2015 at 3:13:55 AM UTC-4, Goktug Gokdogan wrote:
>>>
 As we are getting close to 2.8 release I wrote a new document that is
 concentrating on jsinterop features to be released in 2.8:

 https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#

 Please share your feedback.

 Thanks,

 Goktug

>>> --
>>> 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/1155c295-ecd1-4cdd-86a2-ddf3cffb618c%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/44c98d88-8d67-4f17-b942-4f7202aeac3b%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%3DyUA35xvxa7i00yeGLTBS%2BqEO0zVN3Z3bYfKqhf%2BsyPGs%3DiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.