[JBoss JIRA] (JBDS-1843) Smooks Processing, Plus sign next to Input Task is not visible
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1843?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1843.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Smooks Processing, Plus sign next to Input Task is not visible
> --------------------------------------------------------------
>
> Key: JBDS-1843
> URL: https://issues.jboss.org/browse/JBDS-1843
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration-platform, upstream
> Affects Versions: 4.1.0.GA
> Environment: Fedora 14, OpenJDK 1.6, JBDS 4.1.0 GA
> Reporter: Joel Tosi
> Assignee: Brian Fitzpatrick
> Priority: Minor
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> In JBDS, create new Smooks config. In the process / task window, the 'Plus' symbol next to input task is invisible until you mouse over it. This should be visible at all times.
--
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
12 years, 3 months
[JBoss JIRA] (JBDS-92) Save the installation path for RHDS after Previous button was pressed.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-92?page=com.atlassian.jira.plugin.sy... ]
Max Rydahl Andersen resolved JBDS-92.
-------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Save the installation path for RHDS after Previous button was pressed.
> -----------------------------------------------------------------------
>
> Key: JBDS-92
> URL: https://issues.jboss.org/browse/JBDS-92
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 1.0.0.GA
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Optional
> Fix For: LATER
>
>
> Run installation af RHDS
> Go to step 3
> Select the installation path (C:\Red Hat Developer Studio - for example)
> Press Previous button (step 2 will be)
> Press Next button (again step 3)
> The installation path will be default again (C:\Program Files\Red Hat Developer Studio) instead of selected path before pressing Previous button.
--
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
12 years, 3 months
[JBoss JIRA] (JBDS-1510) Movement of artifacts across operating systems
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1510?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1510.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Movement of artifacts across operating systems
> ----------------------------------------------
>
> Key: JBDS-1510
> URL: https://issues.jboss.org/browse/JBDS-1510
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration
> Reporter: Brian Fitzpatrick
> Fix For: LATER
>
>
> Recently there was a discussion with Andy Miller and Burr regarding JBDS40_050 - Movement of artifacts across operating systems.
> This is one we didn't have enough information to try and resolve for the 3.2/4.0 release. But when reminded, Andy provided the following details:
> "Okay, this rings a bell. We had a case, where an SE was pinging me about a performance test a customer was doing to compare EAP to WebSphere. Part of what they were doing was using JBDS to generate some Web Service stuff, and they were running that application for the performance test on Linux. They generated the web service stuff with JBDS on Windows.
> In the logs, all the invocations to the web services were failing, and were logging errors with the Windows file path information for the WSDL, which of course was not going to work on Linux, as it would never find C:\some\path on a Linux server."
> Ray Ploski may have been involved in this effort initially (per Andy), but he's not sure.
--
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
12 years, 3 months
[JBoss JIRA] (JBDS-1847) No syntax auto-completion in Drools IDE for RHS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1847?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1847.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> No syntax auto-completion in Drools IDE for RHS
> -----------------------------------------------
>
> Key: JBDS-1847
> URL: https://issues.jboss.org/browse/JBDS-1847
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: drools
> Affects Versions: 4.1.0.GA
> Environment: RHEL 6.1
> Sun JDK 1.6.0_25 64-bit
> JBDS 4.1
> Reporter: Blaine Mincey
> Fix For: LATER
>
>
> When creating/editing rules in the Drools IDE, it is possible for syntax auto-completion for the model/facts, variables, etc. on the LHS(When syntax). However, there is not auto-completion for the RHS (Then syntax).
> It would be great to have the syntax auto-completion to work on the RHS as it does for the LHS of rules authoring.
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15640?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-15640:
-------------------------------------
[~maxandersen], high level plan of the implementation is added to the description
> BrowserSim: use JavaFX WebView as a browser engine
> --------------------------------------------------
>
> Key: JBIDE-15640
> URL: https://issues.jboss.org/browse/JBIDE-15640
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Ilya Buziuk
> Fix For: 4.2.x
>
>
> 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
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine
by Ilya Buziuk (JIRA)
[ 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
> BrowserSim: use JavaFX WebView as a browser engine
> --------------------------------------------------
>
> Key: JBIDE-15640
> URL: https://issues.jboss.org/browse/JBIDE-15640
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Ilya Buziuk
> Fix For: 4.2.x
>
>
> 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
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine
by Ilya Buziuk (JIRA)
[ 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 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
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
> BrowserSim: use JavaFX WebView as a browser engine
> --------------------------------------------------
>
> Key: JBIDE-15640
> URL: https://issues.jboss.org/browse/JBIDE-15640
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Ilya Buziuk
> Fix For: 4.2.x
>
>
> 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
12 years, 3 months
[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine
by Ilya Buziuk (JIRA)
[ 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 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
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
> BrowserSim: use JavaFX WebView as a browser engine
> --------------------------------------------------
>
> Key: JBIDE-15640
> URL: https://issues.jboss.org/browse/JBIDE-15640
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Ilya Buziuk
> Fix For: 4.2.x
>
>
> 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
12 years, 3 months