There is a prototype project enabling Eclipse to debug the JS running in 
the browser with sourcemaps - check it out at http://github.com/sdbg/sdbg. 

On Thursday, November 15, 2012 8:46:26 AM UTC-8, Clint Gilbert wrote:
>
> -----BEGIN PGP SIGNED MESSAGE----- 
> Hash: SHA1 
>
> If I could hook Eclipse up to Firefox or Chrome and step through code, 
> that would make SDM much more workable.  Is that currently possible? 
>
> If so, is it possible to inspect the internal state of an object 
> defined in Java, compiled to JS, and running in a browser VM? 
> Breakpoints and stepping line by line are great, but losing object 
> inspection would be a big step back. 
>
> On 11/14/2012 09:58 PM, Chris Lercher wrote: 
> > On Thursday, November 15, 2012 2:53:37 AM UTC+1, Thomas Broyer 
> > wrote: 
> > 
> > SourceMaps could then be used by your IDE so you could put 
> > breakpoints in your editor window. 
> > 
> > 
> > I can see the potential - it could be big. I do have a few doubts 
> > though: 
> > 
> > 1. Would this also allow me to inspect the internal state of 
> > objects from within my IDE? (Is this even possible?) 2. What about 
> > super-sourced classes, which are - at least in Eclipse - usually 
> > excluded from the build path to avoid error messages (that's 
> > probably the smaller problem, as I imagine, that this could be 
> > taken care of by the IDE plugins) 
> > 
> > 
> > 
> > Embedded browsers, even if using the exact same engine, don't 
> > behave like their "full blown" counterparts (IE, when embedded, 
> > has different rules for switching between IE5.5Quirks/IE7/IE8/etc. 
> > modes for instance) 
> > 
> > 
> > I think, living with these differences in Dev Mode would be ok. 
> > The situation was different back in Hosted Mode's time, because 
> > Super Dev Mode was missing. I believe, that Dev Mode currently has 
> > some important use cases, which Super Dev Mode can't cover (yet?) 
> > For these use cases, the browser differences are often not that 
> > important. 
> > 
> > -- You received this message because you are subscribed to the 
> > Google Groups "Google Web Toolkit" group. To view this discussion 
> > on the web visit 
> > https://groups.google.com/d/msg/google-web-toolkit/-/65KGTSLnUJ0J. 
> > To post to this group, send email to 
> > google-we...@googlegroups.com <javascript:>. To unsubscribe from this 
> > group, send email to 
> > google-web-toolkit+unsubscr...@googlegroups.com <javascript:>. For more 
> options, 
> > visit this group at 
> > http://groups.google.com/group/google-web-toolkit?hl=en. 
>
> -----BEGIN PGP SIGNATURE----- 
> Version: GnuPG v1.4.11 (GNU/Linux) 
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlClHDEACgkQ5IyIbnMUeTsejwCcCepJDymqjpECsv7PXhXnbciF 
> L9gAn34/OEEJArXpXU6zq+10OlSmvs2L 
> =QD9T 
> -----END PGP SIGNATURE----- 
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to