[jopr-dev] request for comments - timeline view
Heiko W.Rupp
hwr at redhat.com
Sun Feb 15 16:19:27 EST 2009
Am 15.02.2009 um 21:15 schrieb Joseph Marques:
> the dual monitors i do my primary development on are standard aspect
> ratio (though, my resolution is 1600x1200). yes, there are a
We should cater for people with 1280 px in screen width. The following
is from the web server of one of my domains:
1280*x makes 45% of all views and 1024*x makes for another 23%.
1280x800 29.9 %
1024x768 23.5 %
1280x1024 15.9 %
1440x900 8.2 %
1680x1050 7 %
Others 15.2 %
One may estimate that IT ops have the big screens, but we should not
count on it.
> lot of tabs, but i'm less worried about the quantity of data shown
> than i am about the placement of data and how intuitive things
This lots of tabs worries me. And the lots of meicoa icons
> would be to find. case in point: microsoft word is a "busy"
> application with it's ten or so default menus, and the 40 or so
> icons on the two default toolbars, but having access to all of those
> things at a glance because of they properly named and have somewhat
> intuitive icons to identity what they do helps tremendously. i
> could see us in the future perhaps even replacing the text of
> "monitor",
On the other hand, there are many people out there, that especially
see Word as the prime example of complete
feature overload.
> "events", "configuration", "operations", "alerts", "content" with
> more easily recognizable icons altogether (or maybe that would be a
> user option [icon+text vs. icon-only vs. text-only]).
Icon only is bad. There are a few standard icons (e.g. disk symbol to
save), but otherwise most of time the same icon
has three different meanings in two programs.
>> But - if we are to add a new tab, I do like the idea of a summary
>> tab. That should probably be the landing tab when selecting a new
>> resource from the Browse Resources (or any link when moving from a
>> page without a resource in context).
> i would agree, it would be an ideal place to place links that don't
> explicitly navigate to one of the other tabs via the "mica" icons.
Yes indeed.
Adding the display timerange there would allow to see historic data.
RHQ-1496 has code to dynamically load availability
data and to autorefresh the timeline, so that users could change the
range and a refresh of the timeline would show the
right stuff.
Simile also has a tiemeplot library, that is timeline + graphs, so one
could even put some indicator charts in it.
Heiko
--
Reg. Adresse: Red Hat GmbH, Otto-Hahn-Strasse 20, 85609 Dornach bei
Muenchen
Handelsregister: Amtsgericht Muenchen HRB 153243
Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham,
Werner Knoblich
More information about the jopr-dev
mailing list