Thursday, June 5, 2014

Re: Rescue DevMode via JavaFx and JavaPlugin?



On Thursday, June 5, 2014 2:07:44 PM UTC+2, joerg.h...@googlemail.com wrote:
Hi there,

just to bring in an idea that came to my mind:
JavaFx allows DOM integration and a bridge from Java to JavaScript in the Browser. The plugin is maintained by Oracle.
Would it be possible to tweak GWT such that a new DevMode could run as JavaFx app in the browser and a new CompilingClassLoader could redirect JSNI via JavaFx to the browser.
Does that make sense or do you think I am totally crazy or oversee a major problem...

There 2 issues that affect the DevMode plugin, independently of the technology it's written in:

  1. calls from JS to Java and back have to be blocking. Chrome is removing the NPAPI, and the replacement PPAPI only supports non-blocking calls. One could build DevMode as a browser extension making use of the debugger APIs to set a breakpoint and manipulate variable values as a hack to pass values between the JS and Java world, but then there's the other issue:
  2. the plugin needs to be notified when a JS object is garbage-collected so it can tell the Java side of DevMode to free the memory for the corresponding Java object. If we don't have that, DevMode leaks memory like crazy. This is the kind of API that Mozilla removed in Firefox 27, and there's no existing alternative. I'm not sure Chrome's PPAPI would give us the information either.
So no, definitely, there's no way to "rescue" DevMode.

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