[ https://issues.jboss.org/browse/JBIDE-15640?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-15640: -------------------------------- Description: JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html‎] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser. *Pros:* # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...] # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows # Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime) *Cons:* # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone) # window.localStorage is not supported (may be a problem for CordovaSim) # Character encoding problems on some installations # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs *On the high level our plan is to:* # Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Coding in progress* # Solve perfomance issues. Debugger freezes rather often - *Coding in progress* # Mock javaFX dependencies - *Done* # Fix LiveReload and Touch Events for JavaFx WebView - *Done* # Move Dev tools front-end source code to the separate plugin / git submodule # Port for debugging should not be hardcoded was: JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html‎] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser. *Pros:* # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...] # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows # Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime) *Cons:* # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone) # window.localStorage is not supported (may be a problem for CordovaSim) # Character encoding problems on some installations # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs *On the high level our plan is to:* # Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira to javaFx team https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Coding in progress* # Solve perfomance issues. Debugger freezes rather often - *Coding in progress* # Mock javaFX dependencies - *Done* # Fix LiveReload and Touch Events for JavaFx WebView - *Done* # Move Dev tools front-end source code to the separate plugin / git submodule # Port for debugging should not be hardcoded -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira