[
https://issues.jboss.org/browse/JBIDE-16883?page=com.atlassian.jira.plugi...
]
Vlado Pakan edited comment on JBIDE-16883 at 4/29/14 8:42 AM:
--------------------------------------------------------------
Case 1: I agree with you it works the same way as Installed JREs properties
Case 2: I will verify with 4.2.0.Beta2 build when available. Regarding Progress Bar if it
has just 2 values it's actually not Progress Bar we should use another kind of
animation because it's confusing for user to see nothing happening in progress bar
even there is ongoing download.
Case 3: It's OK to remove downloaded engine from UI but not ok to remove it from hard
drive. JRE dialog is not removing JRE from hard drive. And in case user remove JRE and
then close dialog via Cancel button JRE is not removed. When JRE dialog is reopen user can
see there were no JRE removed otherwise buttons OK and Cancel have no sense.
Case 4: I will verify with 4.2.0.Beta2 build when available.
Case 5: created issue JBIDE-17214
was (Author: vpakan):
Case 1: I agree with you it works the same way as Installed JREs properties
Case 2: I will verify with 4.2.0.Beta2 build when available. Regarding Progress Bar if it
has just 2 values it's actually not Progress Bar we should use another kind of
animation because it's confusing for user to see nothing happening in progress bar
even there is ongoing download.
Case 3: It's OK to remove downloaded engine from UI but not ok to remove it from hard
drive. JRE dialog is not removing JRE from hard drive. And in case user remove JRE and
then close dialog via Cancel button JRE is not removed. When JRE dialog is reopen user can
see there were no JRE removed
Case 4: I will verify with 4.2.0.Beta2 build when available.
Case 5: created issue JBIDE-17214
Broken UI logic in Hybrid Mobile/ Engine properties
---------------------------------------------------
Key: JBIDE-16883
URL:
https://issues.jboss.org/browse/JBIDE-16883
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.2.0.Beta1
Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78, Linux
Reporter: Vlado Pakan
Assignee: Gorkem Ercan
Priority: Critical
Fix For: 4.2.0.Beta2
Attachments: enginesearch.png
Case 0:
1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined
2. Resize Preferences window
ERROR: Engine table is not resized
Case 1:
1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined
2. Click on another Preferences tree item
ERROR: It's not possible to select another preferences. Error dialog is displayed
saying: "The currently displayed page contains invalid values"
Case 2:
1. Use this preferences dialog to download Hybrid Mobile engine
ERROR: Displayed Progress Bar has only two values 0% and 100% there is no progress change
during downloading
ERROR: OK button within Download Hybrid Mobile Engine dialog should be enabled only when
version and at least one platform is selected
ERROR: When first engine is downloaded it should be marked as default automatically
ERROR: While downloading OK button, Version Combo and Platform Table are is still
enabled
Case 3:
1. Remove all downloaded engines by clicking on button Remove
ERROR: Engines are removed immediately after Remove button is clicked. They should be
really removed when button OK is pushed
ERROR: Once there is no engine in dialog error from Case 1 happens
Case 4:
1. Remove all downloaded engines
2. Reopen preferences dialog
3. Download engine
4. Check downloaded engine as default
ERROR: Button OK is still disabled.
5. Uncheck default button
6. Check default button
7. OK button is enabled and it's possible to click on it
Case 5:
1. Download at least 1 engine
2. Search for engine on local file system more times using the same directory
ERROR: Platform in table is "Android Android ..."
3. Click on i image in third column
ERROR: It shows more than one line with engine location and shows incorrect location for
files found on local file system not downloaded from repo
!enginesearch.png!
--
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