----- Original Message ----- Looks great to me! -Amit. -- Amit Saha <http://echorand.me> Software Engineering and Development Red Hat, Inc.

On 12/02/2013 07:29 PM, Jaroslav Kortus wrote: This is one of those cases where a lot of users' intuitions don't match up with usability research: cramming more information into a single screen by making it wider doesn't actually make it easier to use in general. This is why you see a lot more user interfaces these days that have a maximum viewport width, and the Beaker 0.15+ UI is one of them (although as of 0.15.1, we do allow the data tables to overflow when necessary - failing to do that and hence truncating the display of job results was one of the problems in the 0.15 release) More isn't necessarily better though - how much of the old information did you actually *need* to achieve any given task? The Beaker 0.15+ UI is deliberately less dense at the widget level, so we're aiming to show people the information they need when they need it, rather than just dumping everything we have available onto the screen and calling it "good enough" (again, reducing visual density to avoid creating a general impression of noise and clutter is one of the general recommendations coming out of usability research) That page isn't fundamentally changing in Beaker 0.15 (aside from the general improvements to data table pagination), but yes, improving the system table is on our longer term hit list of things to improve given the better web UI tools that are available in Beaker 0.15+ One step at a time though - there are a lot of things that could stand to be improved in the web UI. The system details page is currently at the top of the list for UI improvements because I think it went backwards in usability between 0.14.x and 0.15.1, as the reduced visual density made existing usability issues more obvious. The job results page is similarly guilty of displaying redundant or uninteresting information by default, so that's currently flagged for closer scrutiny in 0.16. I like the "Action" column idea for the system table (similar to the one we have on the Jobs table), but it's out of scope for this update. Having more than one data table on a page is certainly something that should be possible in the future - it wasn't practical given the limitations of the previous web UI toolkit :) For example, something I would eventually like to see is a per-user "usage report" page in the web UI, with the info discussed in this usage email proposal for Beaker 0.16: http://beaker-project.org/dev/proposals/time-limited-manual-reservations.... Cheers, Nick. -- Nick Coghlan Red Hat Hosted & Shared Services Software Engineering & Development, Brisbane Testing Solutions Team Lead Beaker Development Lead (http://beaker-project.org/)

Excerpts from Jeffrey Burke's message of 2013-12-03 01:03:04 +1000: The "Hypervisor" field is supposed to be short for "Type of hypervisor which this system is running inside of, if any". But I agree the name is ambiguous. I've filed a bug for it: https://bugzilla.redhat.com/show_bug.cgi?id=1037280 The screenshots were just a mock-up which I produced by editing the HTML by hand, there's no code behind them yet. Integration with RT has been talked about for a long time but I wasn't planning to tackle it. The "out of service" message would be the existing "Condition report" field, a message which the admin fills in when they mark the system as broken. Although I have been thinking it might make sense to get rid of "Condition report" and use system notes instead. For the "out of service" message it could just display the most recent system note. -- Dan Callaghan <dcallagh(a)redhat.com&gt; Software Engineer, Hosted & Shared Services Red Hat, Inc.