Hi Brian,
> I highly encourage doing an experiment and coming up with a demo.
> This is how innovation happens!
Agreed. I'll get back to poking at this and hopefully share something,
even embarassingly inadequate "soon". I had played with it awhile ago,
but it's such a huge task, that I got demot
I highly encourage doing an experiment and coming up with a demo. This is
how innovation happens!
But it seems to me that it's way too early to make migration plans. Even if
the new thing is super-cool, we still have to support old code at least
until all of Google moves off of it and that will
As far as I know, there is no schedule for GWT 3.0, or 2.6 for that matter.
I was thinking perhaps we should continue with smaller maintenance
releases, 2.5.2 and so on. It seems to fit our current working style where
we are making gradual changes, not landing major new features. But arguably
J
On Sat, Apr 6, 2013 at 2:05 PM, Stephen Haberman wrote:
> > For me it would be totally fine to have a plugin for FF15 and then
>
> for FF20 and the next for FF25 which would reduce your maintaining
> > work. Same for Chrome.
>
> I hold off on updating FF as well, but I believe a lot of users got
> Hm maybe our app isn't large enough (~150 KLOC and growing) but we
> found DevMode to work pretty well in Firefox. Reloading the app is a
> matter of seconds and if you restart FireFox from time to time you
> can workaround the current memory leak.
Agreed, that is how I use it now.
> For me it
Hm maybe our app isn't large enough (~150 KLOC and growing) but we found
DevMode to work pretty well in Firefox. Reloading the app is a matter of
seconds and if you restart FireFox from time to time you can workaround the
current memory leak. Of course maintaining DevMode plugins is annoying but
Hey,
Again preferring gwt-contrib for the discussion, even though this is
kind of a GWT steering/roap map discussion, but should we decide on an
official stance on JVM dev mode?
AFAICT, we've generally been considering it deprecated, given that
maintaining the plugins sucks, and the rest of the w
Hey,
Thought I would move this to gwt-contrib; during a compiler
improvements discussion in the last steering committee meeting, the
concept of having a dev mode run incrementally in Eclipse came up (e.g.
on save, reuses the existing AST), and Ray made a side comment
describing it as a "moonshot",
