ginger
ginger copied to clipboard
System Services listing over crowded
System service listing looks over crowded with many columns.
Few Observations:
- Column Loaded looks redundant if some how Status represent the same to the user ? IF required this can be moved into details data.
- Status background color coding not uniform. For example: back ground color of "Active (Exited)" looks smaller when compared to " Active (running)"
- Auto start could have been part of Actions since it is an action. Why a separate on/off switch. Some how this is not looking good.
So overall I feel scope for improvisation by showing up only important details at the list level and move columns not required into details section.
I would propose few columns like service, description, state and details
On 05/30/2016 05:49 AM, Chandra Shekhar Reddy wrote:
- Column Loaded looks redundant if some how Status represent the same to the user ? IF required this can be moved into details data.
'Loaded' tells if the service definition was loaded in systemd. Some services can have 'masked' status for example. 'Status' is a merge of Active and sub status, where Active is the high-level activation state such as 'active' or 'failed' while Sub is the low-level activation state, like 'running' or 'failed'.
Perhaps this is too advanced when dealing only with services, so I wouldn't complain about moving the 'Loaded' status to the details panel.
We can move this discussion to the ML and talk about the other 2 UI issues the mailing list to gather more feedback.
Daniel
Daniel,
It is good idea.
@All
Please look at below issue raised in the ginger git hub and provide you opinion.
https://github.com/kimchi-project/ginger/issues/352
Thanks and Regards Chandra On 6/1/16 6:33 AM, Daniel Henrique Barboza wrote:
On 05/30/2016 05:49 AM, Chandra Shekhar Reddy wrote:
- Column Loaded looks redundant if some how Status represent the same to the user ? IF required this can be moved into details data.
'Loaded' tells if the service definition was loaded in systemd. Some services can have 'masked' status for example. 'Status' is a merge of Active and sub status, where Active is the high-level activation state such as 'active' or 'failed' while Sub is the low-level activation state, like 'running' or 'failed'.
Perhaps this is too advanced when dealing only with services, so I wouldn't complain about moving the 'Loaded' status to the details panel.
We can move this discussion to the ML and talk about the other 2 UI issues the mailing list to gather more feedback.
Daniel feedback.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kimchi-project/ginger/issues/352#issuecomment-222865327, or mute the thread https://github.com/notifications/unsubscribe/AKVDhcCLr6l4HGQPZAKsS4_yuWKlB7btks5qHNp1gaJpZM4Ipm5P.