Small correction: Google is not planning to delete dev-mode from GWT
proper. That's community's decision based on how the would like to move
forward with GWT 3.0.
Wrt. J2CL; pls don't expect a beta release of J2CL this quarter. Also J2CL
doesn't even have devmode since transpilation is instant
>
> have been pushing for more than a year now to delete it from GWT proper
> too.
>
Are there any updates on that ?
Is there some patch for review ?
Thanks
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this
FWIW my answer to "I want a really awesome debugging experience" is that
you shouldn't be doing any debugging in the browser in the first place,
e.g. whether it's old-school DevMode or SuperDevMode or Typescript etc.
This is what Tessell allowed (apologies for the self-promotion, although I
am
IMHO @Ivan's second suggested approach would be a perfect solution:
"implementing
Java watch expressions and conditional breakpoints in Eclipse SDBG".
Hopefully this will be possible to realize and hopefully gwt
contributors/maintainers will be willing to cooperate with @Ivan about this
idea.
On Thursday, January 12, 2017 at 10:43:57 PM UTC+1, sannysan...@gmail.com
wrote:
>
> Hello, GWT people.
>
>
>
> GWT got its popularity because it allowed DevMode in the browser (run java
> in VM in browser, manipulate DOM, use your IDE!). In fact, the GWT project
> appeared as clever hack on
Hi Sanny,
Thanks for your message !
I agree with Jens, once you accept and understand the new SDM+sourcemaps
workflow, the thing is really powerful, yet of course different than the
experience with DevMode.
It's even easier to find browsers specific bugs since the code is executed
in the
Sorry but this will very likely never happen unless you do it yourself
together with other interested people and manage it on Github as a
community project. Google (GWT's main committer) invests in J2CL + Closure
Compiler in the future so they won't do it and current contributors will
likely
