On Monday, October 3, 2016 at 3:12:08 PM UTC+2,
sameepsingha...@drishti-soft.com wrote:
>
> I am not much concerned about name, but would like to know when the GWT
> 3.0 will be released??
>
Nobody knows. (and this is an official answer)
(a little birdie told me that “j2cl is working out
I am not much concerned about name, but would like to know when the GWT 3.0
will be released??
On Saturday, June 13, 2015 at 2:33:08 PM UTC+5:30, Paul Robinson wrote:
>
> The GWT Meetup 2015 videos are very interesting.
>
>
> I can see why the proposals for GWT 3.0 have been made. However, we
Nevermind, found it.
--
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
I searched for the modernizing GWT talk but didn't find it on youtube - is
there any other talk / article that we can refer to, on how to write future
proof gwt code?
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this
On Sunday, June 14, 2015 at 12:31:15 PM UTC+1, stuckagain wrote:
I'm excited that you guys are planning a radical change (really). I hope
it becomes more clear on what we should be using to future proof our apps.
I hope we will get some usable preview of Singular (if that is really
going
Will the new transpiler support the following features and fixes the linked
issues:
- Good SourceMaps including SuperDebug (see Brians speech at gwt.create)
and debugger support within the IDE (like sdbg for eclipse)
- StackTraces including emulation mode (for browsers without - like
On Thu, Jul 9, 2015 at 5:31 PM, Stephen Haberman stephen.haber...@gmail.com
wrote:
https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE
Thanks!
I feel dumb, as the gwt-contrib posts were going under the Forums tab in
my gmail account, and so I missed the original
https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE
Thanks!
I feel dumb, as the gwt-contrib posts were going under the Forums tab in my
gmail account, and so I missed the original email/thread go buy. I only
stumbled across this thread later via the web.
I'll start
Sounds like I'm late to party; I missed the 2015 meetup videos, does
someone have a link? (That will teach me to not login to G+ very
often...well played, Google...)
Not that my opinion matters very much (vs. the GWT team who's doing all the
actual work), but I'll +100 any plans for
On Monday, July 6, 2015 at 2:42:04 PM UTC+2, Stephen Haberman wrote:
Sounds like I'm late to party; I missed the 2015 meetup videos, does
someone have a link? (That will teach me to not login to G+ very
often...well played, Google...)
Features that I hope will still be supported (or have replacements) in GWT
3.0:
* The core parts of the widget library, i.e. the base widgets, composites,
cell widgets (e.g. CellTable, DataGrid), and layout panels. However, I will
not miss the old-style table-based panels and all deprecated
Daniel,
Thanks for the background info.
In my applications (non public web apps for banking purposes) I tend to
use GIN, Guava, UiBinder + Widgets + GWT-RPC.
- GWT-RPC has been a limitation (I filled several issues in the passed) and
I was looking for a REST/JSON replacement but it was not
Thanks Daniel.
It's great that the steering committee are discussing the topic this early
in the process; in particular, in the context of how GWT dev's can help
themselves to be future proof (e.g. your Modernizing GWT talk).
I completely understand how certain GWT generator based libraries
CssResources and such might be a bit more work... we were planning to
move to GssResources ... will those remain ? probably not...
CssResources will continue to work, the generator can be adapted to use APT
api instead of GWT generators.
Widgets ... by switching to GQuery we can avoid widgets
Hi Daniel,
it would be nice, if the team can provide early access to the new compiler.
As the owner of mvp4g I would like to do the necessary changes to get mvp4g
running with the new version.
Also I like the idea that the new version contains the basic classes, to
write old school widgets.
I have the same concerns as the last comment. We are a java shop and use
enterprise java for our back-end. We have been using GWT for the last 9
years to write thin front ends for our applications. Basically GWT RPC and
UiBinder are 99% of the code we deploy. If I need to replace those with
I'm excited that you guys are planning a radical change (really). I hope it
becomes more clear on what we should be using to future proof our apps.
I hope we will get some usable preview of Singular (if that is really going
to be a replacement).
Somehow I am not totally concerned that we will
Hi,
I'm also frustrated about which technologies to use on new GWT projects
(see
https://groups.google.com/forum/?fromgroups#!topic/google-web-toolkit/_QSayBAmeX8).
But when it comes about the name, GWT should stay. The basic idea around
GWT is writing code in Java which is then recompile (or
Also think of people who use GWT for non web based project.
We use GWT for example to create native mobile apps with Titanium. And our
customers love the UI Binder support.
Dropping UI Binder means we wont be able to support new version of GWT.
Such a bad move.
On 14 June 2015 at 16:22,
Hi all,
thanks for sharing your views in this discussion.
Let me add a little background:
Currently we the GWT team have decided to work on a new fast transpiler
from Java to Closure (our internal enhanced version of JavaScript). This
makes sense for a lot of reasons that I won't go into detail
I think that there's enough branding/momentum/etc. behind the GWT name that
to be taken seriously it should stick with the GWT name, even if possibly
adjusted slightly like Jens's suggestions.
I'm fully behind the direction the compiler is taking and I believe that
the vision put forward in the
I kind of agree not calling it GWT 3.0. I would not name it completely
different, maybe something along the lines of GWT X1, GWT RST (abbr. of
reset) or GWT Next. I am pretty sure we could come up with something more
distinct to indicate that this release is a lot different and a reboot of
On Saturday, 13 June 2015 12:18:37 UTC+1, Thomas Broyer wrote:
it's expected that you could future-proof your application in GWT 2.8.
Yes, except that if you're heavily invested in GWT widgets, then
future-proofing means switching to a different rendering library and so
almost a complete
23 matches
Mail list logo
