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

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.


Am Sonntag, 6. November 2016 00:52:01 UTC+1 schrieb Kirill Prazdnikov:

I think people complaining because debug in chrome so slow today. 

There are some bugs. I use old build of chrome to debug apps.

On Saturday, November 5, 2016 at 1:48:29 PM UTC+3, Thomas Broyer wrote:

On Saturday, November 5, 2016 at 11:23:33 AM UTC+1, Ariel Viera wrote:

Is theoretically possible to port GWT Dev Mode plugin for Chrome using PNACL or NACL

No.

Because communication between JS and NaCl is asynchronous, and DevMode MUST be blocking (and reentrant).

(we've already had that conversation many times over the last few years; I bet you could find more details in the forum archives)

BTW, I wouldn't bet on NaCl these days: https://bugs.chromium.org/p/chromium/issues/detail?id=239656#c160 ("Pepper and NaCl are destaffed.")

--
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.