Bug 1030222 - Fix the colours change behaviour for natives on pack screen
Summary: Fix the colours change behaviour for natives on pack screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: CR2
: EAP 6.2.0
Assignee: Miles Tjandrawidjaja
QA Contact: Petr Kremensky
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-14 08:17 UTC by Petr Kremensky
Modified: 2014-09-03 04:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:55:36 UTC
Type: Bug


Attachments (Terms of Use)

Description Petr Kremensky 2013-11-14 08:17:18 UTC
Description of problem:
 At first, this is really minor issue.

 We should fix the colour change mechanism for Natives box on packs selection screen. Default colour is blue, once user make some change on pack selection, the colour switch to red. Colour is switched back to blue only if user make some changes on core components, or go to next->previsous / previsou->next scree. We can use the state of Natives checkbox node. If the Natives checkbox node is selected -> colour should be blue, if it is not selected / partially selected, the colour should be red.

Version-Release number of selected component (if applicable):
 EAP 6.2.0.ER7

How reproducible:
 Always

Steps to Reproduce:
 1. Start the gui installer. Go to pack selection screen using default values.
 2. Read the issue description.

Comment 1 Miles Tjandrawidjaja 2013-11-15 16:54:06 UTC
Updated so that natives checkbox is blue if fully selected.
Otherwise (no selected/partially selected) the colour will be red.

http://git.app.eng.bos.redhat.com/izpack.git/commit/?h=izpack-wip&id=3a9046fd29596c38d40f462efbadcc03f45fb944

Comment 2 Petr Kremensky 2013-11-19 08:50:44 UTC
Verified on EAP 6.2.0.CR2 installer, natives checkbox is behaving as described in comment 1.


Note You need to log in before you can comment on or make changes to this bug.