That is a great conversation which really gives me confidence in the future
of GWT. Thanks for posting.
On Thursday, 2 June 2016 09:51:53 UTC+1, mark kevin ringor wrote:
>
> https://www.youtube.com/watch?v=CElykwDVrBc
> Here is a video about GWT 2.8
>
> On Sunday, May 8, 2016 at 11:26:22 PM
https://www.youtube.com/watch?v=CElykwDVrBc
Here is a video about GWT 2.8
On Sunday, May 8, 2016 at 11:26:22 PM UTC+8, steve Zara wrote:
>
> GWT 2.8 is now well over a year behind what seemed to be the original
> schedule. I'm having to deal with colleagues who say they have lost
> confidence
I am with NGdeM on this one.
Just make a lot more smaller releases. This will give a better impression
of the state of the GWT project.
I am aware you can create your own builds. But it is much better to do a
lot more official releases for the state of the project.
--
You received this
Hi,
And thanks for the suggestion.
Something I will definitely try out.
However, I am not sure how practical this approach actually is once you
depend on third party gwt libraries that do not keep a release pace matchin
your internal nexus GWT 2.8 releases...
Some people seem to be keeping pace
> I said this many times but... I strongly recommend that you create your
> own releases. This is what we have been doing for years...
>
Our company also does this for years, although we don't have a fixed
schedule. We pull GWT from trunk if we think there are enough commits worth
doing so,
I said this many times but... I strongly recommend that you create your own
releases. This is what we have been doing for years...
1. create a release using something like... (tools and trunk are github
clones, build-deploy.sh is the script to deploy to your company repo, you
should create it
One can understand that the amount of resources behind Angular are far
superior to those behind GWT.
In any case, the project's last official hear-beat dates from December 3,
2015, and this was a beta release.
For anybody watching, it is scary to see a UI framework having releases
going out
J2CL is the next-generation Java-to-JavaScript compiler that is currently
being developed by Google. The GWT committee will decide if J2CL will be
used for GWT 3 (or whatever the next major release of GWT will be called).
On Monday, May 9, 2016 at 3:53:16 PM UTC-4, steve Zara wrote:
>
> I
I misunderstood. I assumed that GWT and J2CL were basically the same thing
(or that GWT would be renamed J2CL!
On Monday, 9 May 2016 17:30:45 UTC+1, Michael Zhou wrote:
>
> Google is definitely interested in Java 8 emulation, but most efforts are
> being spent on J2CL, which goes from Java 8
On Monday, May 9, 2016 at 5:20:25 PM UTC+2, steve Zara wrote:
>
> Also a GWT conference is long overdue.
>
What do you mean exactly?
http://gwtcreate.com/ or http://www.gwtcon.org/ ? or that there's no
GWT.create 2016? (yet?)
--
You received this message because you are subscribed to the
Google is definitely interested in Java 8 emulation, but most efforts are
being spent on J2CL, which goes from Java 8 -> Closure-style ES6.
On Sunday, May 8, 2016 at 4:53:17 PM UTC-4, steve Zara wrote:
>
> Thank you - it does highlight where help can be given. I'm really
> surprised at the
It seems to me that the answer to a bad feeling is to contribute time and
resources to help out, and I am going to try and do that. I would say that
the number of developers isn't the only problem. I can't understand why an
earlier release wasn't made with Java 8 syntax support. My impression is
So many people depending on GWT, GWT depending on Java 8 support/ guava and
Google does not work on the Java 8 API emulation. 3 devs working on Java 8
emulation in spare time.
Is it just me having a bad feeling here?
--
You received this message because you are subscribed to the Google
I will see if I can find time to help.
On 8 May 2016 at 21:36, Jens wrote:
> Is there anything that can be done to assist with progress? Is there a
>> problem with lack of interest in GWT from, say, Google? Does GWT 2.8
>> involve too many features when compared to
Thank you - it does highlight where help can be given. I'm really
surprised at the situation with Java 8 emulation - is this something that
Google is just not interested in? It seems odd given their description of
Java technologies that give them cross-platform development: Android JDK,
GWT, and
>
> Is there anything that can be done to assist with progress? Is there a
> problem with lack of interest in GWT from, say, Google? Does GWT 2.8
> involve too many features when compared to 2.7? Is there a lack of
> developers working on GWT? Are more testers needed?
Basically it has
GWT 2.8 is now well over a year behind what seemed to be the original schedule.
I'm having to deal with colleagues who say they have lost confidence in the
GWT project, which is a problem as I have GWT projects to support and further
develop, as part of what I hope will be a globally used and
17 matches
Mail list logo