On thing I'd like to see on GWT 3.0 and beyond is the reduction (or
complete avoidance) of the Not invented here syndrome from Google:
- Using a standard build tool which integrates well with Maven
repositories - and don't force the end user to switch build tools just
because
-
Hi,
we have heavy invested our time into GWT to build the product which will
be available for at least next 5 years (ERP in cloud). But I think the
direction they have made is really necessary and only reasonable. And it
should be done year or two before (after SDM and GSS), because some
On Monday, June 22, 2015 at 5:28:36 AM UTC+9:30, Jens wrote:
Yeah I think finalizing JsInterop including all the pieces to make
Elemental 2.0 possible is one of the most important point which should
actually have higher priority than the new compiler itself. That way other
people can
Thanks Thomas.
Good point on getting started experimenting before the compiler is made
available. I've been building a few of libraries using APT for code
generation recently, making use of the wonderful google square libraries
like auto and javapoet. I think it'd be pretty straightforward to
I was probably too specific in asking for early access to the compiler.
Early access to elemental 2.0 and jsinterop 2.0 would be really helpful to
try and figure out how to port JSNI/JSO code over to jsinterop.
Yeah I think finalizing JsInterop including all the pieces to make
Elemental
Also worth noting that, outside of GWT-RPC, I think that many of the
current major GWT features (widgets, uibinder, etc.) could be ported by the
community such that only minor code changes are necessary. I would even
hazard a guess that companies like Vaadin might be interested in supporting
or at
On Sunday, June 21, 2015 at 11:17:50 AM UTC+2, James Horsley wrote:
Also worth noting that, outside of GWT-RPC, I think that many of the
current major GWT features (widgets, uibinder, etc.) could be ported by the
community such that only minor code changes are necessary. I would even
When is GWT 3 available?
On Sunday, June 21, 2015 at 6:38:50 AM UTC+8, Paul Robinson wrote:
I suspect most people here just haven't quite realised the magnitude of
what's planned. The plans are quite reasonable for anybody that can start
from scratch (which doesn't include me). Anybody
I'm a bit surprised that there hasn't been more comment on the direction
the GWT team plan to take GWT in 3.0.
I've been involved in a GWT project over the last 18 months or so where
we're developing a large line-of-business app which we expect to have a
lifetime of potentially a decade or
Sitting here thinking the same. I m having hard time understanding why
people think this is the right direction GWT should take.
Our apps will most likely not move beyond 2.8
On 20 June 2015 at 23:35, Bryan Buchanan bry...@webbtide.com wrote:
I'm a bit surprised that there hasn't been more
GWT 2.8 will be a long supported and maintained branch of GWT. It's just
that you can not use the new compiler if you use some of the current GWT
library stuff.
Upcoming things like Singular, Elemental 2.0, Java 8, JsInterop can all be
used with GWT 2.8. You are not forced to upgrade your
I suspect most people here just haven't quite realised the magnitude of
what's planned. The plans are quite reasonable for anybody that can start
from scratch (which doesn't include me). Anybody invested in GWT will have
a problem. That includes Google, although there are no obvious plans for a
Well the question could also be why not java ?
On 12 June 2015 at 11:21, Phineas Gage phineas...@gmail.com wrote:
I thought I'd share this link to a series of important videos from the
recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors
group:
I thought I'd share this link to a series of important videos from the
recent GWT Meet-up 2015, which was posted on G+ and in the GWT Contributors
group:
https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE
*Summary:*
For anyone who wasn't already aware, there are seismic
There's no technical reason why not Java the language, but as for the
infrastructure available for compiling Java to JavaScript and getting
convenient bidirectional access to the JavaScript universe for use in a web
application, there are more questions now.
Let's say you want to use GWT 2.8
First video, GWT 2.8 and Beyond, starting around 17:20...
I'd also like to hear if I misstated or misunderstood something. I listened
to all of the videos and in the discussion I heard more about re-writing
and renaming than keeping much of anything.
On Friday, June 12, 2015 at 3:20:03 PM
Someone in the video commented that there needs to be a very clear
messaging around how to best protect/future proof yourself. The
Modernizing GWT video was obviously a step in that direction but I'd love
to see something more concrete e.g. if UiBinder won't be supported, what
should we be using?
One thing I may have overstated is that there's a slide discussing what
*may* be ported forward (Modernizing GWT Applications
https://www.youtube.com/watch?v=0flgI0AMJjklist=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLEindex=8,
around 18:45), which *may* include GSS and ClientBundles, i18n (since
that's
To those who've generously uploaded the videos: any possibility of also
uploading the slides? The technical presentations are pretty much useless
w/o the slides.
The Youtube playlist has a link at the top pointing to a Google Drive
containing the slides.
-- J.
--
You received this
Thanks, Jens!
@Brandon: would you please check your slides? The Copy of ... isn't
loading, and I don't see the slides for the Contributing to Eclipse...
presentation.
tia,
jec
On Friday, June 12, 2015 at 7:55:05 AM UTC-7, Jens wrote:
To those who've generously uploaded the videos: any
Is the phasing out of gwt-user something you heard when attending the
meetings? It may be a question of interpretation but I don't read the same
from the slides. Sounds more like a fork of GWT to me. Of course if all
efforts go to the new project, then it is in effect the same thing ;-) may
be
Thanks for the link .
To those who've generously uploaded the videos: any possibility of also
uploading the slides? The technical presentations are pretty much useless
w/o the slides.
TIA,
jec
On Friday, June 12, 2015 at 2:21:49 AM UTC-7, Phineas Gage wrote:
I thought I'd share this link to
22 matches
Mail list logo
