Hi Daniel,

These are good news, the bad news is the fact that we won't be able to use 
eclipse with all its developement shortcutted features (source navigation, 
breakpoint and bookmark management, tasks, etc...). The solution is an 
eclipse plugin that will read the sourcemap and display/communicate with 
the browser to dispatch debug events. The good news is that there's already 
on project doing this, but the bémol is that the sourcemap spec is leaking 
some vital information: see this bug for example 
https://groups.google.com/forum/#!topic/sdbg/Ku3WWrdtKis

Do you think GWT can allocate some of the energy they were spending in the 
browser plugin to fix this kind of issues?

I just want to underline that GWT's success was: *develop in Java and run 
in the browser*. Now there's a big piece of the *"develop in java" that was 
cut off: debugging and source navigation while running.* So it's the heart 
of the spirit of GWT that has been touched with the superDevMode

Unless the strategy is to migrate projects towards dart and drop GWT out, I 
think this feature is vital for the success of GWT to keep going

On Thursday, November 20, 2014 11:59:06 AM UTC+1, Daniel Kurka wrote:
>
> Today we are excited to announce the GWT 2.7.0 release.  Thanks to 
> everyone who contributed to this release, especially our non-Google open 
> source contributors.
>
> One major feature of this release is a new super fast compilation path in 
> Super Dev mode that replaces the old dev mode.
> For a run-down of all changes since GWT 2.6.1, read the release notes 
> <http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0>.
>
> The release is available for download here 
> <http://www.gwtproject.org/download.html> or on maven central.
>
> If you find any issues with this release, please file a bug in our issue 
> tracker.
>
> Daniel,
> on behalf of the GWT team at Google
>
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to