0001670: Skipped updates to be set/sorted as Green, yet still displaying available version.

(0001082)
bytehead (updater)
2012-08-10 01:40

very good one.

(0001084)
Kyle_Katarn (administrator)
2012-08-10 23:32

Not so easy, as it will make "column sorting" complex but good idea

(0001088)
bytehead (updater)
2012-08-11 01:27
edited on: 2012-08-11 01:27

This should be combined with ideas from 0001623 and 0001577 as they can complement each other.

(0001089)
poutnikg (reporter)
2012-08-11 02:10

There could be "OK - update available 1.2.3",
than still being able to be sorted by Avilable string..

Or, why not to sort according to green/yellow/ orange status ?

(0001090)
bytehead (updater)
2012-08-11 13:25
edited on: 2012-08-11 14:34

I would reserve new color options for diff. things, like unreliable update status (no. of users <= min) or beta status (unreliable by definition due to community involvement and vague beta term nature), or smth. like that.

>> There could be "OK - update available 1.2.3",

This one seems like a better idea to me.

(0001092)
Kyle_Katarn (administrator)
2012-08-11 13:51

Sounds good here too !

(0001095)
poutnikg (reporter)
2012-08-12 13:21

I like that.

I did not want to introduce any new color value here,
but in place bytehead mentined - for unreliable info of various kind,
e.g. for low users of unclear beta.

Sorting by color status would not add any color value either.

But sorting Update available/ OK / OK - Update available
serves the same purpose as well.

Issue History
Date Modified	Username	Field	Change
2012-08-10 01:15	poutnikg	New Issue
2012-08-10 01:40	bytehead	Note Added: 0001082
2012-08-10 23:32	Kyle_Katarn	Note Added: 0001084
2012-08-10 23:32	Kyle_Katarn	Assigned To	=> Kyle_Katarn
2012-08-10 23:32	Kyle_Katarn	Status	new => acknowledged
2012-08-11 01:25	bytehead	Tag Attached: UX
2012-08-11 01:25	bytehead	Relationship added	related to 0001623
2012-08-11 01:25	bytehead	Relationship added	related to 0001577
2012-08-11 01:27	bytehead	Note Added: 0001088
2012-08-11 01:27	bytehead	Note Edited: 0001088	View Revisions
2012-08-11 02:10	poutnikg	Note Added: 0001089
2012-08-11 13:25	bytehead	Note Added: 0001090
2012-08-11 13:51	Kyle_Katarn	Note Added: 0001092
2012-08-11 14:34	bytehead	Note Edited: 0001090	View Revisions
2012-08-12 13:21	poutnikg	Note Added: 0001095

Notes
(0001082) bytehead (updater) 2012-08-10 01:40	very good one.

(0001084) Kyle_Katarn (administrator) 2012-08-10 23:32	Not so easy, as it will make "column sorting" complex but good idea

(0001088) bytehead (updater) 2012-08-11 01:27 edited on: 2012-08-11 01:27	This should be combined with ideas from 0001623 and 0001577 as they can complement each other.

(0001089) poutnikg (reporter) 2012-08-11 02:10	There could be "OK - update available 1.2.3", than still being able to be sorted by Avilable string.. Or, why not to sort according to green/yellow/ orange status ?

(0001090) bytehead (updater) 2012-08-11 13:25 edited on: 2012-08-11 14:34	I would reserve new color options for diff. things, like unreliable update status (no. of users <= min) or beta status (unreliable by definition due to community involvement and vague beta term nature), or smth. like that. >> There could be "OK - update available 1.2.3", This one seems like a better idea to me.

(0001092) Kyle_Katarn (administrator) 2012-08-11 13:51	Sounds good here too !

(0001095) poutnikg (reporter) 2012-08-12 13:21	I like that. I did not want to introduce any new color value here, but in place bytehead mentined - for unreliable info of various kind, e.g. for low users of unclear beta. Sorting by color status would not add any color value either. But sorting Update available/ OK / OK - Update available serves the same purpose as well.