Sunday, November 6, 2016

Re: Can a GWT Dev Mode plugin be rewritten for Chrome using NACL?



On Sunday, November 6, 2016 at 10:55:56 AM UTC+1, Max Fromberger wrote:
From my point of view the only future proof (because never to be deprecated) way of debugging is debugging in JS, i.e. super dev mode. This is going to work until the end of browsers.

I still believe one could implement a DevMode using browsers' remote debugging protocols (calling into the plugin would be replaced with hitting a breakpoint at a specific location, and values would be passed by reading and setting variables), and that would be as future-proof as "debugging right in JS".
But I'm not the one who'll invest in this thing; source maps are the way to go, and in the worst case use -style PRETTY.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment