Google (who proposed that change of direction) has only internal *customers*;
we outside Google are not customers, we're a community of users of a FLOSS
project.
Sencha and Vaadin, and to some extent Arcbees and RedHat, *do* have customers
though, and they don't seem to disagree with those
I'd like to see completely renovated GWT 3.0, even some other name rather
than GWT will welcome.
Whoever want to use current Widget library better stay at GWT 2.8..
On Sunday, June 21, 2015 at 12:38:13 PM UTC-4, Lukas Glowania wrote:
Hi,
like many people i think Super Dev Mode is quite a
The GWT team might want to survey existing users of their product before
breaking backcompat. A normal company wants to keep customers happy, and
provide updates that don't break existing code bases. However, I suppose a
company with a huge market share and endless resources can act with
Dont get it wrong. Steering community and all is nice but at the end f the
day they will do what s good for Google.
Even though I m still not sure 3.0 is a bad move though.
Time will tell.
On 22 June 2015 at 23:33, bobbitdid...@gmail.com wrote:
The GWT team might want to survey existing
Evert thing has start and the end in their life cycle. No product can
continue forever. I think GWT is too fat to add more modern feature. It's
time to branch out and prune out.
On Sunday, June 21, 2015 at 12:38:13 PM UTC-4, Lukas Glowania wrote:
Hi,
like many people i think Super Dev Mode
This is an open source project.
The source code is freely available.
Just a reminder.
P.
Em segunda-feira, 22 de junho de 2015 18:33:21 UTC-3, bobbit...@gmail.com
escreveu:
The GWT team might want to survey existing users of their product before
breaking backcompat. A normal company wants
Say WHAT!? JSNI is going to be removed!? They realize that's going to
break a bunch of existing code, right?
It only breaks if you upgrade to GWT 3.0 and GWT 3.0 is expected to be a
very breaking upgrade. So a lot of code will simply stay at GWT 2.8.
-- J.
--
You received this
On Sunday, June 21, 2015 at 3:20:51 PM UTC-5, Thomas Broyer wrote:
On Sunday, June 21, 2015 at 9:35:35 PM UTC+2, Lukas Glowania wrote:
Which announcements in particular would make it to a dead end?
The new compiler, JSNI (removed) vs. JsInterop (doesn't work in DevMode).
That would
On Monday, June 22, 2015 at 6:19:27 AM UTC-5, Jens wrote:
Say WHAT!? JSNI is going to be removed!? They realize that's going to
break a bunch of existing code, right?
It only breaks if you upgrade to GWT 3.0 and GWT 3.0 is expected to be a
very breaking upgrade. So a lot of code will
Hi,
like many people i think Super Dev Mode is quite a pain. Of course SDM and
its IDE support is getting better and better, but i guess it will always
feel workaroundish compared to Dev Mode.
So what could be done to make modern Browsers work with Dev Mode? Dev Mode
works with NPAPI, that
On Sunday, June 21, 2015 at 6:38:13 PM UTC+2, Lukas Glowania wrote:
Hi,
like many people i think Super Dev Mode is quite a pain. Of course SDM and
its IDE support is getting better and better, but i guess it will always
feel workaroundish compared to Dev Mode.
So what could be done to
On Sunday, June 21, 2015 at 9:35:35 PM UTC+2, Lukas Glowania wrote:
Which announcements in particular would make it to a dead end?
The new compiler, JSNI (removed) vs. JsInterop (doesn't work in DevMode).
That would require rewriting a whole lot of DevMode for GWT 3.0.
--
You received
Which announcements in particular would make it to a dead end?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
13 matches
Mail list logo
