[JBoss JIRA] (JBIDE-16618) CordovaSim doesn't work on Fedora 20
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16618?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16618:
----------------------------------------
Summary: CordovaSim doesn't work on Fedora 20 (was: CordovaSim doesn't work)
> CordovaSim doesn't work on Fedora 20
> ------------------------------------
>
> Key: JBIDE-16618
> URL: https://issues.jboss.org/browse/JBIDE-16618
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.1.1.Final
> Environment: Fedora 20. Fully updated. Sun JDK 1.7.0_51
> Reporter: Boleslaw Dawidowicz
>
> Basically following burr's video:
> http://vimeo.com/82204444
> - Install JBoss Tools
> - Install Cordova/Hybrid stuff
> - Create simple hybrid app
> - "Run as CordovaSim"
> - CordovaSim doesn't show up. There is blank window visible for a second.
> Some additional hints:
> - Same behaviour on JBDS 7.1 with Cordova and Google Android plugings
> - BrowserSim seems to run fine - just opening it by clicking the button on the toolbar.
> - Cordova app works fine when deployed to actual android device or android emulator.
--
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, 2 months
[JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-14744 at 2/19/14 8:23 AM:
-------------------------------------------------------------------
It turns out that the spec is incomplete when it comes to cartridges. My current understanding of it is as follows:
{code}
- cartridge-spec := list of items
- list of items := ([) item,(item)* (])
- item := name | url | json object
- json object := json object with name- | url-proprety
- name := name | name-pattern
- name-pattern := substring (| substring)*
- substring := (*)string(*)
{code}
was (Author: adietish):
It turns out that the spec is incomplete when it comes to cartridges:
{quote}
a) a comma delimited list of cartridge name search conditions
b) a string containing a JSON array
{quote}
It is currently as follows:
# comma delimited list of SPEC
# json arry of any valid json that one can send to the broker
SPEC :=
* name-pattern
* url
> Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14744
> URL: https://issues.jboss.org/browse/JBIDE-14744
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.2.0.Beta1
>
> Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, alternative-cartridges.png, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.png, openshift-quickstart.png
>
>
> The web ui offers a large set of quickstarts/templates:
> !openshift-quickstart.png!
> in a mail from clayton on the 4th of june:
> {quote}
> For QuickStarts, brokers may choose to
> a) enable community quickstarts
> (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf)
> b) enable their own list of quickstarts
> (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json)
> c) disable the quickstarts link
> (delete /etc/openshift/quickstarts.json)
> To correctly fetch the quickstarts for a server, retrieve the API document
> /broker/rest/api
> and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts. If it is absent, you should assume there are no quickstarts.
> Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific:
> * API versioning is not supported
> * Only JSON is supported
> * The body of the response is slightly different than standard REST API feed results
> * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not)
> The format of the JSON response (in either a) or b) above) is:
> {quote}
> {code}
> {
> data: [
> quickstart: {
> id: "<string id>",
> href: "<absolute URL to a display URL for the quickstart>",
> name: "<name>",
> updated: "<last update date in seconds from the epoch>",
> summary: "<brief HTML body of the item>",
> body: "<full HTML body of the item>",
> cartridges: "<cartridge spec>",
> website: "<URL of metadata about the source of the quickstart or the technology>",
> tags: "<comma delimited list of tags>",
> language: "<display name of the type of quickstart>",
> initial_git_url: "<absolute URL or Git reference to source>",
> provider: "openshift|reviewed|partner|community", # default is community
> },
> ]
> }
> {code}
> {quote}
> You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately. You should also assume that the structure could be changed at any time.
> Cartridge spec:
> The cartridge spec is defined as either:
> a) a comma delimited list of cartridge name search conditions
> b) a string containing a JSON array
> If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field.
> Otherwise,
> 1) split the string by "," into "segments"
> 2) trim whitespace from each segment
> 3) split each segment by "|" into "matches" - these represent logical ORs
> 4) strip leading and trailing "*" characters
> 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select.
> See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> {quote}
--
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, 2 months
[JBoss JIRA] (JBIDE-16618) CordovaSim doesn't work
by Boleslaw Dawidowicz (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16618?page=com.atlassian.jira.plugi... ]
Boleslaw Dawidowicz commented on JBIDE-16618:
---------------------------------------------
No visible trace of any error in the console when run from commandline.
Let me know if you want my help to try something out or debug for additional info.
> CordovaSim doesn't work
> -----------------------
>
> Key: JBIDE-16618
> URL: https://issues.jboss.org/browse/JBIDE-16618
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.1.1.Final
> Environment: Fedora 20. Fully updated. Sun JDK 1.7.0_51
> Reporter: Boleslaw Dawidowicz
>
> Basically following burr's video:
> http://vimeo.com/82204444
> - Install JBoss Tools
> - Install Cordova/Hybrid stuff
> - Create simple hybrid app
> - "Run as CordovaSim"
> - CordovaSim doesn't show up. There is blank window visible for a second.
> Some additional hints:
> - Same behaviour on JBDS 7.1 with Cordova and Google Android plugings
> - BrowserSim seems to run fine - just opening it by clicking the button on the toolbar.
> - Cordova app works fine when deployed to actual android device or android emulator.
--
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, 2 months
[JBoss JIRA] (JBIDE-16618) CordovaSim doesn't work
by Boleslaw Dawidowicz (JIRA)
Boleslaw Dawidowicz created JBIDE-16618:
-------------------------------------------
Summary: CordovaSim doesn't work
Key: JBIDE-16618
URL: https://issues.jboss.org/browse/JBIDE-16618
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.1.1.Final
Environment: Fedora 20. Fully updated. Sun JDK 1.7.0_51
Reporter: Boleslaw Dawidowicz
Basically following burr's video:
http://vimeo.com/82204444
- Install JBoss Tools
- Install Cordova/Hybrid stuff
- Create simple hybrid app
- "Run as CordovaSim"
- CordovaSim doesn't show up. There is blank window visible for a second.
Some additional hints:
- Same behaviour on JBDS 7.1 with Cordova and Google Android plugings
- BrowserSim seems to run fine - just opening it by clicking the button on the toolbar.
- Cordova app works fine when deployed to actual android device or android emulator.
--
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, 2 months
[JBoss JIRA] (JBDS-2921) Dropping a file to Editor pane from Nautilus file browser doesn't work
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-2921?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-2921:
--------------------------------------
[~tkonishi] This works on my machine . Running Fedora 20 on Gnome and Java 1.7. I used a text file as an example and dragged it to the main screen. It opened without an errors. what version Java are you using?
> Dropping a file to Editor pane from Nautilus file browser doesn't work
> ----------------------------------------------------------------------
>
> Key: JBDS-2921
> URL: https://issues.jboss.org/browse/JBDS-2921
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.1.0.GA
> Environment: Red Hat Enterprise Linux 6 (Gnome 2)
> Fedora 20 (Gnome 3)
> Reporter: Takayuki Konishi
>
> Dropping a file to Editor pane from Nautilus file browser doesn't work. It works on JBDS 7.0, Eclipse 4.3.0 and Eclipse 4.3.1.
> I got this exception:
> {code:title=$WORKSPACE/.metadata/.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-19 10:56:37.879
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {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
12 years, 2 months
[JBoss JIRA] (JBIDE-16522) Run on Android Device does not work on OS X - 4.2.x
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16522?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-16522.
---------------------------------
It works fine now - it seems the device is connected at all times and the app can be deployed fine.
Verified in JBDS 8.0.0.Alpha2b B71
> Run on Android Device does not work on OS X - 4.2.x
> ---------------------------------------------------
>
> Key: JBIDE-16522
> URL: https://issues.jboss.org/browse/JBIDE-16522
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: OS X Mavericks
> Latest Android SDK
> JBDS 7.1.0.Beta1
> Nexus 7
> Reporter: Martin Malina
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.0.Alpha2
>
>
> Following the instructions in JBIDE-15904 I am trying to run an app on an Android Device.
> This fails for me - I get: No developer enabled android device is attached to this computer please attach your device and try again. (Punctuation is missing, btw.)
> When I try to run adb devices, I can see the device is not there. Development mode is enabled on the device and it works for Vlado on Linux.
> I found out that using Run on Android Device somehow breaks the connection with the device - before I run that, "adb devices" shows the device just fine. After I run that, the device is no longer displayed.
> We even tried to deploy the app using adb install and it worked (while the device was still connected)
--
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, 2 months
[JBoss JIRA] (JBDS-2921) Dropping a file to Editor pane from Nautilus file browser doesn't work
by Takayuki Konishi (JIRA)
Takayuki Konishi created JBDS-2921:
--------------------------------------
Summary: Dropping a file to Editor pane from Nautilus file browser doesn't work
Key: JBDS-2921
URL: https://issues.jboss.org/browse/JBDS-2921
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 7.1.0.GA
Environment: Red Hat Enterprise Linux 6 (Gnome 2)
Fedora 20 (Gnome 3)
Reporter: Takayuki Konishi
Dropping a file to Editor pane from Nautilus file browser doesn't work. It works on JBDS 7.0, Eclipse 4.3.0 and Eclipse 4.3.1.
I got this exception:
{code:title=$WORKSPACE/.metadata/.log}
!ENTRY org.eclipse.ui 4 0 2014-02-19 10:56:37.879
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
at org.eclipse.swt.SWT.error(SWT.java:4397)
at org.eclipse.swt.SWT.error(SWT.java:4312)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
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:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: org.eclipse.core.runtime.AssertionFailedException: assertion failed:
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
{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
12 years, 2 months
[JBoss JIRA] (JBIDE-16616) New Maven Project dialog, "Finish" in no more enabled after archetypes are retrieved
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16616?page=com.atlassian.jira.plugi... ]
Radoslav Rábara updated JBIDE-16616:
------------------------------------
Attachment: filter.jpg
last page - jobs.jpg
last page - no jobs.jpg
> New Maven Project dialog, "Finish" in no more enabled after archetypes are retrieved
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-16616
> URL: https://issues.jboss.org/browse/JBIDE-16616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Alpha2
> Reporter: Radoslav Rábara
> Fix For: 4.2.0.Beta1
>
> Attachments: filter.jpg, last page - jobs.jpg, last page - no jobs.jpg
>
>
> When you are on the last page of dialog New Maven Project and the job "Retrieving archetypes:" is still running then the button Finish will be enabled only until the job is running.
> This bug is reproducible only once after the dialog New Maven Project is opened. When you want to reproduce it more times in the single instance of JBDS than you need to restart the JBDS.
--
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, 2 months
[JBoss JIRA] (JBIDE-16617) New Hybrid Mobile dialog shows error before anything is entered
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16617?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-16617:
----------------------------------
Description:
When you create a new hybrid mobile project (File -> New -> Hybrid Mobile...), on the first page of the dialog, you're shown an error at the top even though you haven't done anything yet.
This is ugly and violates http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards Guideline 5.3.
!hybrid-dialog-1.png!
Also, consider polishing the next page, too.
!hybrid-dialog-2.png!
If I don't have an engine installed, I get the error Please select a Hybrid Mobile Engine. This is not very nice, but I'm not sure how to improve it - perhaps if there are no engines installed, have a different message? And if you have at least one engine, select the first one by default, so that we avoid unnecessary errors?
was:
When you create a new hybrid mobile project (File -> New -> Hybrid Mobile...), on the first page of the dialog, you're shown an error at the top even though you haven't done anything yet.
This is ugly and violates http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards Guideline 5.3.
Also, consider polishing the next page, too. If I don't have an engine installed, I get the error Please select a Hybrid Mobile Engine. This is not very nice, but I'm not sure how to improve it - perhaps if there are no engines installed, have a different message? And if you have at least one engine, select the first one by default, so that we avoid unnecessary errors?
> New Hybrid Mobile dialog shows error before anything is entered
> ---------------------------------------------------------------
>
> Key: JBIDE-16617
> URL: https://issues.jboss.org/browse/JBIDE-16617
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Alpha2
> Environment: JBDS 8.0.0.Alpha2b B71
> Reporter: Martin Malina
> Fix For: 4.2.0.Beta1
>
> Attachments: hybrid-dialog-1.png, hybrid-dialog-2.png
>
>
> When you create a new hybrid mobile project (File -> New -> Hybrid Mobile...), on the first page of the dialog, you're shown an error at the top even though you haven't done anything yet.
> This is ugly and violates http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards Guideline 5.3.
> !hybrid-dialog-1.png!
> Also, consider polishing the next page, too.
> !hybrid-dialog-2.png!
> If I don't have an engine installed, I get the error Please select a Hybrid Mobile Engine. This is not very nice, but I'm not sure how to improve it - perhaps if there are no engines installed, have a different message? And if you have at least one engine, select the first one by default, so that we avoid unnecessary errors?
--
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, 2 months