[JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-14363:
-----------------------------------
Summary: Creation of 'core' component in base
Key: JBIDE-14363
URL: https://issues.jboss.org/browse/JBIDE-14363
Project: Tools (JBoss Tools)
Issue Type: Task
Components: common/jst/core
Affects Versions: 4.1.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Beta1
The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements:
1) Only code designed for re-use can live there
2) Only fully and properly java-doc'd code can live there
3) Only code for use by TWO OR MORE components can live there.
4) Addition of dependencies for this component will be strictly regulated
5) Code must be properly tested and have tests cases demonstrating it.
6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example:
{code}
org.jboss.tools.core.platform
org.jboss.tools.core.platform.ui
org.jboss.tools.core.wtp
org.jboss.tools.core.wtp.ui
{code}
Bundles such as these would require test bundles, as well as features that keep them separate.
{code}
org.jboss.tools.core.platform.feature
org.jboss.tools.core.wtp.feature
{code}
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-14361) BrowserSim: LiveReload's port should be detected by BrowserSim
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14361?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-14361:
--------------------------------
Description: By design LiveReload's port could be configured. So, either BrowserSim need to automatically detect the port or the posibility of configuring it in BrowserSim/CordovaSim need to be implemented. Now, the port is hardcoded - 35729 (was: By design LiveReload's port could be configured. So, either BrowserSim need to automatically detect the port or the posibility of configuring it via BrowserSim/CordovaSim need to be implemented. Now, the port is hardcoded - 35729)
> BrowserSim: LiveReload's port should be detected by BrowserSim
> --------------------------------------------------------------
>
> Key: JBIDE-14361
> URL: https://issues.jboss.org/browse/JBIDE-14361
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
>
> By design LiveReload's port could be configured. So, either BrowserSim need to automatically detect the port or the posibility of configuring it in BrowserSim/CordovaSim need to be implemented. Now, the port is hardcoded - 35729
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-14358) Not able to generate JBOSS WS client code in eclispe Juno
by Roopa Chakra (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14358?page=com.atlassian.jira.plugi... ]
Roopa Chakra commented on JBIDE-14358:
--------------------------------------
Tried the workaround. I am able to generate client code. Thanks for looking into this issue.
> Not able to generate JBOSS WS client code in eclispe Juno
> ---------------------------------------------------------
>
> Key: JBIDE-14358
> URL: https://issues.jboss.org/browse/JBIDE-14358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.0.0.Final
> Environment: EAP 5.1.0
> Reporter: Roopa Chakra
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Beta1
>
>
> Tried installing JBoss tools (JBoss Tools (Juno) 4.0.1.Final from eclipse market place) to eclipse juno. Set the JBOSS WS run time location by following steps.
>
> Window->Preferences->Web Services->JBossWS Preferences->Add. Then provide a name (eg. jboss-eap-5.1.0), Home Folder should be $JBOSS_HOME (which is the jboss-as folder). JBOSS server is EAP 5.1.0.
> When I right click on existing wsdl to generate client code I get below exception.
> Not sure why tools is not able to find JBOSSWS runtime location.
>
> IWAB0014E Unexpected exception occurred.
>
> java.lang.NullPointerException
> at org.jboss.tools.ws.creation.core.utils.JBossWSCreationUtils.getJBossWSRuntimeLocation(JBossWSCreationUtils.java:296)
> at org.jboss.tools.ws.creation.core.commands.InitialClientCommand.execute(InitialClientCommand.java:62)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:908)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)"
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-13552) BrowserSim: Ripple integration
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13552?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-13552:
--------------------------------
Description:
Ripple is an emulator, which provides mobile environment (such as Cordova API) to HTML applications.
Ripple extension for Chrome is written in HTML/JavaScript with usage of Chrome extensions API and some Chrome-only API. When run as an extension, Ripple looks like a mobile iframe in the center of a browser window, and several controls around this iframe, including Geolocation, Orientation and Messaging. These controls allow to change "answers" for queries to emulated API.
*On the high level our plan is to:*
1. get rid of dependencies to Chrome extensions API and Chrome-only API
2. replace the mobile iframe with BrowserSim popup window
3. implement missing pieces
4. replace some Ripple controls with BrowserSim controls
5. integrate our Ripple-BrowserSim simulator in Eclipse
6. other issues
*More details follow:*
*1. get rid of dependencies to Chrome extensions API and Chrome-only API*
This includes:
- allow Ripple code to access {{window}} and {{document}} objects of Cordova applications. _*Resolved* by hosting Ripple and Cordova applications on the same Jetty server_
- allowing cross-origin XHR from BrowserSim. _We *resolved* this by implementation of a Jetty-based proxy_
- Web SQL API is deprecated and it is not available in BrowserSim on Windows. _We *resolved* it by our own implementation of this API in pure JavaScript JBIDE-13813._
- allow to upload files to simulate Cordova Camera API. The problem is that some Chrome API is not available in BrowserSim (an example is {{window.URL.createObjectURL(blob)}}). _We *resolved* it by an upload file servlet in Jetty_
*2. replace the mobile iframe with BrowserSim popup window*
- there is bug in SWT which leads to multiple popups being opened instead of one. _*Resolved.* We already found a workaround for it_
- iframe should be removed from the control page. _*Resolved*. The iframe all JS dependencies to it are removed._
- need a way to change BrowserSim skin while running as popup. The problem is that when the skin is changing, we loose connection with the parent window. _*Resolved*. Now we refresh the parent window after the skin is changed. After refresh the parent window tries to open a new popup, and we connect already created new skin to it.*_
*3. implement missing pieces*
- Compas API does not work in both CordovaSim and original Ripple. *Resolved* actually it works - bad demo sample
- Capture API (audio and video recording using an external app) does not work in both CordovaSim and original Ripple *Resolved* JBIDE-14300
- Media API (audio playback and recording) does not work in CordovaSim now (not sure if it works in original Ripple) *Not a bug* JBIDE-14306
- Bar code scanner?
- Card reader?
*4. replace some Ripple controls with BrowserSim controls*
- the {{backbutton}} event should be fired when user presses the Back button in BrowserSim. _*Resolved*_
- BrowserSim's change skin controls should used instead of Ripple's select device controls (Device API should know which device is selected)
- Ripple's orientation change should be replaced by BrowserSim's one. _*Resolved*_
*5. integrate our Ripple-BrowserSim simulator in Eclipse*
- provide an easy way to run our simulator from Eclipse, probably add something like "Open in CordovaSim" toolbar item/context menu _*In progress.*_
- create build scripts, which probably includes building Ripple from its github repository and packaging it into a bundle
*6. other issues*
- CordovaSim should show an error if jetty port is not available. _*Resolved*_
- A bug: if there are two Cordova projects in the workspace with {{index.html}} and we run CordovaSim for both these projects, than only one of the {{index.html}} files may be showed in both cases. The problem is that by default Jetty allows the {{If-modified-since}} header and the file with an earlier modification date will never be returned. _*Resolved* by not returning this header._
was:
Ripple is an emulator, which provides mobile environment (such as Cordova API) to HTML applications.
Ripple extension for Chrome is written in HTML/JavaScript with usage of Chrome extensions API and some Chrome-only API. When run as an extension, Ripple looks like a mobile iframe in the center of a browser window, and several controls around this iframe, including Geolocation, Orientation and Messaging. These controls allow to change "answers" for queries to emulated API.
*On the high level our plan is to:*
1. get rid of dependencies to Chrome extensions API and Chrome-only API
2. replace the mobile iframe with BrowserSim popup window
3. implement missing pieces
4. replace some Ripple controls with BrowserSim controls
5. integrate our Ripple-BrowserSim simulator in Eclipse
6. other issues
*More details follow:*
*1. get rid of dependencies to Chrome extensions API and Chrome-only API*
This includes:
- allow Ripple code to access {{window}} and {{document}} objects of Cordova applications. _*Resolved* by hosting Ripple and Cordova applications on the same Jetty server_
- allowing cross-origin XHR from BrowserSim. _We *resolved* this by implementation of a Jetty-based proxy_
- Web SQL API is deprecated and it is not available in BrowserSim on Windows. _We *resolved* it by our own implementation of this API in pure JavaScript JBIDE-13813._
- allow to upload files to simulate Cordova Camera API. The problem is that some Chrome API is not available in BrowserSim (an example is {{window.URL.createObjectURL(blob)}}). _We *resolved* it by an upload file servlet in Jetty_
*2. replace the mobile iframe with BrowserSim popup window*
- there is bug in SWT which leads to multiple popups being opened instead of one. _*Resolved.* We already found a workaround for it_
- iframe should be removed from the control page. _*Resolved*. The iframe all JS dependencies to it are removed._
- need a way to change BrowserSim skin while running as popup. The problem is that when the skin is changing, we loose connection with the parent window. _*Resolved*. Now we refresh the parent window after the skin is changed. After refresh the parent window tries to open a new popup, and we connect already created new skin to it.*_
*3. implement missing pieces*
- Compas API does not work in both CordovaSim and original Ripple. *Resolved* actually it works - bad demo sample
- Capture API (audio and video recording using an external app) does not work in both CordovaSim and original Ripple *Resolved* JBIDE-14300
- Media API (audio playback and recording) does not work in CordovaSim now (not sure if it works in original Ripple)
- Bar code scanner?
- Card reader?
*4. replace some Ripple controls with BrowserSim controls*
- the {{backbutton}} event should be fired when user presses the Back button in BrowserSim. _*Resolved*_
- BrowserSim's change skin controls should used instead of Ripple's select device controls (Device API should know which device is selected)
- Ripple's orientation change should be replaced by BrowserSim's one. _*Resolved*_
*5. integrate our Ripple-BrowserSim simulator in Eclipse*
- provide an easy way to run our simulator from Eclipse, probably add something like "Open in CordovaSim" toolbar item/context menu _*In progress.*_
- create build scripts, which probably includes building Ripple from its github repository and packaging it into a bundle
*6. other issues*
- CordovaSim should show an error if jetty port is not available. _*Resolved*_
- A bug: if there are two Cordova projects in the workspace with {{index.html}} and we run CordovaSim for both these projects, than only one of the {{index.html}} files may be showed in both cases. The problem is that by default Jetty allows the {{If-modified-since}} header and the file with an earlier modification date will never be returned. _*Resolved* by not returning this header._
> BrowserSim: Ripple integration
> ------------------------------
>
> Key: JBIDE-13552
> URL: https://issues.jboss.org/browse/JBIDE-13552
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Yahor Radtsevich
> Fix For: 4.1.0.Beta1
>
>
> Ripple is an emulator, which provides mobile environment (such as Cordova API) to HTML applications.
> Ripple extension for Chrome is written in HTML/JavaScript with usage of Chrome extensions API and some Chrome-only API. When run as an extension, Ripple looks like a mobile iframe in the center of a browser window, and several controls around this iframe, including Geolocation, Orientation and Messaging. These controls allow to change "answers" for queries to emulated API.
> *On the high level our plan is to:*
> 1. get rid of dependencies to Chrome extensions API and Chrome-only API
> 2. replace the mobile iframe with BrowserSim popup window
> 3. implement missing pieces
> 4. replace some Ripple controls with BrowserSim controls
> 5. integrate our Ripple-BrowserSim simulator in Eclipse
> 6. other issues
> *More details follow:*
> *1. get rid of dependencies to Chrome extensions API and Chrome-only API*
> This includes:
> - allow Ripple code to access {{window}} and {{document}} objects of Cordova applications. _*Resolved* by hosting Ripple and Cordova applications on the same Jetty server_
> - allowing cross-origin XHR from BrowserSim. _We *resolved* this by implementation of a Jetty-based proxy_
> - Web SQL API is deprecated and it is not available in BrowserSim on Windows. _We *resolved* it by our own implementation of this API in pure JavaScript JBIDE-13813._
> - allow to upload files to simulate Cordova Camera API. The problem is that some Chrome API is not available in BrowserSim (an example is {{window.URL.createObjectURL(blob)}}). _We *resolved* it by an upload file servlet in Jetty_
> *2. replace the mobile iframe with BrowserSim popup window*
> - there is bug in SWT which leads to multiple popups being opened instead of one. _*Resolved.* We already found a workaround for it_
> - iframe should be removed from the control page. _*Resolved*. The iframe all JS dependencies to it are removed._
> - need a way to change BrowserSim skin while running as popup. The problem is that when the skin is changing, we loose connection with the parent window. _*Resolved*. Now we refresh the parent window after the skin is changed. After refresh the parent window tries to open a new popup, and we connect already created new skin to it.*_
> *3. implement missing pieces*
> - Compas API does not work in both CordovaSim and original Ripple. *Resolved* actually it works - bad demo sample
> - Capture API (audio and video recording using an external app) does not work in both CordovaSim and original Ripple *Resolved* JBIDE-14300
> - Media API (audio playback and recording) does not work in CordovaSim now (not sure if it works in original Ripple) *Not a bug* JBIDE-14306
> - Bar code scanner?
> - Card reader?
> *4. replace some Ripple controls with BrowserSim controls*
> - the {{backbutton}} event should be fired when user presses the Back button in BrowserSim. _*Resolved*_
> - BrowserSim's change skin controls should used instead of Ripple's select device controls (Device API should know which device is selected)
> - Ripple's orientation change should be replaced by BrowserSim's one. _*Resolved*_
> *5. integrate our Ripple-BrowserSim simulator in Eclipse*
> - provide an easy way to run our simulator from Eclipse, probably add something like "Open in CordovaSim" toolbar item/context menu _*In progress.*_
> - create build scripts, which probably includes building Ripple from its github repository and packaging it into a bundle
> *6. other issues*
> - CordovaSim should show an error if jetty port is not available. _*Resolved*_
> - A bug: if there are two Cordova projects in the workspace with {{index.html}} and we run CordovaSim for both these projects, than only one of the {{index.html}} files may be showed in both cases. The problem is that by default Jetty allows the {{If-modified-since}} header and the file with an earlier modification date will never be returned. _*Resolved* by not returning this header._
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-13552) BrowserSim: Ripple integration
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13552?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-13552:
--------------------------------
Description:
Ripple is an emulator, which provides mobile environment (such as Cordova API) to HTML applications.
Ripple extension for Chrome is written in HTML/JavaScript with usage of Chrome extensions API and some Chrome-only API. When run as an extension, Ripple looks like a mobile iframe in the center of a browser window, and several controls around this iframe, including Geolocation, Orientation and Messaging. These controls allow to change "answers" for queries to emulated API.
*On the high level our plan is to:*
1. get rid of dependencies to Chrome extensions API and Chrome-only API
2. replace the mobile iframe with BrowserSim popup window
3. implement missing pieces
4. replace some Ripple controls with BrowserSim controls
5. integrate our Ripple-BrowserSim simulator in Eclipse
6. other issues
*More details follow:*
*1. get rid of dependencies to Chrome extensions API and Chrome-only API*
This includes:
- allow Ripple code to access {{window}} and {{document}} objects of Cordova applications. _*Resolved* by hosting Ripple and Cordova applications on the same Jetty server_
- allowing cross-origin XHR from BrowserSim. _We *resolved* this by implementation of a Jetty-based proxy_
- Web SQL API is deprecated and it is not available in BrowserSim on Windows. _We *resolved* it by our own implementation of this API in pure JavaScript JBIDE-13813._
- allow to upload files to simulate Cordova Camera API. The problem is that some Chrome API is not available in BrowserSim (an example is {{window.URL.createObjectURL(blob)}}). _We *resolved* it by an upload file servlet in Jetty_
*2. replace the mobile iframe with BrowserSim popup window*
- there is bug in SWT which leads to multiple popups being opened instead of one. _*Resolved.* We already found a workaround for it_
- iframe should be removed from the control page. _*Resolved*. The iframe all JS dependencies to it are removed._
- need a way to change BrowserSim skin while running as popup. The problem is that when the skin is changing, we loose connection with the parent window. _*Resolved*. Now we refresh the parent window after the skin is changed. After refresh the parent window tries to open a new popup, and we connect already created new skin to it.*_
*3. implement missing pieces*
- Compas API does not work in both CordovaSim and original Ripple. *Resolved* actually it works - bad demo sample
- Capture API (audio and video recording using an external app) does not work in both CordovaSim and original Ripple *Resolved* JBIDE-14300
- Media API (audio playback and recording) does not work in CordovaSim now (not sure if it works in original Ripple)
- Bar code scanner?
- Card reader?
*4. replace some Ripple controls with BrowserSim controls*
- the {{backbutton}} event should be fired when user presses the Back button in BrowserSim. _*Resolved*_
- BrowserSim's change skin controls should used instead of Ripple's select device controls (Device API should know which device is selected)
- Ripple's orientation change should be replaced by BrowserSim's one. _*Resolved*_
*5. integrate our Ripple-BrowserSim simulator in Eclipse*
- provide an easy way to run our simulator from Eclipse, probably add something like "Open in CordovaSim" toolbar item/context menu _*In progress.*_
- create build scripts, which probably includes building Ripple from its github repository and packaging it into a bundle
*6. other issues*
- CordovaSim should show an error if jetty port is not available. _*Resolved*_
- A bug: if there are two Cordova projects in the workspace with {{index.html}} and we run CordovaSim for both these projects, than only one of the {{index.html}} files may be showed in both cases. The problem is that by default Jetty allows the {{If-modified-since}} header and the file with an earlier modification date will never be returned. _*Resolved* by not returning this header._
was:
Ripple is an emulator, which provides mobile environment (such as Cordova API) to HTML applications.
Ripple extension for Chrome is written in HTML/JavaScript with usage of Chrome extensions API and some Chrome-only API. When run as an extension, Ripple looks like a mobile iframe in the center of a browser window, and several controls around this iframe, including Geolocation, Orientation and Messaging. These controls allow to change "answers" for queries to emulated API.
*On the high level our plan is to:*
1. get rid of dependencies to Chrome extensions API and Chrome-only API
2. replace the mobile iframe with BrowserSim popup window
3. implement missing pieces
4. replace some Ripple controls with BrowserSim controls
5. integrate our Ripple-BrowserSim simulator in Eclipse
6. other issues
*More details follow:*
*1. get rid of dependencies to Chrome extensions API and Chrome-only API*
This includes:
- allow Ripple code to access {{window}} and {{document}} objects of Cordova applications. _*Resolved* by hosting Ripple and Cordova applications on the same Jetty server_
- allowing cross-origin XHR from BrowserSim. _We *resolved* this by implementation of a Jetty-based proxy_
- Web SQL API is deprecated and it is not available in BrowserSim on Windows. _We *resolved* it by our own implementation of this API in pure JavaScript JBIDE-13813._
- allow to upload files to simulate Cordova Camera API. The problem is that some Chrome API is not available in BrowserSim (an example is {{window.URL.createObjectURL(blob)}}). _We *resolved* it by an upload file servlet in Jetty_
*2. replace the mobile iframe with BrowserSim popup window*
- there is bug in SWT which leads to multiple popups being opened instead of one. _*Resolved.* We already found a workaround for it_
- iframe should be removed from the control page. _*Resolved*. The iframe all JS dependencies to it are removed._
- need a way to change BrowserSim skin while running as popup. The problem is that when the skin is changing, we loose connection with the parent window. _*Resolved*. Now we refresh the parent window after the skin is changed. After refresh the parent window tries to open a new popup, and we connect already created new skin to it.*_
*3. implement missing pieces*
- Compas API does not work in both CordovaSim and original Ripple. *Resolved* actually it works - bad demo sample
- Capture API (audio and video recording using an external app) does not work in both CordovaSim and original Ripple
- Media API (audio playback and recording) does not work in CordovaSim now (not sure if it works in original Ripple)
- Bar code scanner?
- Card reader?
*4. replace some Ripple controls with BrowserSim controls*
- the {{backbutton}} event should be fired when user presses the Back button in BrowserSim. _*Resolved*_
- BrowserSim's change skin controls should used instead of Ripple's select device controls (Device API should know which device is selected)
- Ripple's orientation change should be replaced by BrowserSim's one. _*Resolved*_
*5. integrate our Ripple-BrowserSim simulator in Eclipse*
- provide an easy way to run our simulator from Eclipse, probably add something like "Open in CordovaSim" toolbar item/context menu _*In progress.*_
- create build scripts, which probably includes building Ripple from its github repository and packaging it into a bundle
*6. other issues*
- CordovaSim should show an error if jetty port is not available. _*Resolved*_
- A bug: if there are two Cordova projects in the workspace with {{index.html}} and we run CordovaSim for both these projects, than only one of the {{index.html}} files may be showed in both cases. The problem is that by default Jetty allows the {{If-modified-since}} header and the file with an earlier modification date will never be returned. _*Resolved* by not returning this header._
> BrowserSim: Ripple integration
> ------------------------------
>
> Key: JBIDE-13552
> URL: https://issues.jboss.org/browse/JBIDE-13552
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Yahor Radtsevich
> Fix For: 4.1.0.Beta1
>
>
> Ripple is an emulator, which provides mobile environment (such as Cordova API) to HTML applications.
> Ripple extension for Chrome is written in HTML/JavaScript with usage of Chrome extensions API and some Chrome-only API. When run as an extension, Ripple looks like a mobile iframe in the center of a browser window, and several controls around this iframe, including Geolocation, Orientation and Messaging. These controls allow to change "answers" for queries to emulated API.
> *On the high level our plan is to:*
> 1. get rid of dependencies to Chrome extensions API and Chrome-only API
> 2. replace the mobile iframe with BrowserSim popup window
> 3. implement missing pieces
> 4. replace some Ripple controls with BrowserSim controls
> 5. integrate our Ripple-BrowserSim simulator in Eclipse
> 6. other issues
> *More details follow:*
> *1. get rid of dependencies to Chrome extensions API and Chrome-only API*
> This includes:
> - allow Ripple code to access {{window}} and {{document}} objects of Cordova applications. _*Resolved* by hosting Ripple and Cordova applications on the same Jetty server_
> - allowing cross-origin XHR from BrowserSim. _We *resolved* this by implementation of a Jetty-based proxy_
> - Web SQL API is deprecated and it is not available in BrowserSim on Windows. _We *resolved* it by our own implementation of this API in pure JavaScript JBIDE-13813._
> - allow to upload files to simulate Cordova Camera API. The problem is that some Chrome API is not available in BrowserSim (an example is {{window.URL.createObjectURL(blob)}}). _We *resolved* it by an upload file servlet in Jetty_
> *2. replace the mobile iframe with BrowserSim popup window*
> - there is bug in SWT which leads to multiple popups being opened instead of one. _*Resolved.* We already found a workaround for it_
> - iframe should be removed from the control page. _*Resolved*. The iframe all JS dependencies to it are removed._
> - need a way to change BrowserSim skin while running as popup. The problem is that when the skin is changing, we loose connection with the parent window. _*Resolved*. Now we refresh the parent window after the skin is changed. After refresh the parent window tries to open a new popup, and we connect already created new skin to it.*_
> *3. implement missing pieces*
> - Compas API does not work in both CordovaSim and original Ripple. *Resolved* actually it works - bad demo sample
> - Capture API (audio and video recording using an external app) does not work in both CordovaSim and original Ripple *Resolved* JBIDE-14300
> - Media API (audio playback and recording) does not work in CordovaSim now (not sure if it works in original Ripple)
> - Bar code scanner?
> - Card reader?
> *4. replace some Ripple controls with BrowserSim controls*
> - the {{backbutton}} event should be fired when user presses the Back button in BrowserSim. _*Resolved*_
> - BrowserSim's change skin controls should used instead of Ripple's select device controls (Device API should know which device is selected)
> - Ripple's orientation change should be replaced by BrowserSim's one. _*Resolved*_
> *5. integrate our Ripple-BrowserSim simulator in Eclipse*
> - provide an easy way to run our simulator from Eclipse, probably add something like "Open in CordovaSim" toolbar item/context menu _*In progress.*_
> - create build scripts, which probably includes building Ripple from its github repository and packaging it into a bundle
> *6. other issues*
> - CordovaSim should show an error if jetty port is not available. _*Resolved*_
> - A bug: if there are two Cordova projects in the workspace with {{index.html}} and we run CordovaSim for both these projects, than only one of the {{index.html}} files may be showed in both cases. The problem is that by default Jetty allows the {{If-modified-since}} header and the file with an earlier modification date will never be returned. _*Resolved* by not returning this header._
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-14361) BrowserSim: LiveReload's port should be detected by BrowserSim
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14361?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-14361:
--------------------------------
Description: By design LiveReload's port could be configured. So, either BrowserSim need to automatically detect the port or the posibility of configuring it via BrowserSim/CordovaSim need to be implemented. Now, the port is hardcoded - 35729
> BrowserSim: LiveReload's port should be detected by BrowserSim
> --------------------------------------------------------------
>
> Key: JBIDE-14361
> URL: https://issues.jboss.org/browse/JBIDE-14361
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
>
> By design LiveReload's port could be configured. So, either BrowserSim need to automatically detect the port or the posibility of configuring it via BrowserSim/CordovaSim need to be implemented. Now, the port is hardcoded - 35729
--
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
11 years, 1 month