Sunday, June 21, 2015

Re: How to rescue Classic Dev Mode?



On Sunday, June 21, 2015 at 6:38:13 PM UTC+2, Lukas Glowania wrote:
Hi,

like many people i think Super Dev Mode is quite a pain. Of course SDM and its IDE support is getting better and better, but i guess it will always feel workaroundish compared to Dev Mode.

So what could be done to make modern Browsers work with Dev Mode? Dev Mode works with NPAPI, that was removed from Chrome and Firefox. Would it be possible to change the NPAPI dependence to an alternative e.g. communication through WebSockets like in SDM? What are the options? Or are there compelling reasons to not even try that?


You'd need to find something that's blocking (you wouldn't want new events to happen while you're "processing" a method call). Options are/were: NPAPI, XMLHttpRequest, and debugger APIs. The first two are deprecated or already gone.
I believe you can do something using the debugger APIs (unfortunately non standard and browser specific), with a breakpoint to "enter" Java code and reading/writing variables with the debugger APIs to pass values between the JS and Java world. Ray Cromwell believes it's not possible because of the need to be re-entrant.
With the changes announced for GWT 3.0, that's probably a dead end though.

--
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+unsubscribe@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/d/optout.

No comments:

Post a Comment