First of all, thank you again for all the hard work you've put into this excellent product/project. Now for the complaint...
I just upgraded from 2.2 to 3.0. About the GUI overhaul in 3. Why the fudge???? What was the point? Surely, the GUI needed updating. But the new GUI fixes almost nothing that was wrong with the old one, and breaks many things that were right. The "cleaner" more modern look is in my very strong opinion a step backwards: it feels like an attempt to copy the other dumbed-down UXs. Just because Google's UX design group goes "clean" doesn't mean it's the right or useful thing for everyone else.
FWIW: I understand if the new GUI reflects an underlying change to the CSS/PHPmechanics, but it should have been refactored without designing away the existing look-feel.
FWIW #2: I know I should be involved more and complain less, and I want to; but currently I must focus my energy on other battles.
Broken / bad changes:
Good / useful changes: (from 2.2)
Still not fixed, dammit!
See next post. Apparently I can't have so many lists in a post.
I just upgraded from 2.2 to 3.0. About the GUI overhaul in 3. Why the fudge???? What was the point? Surely, the GUI needed updating. But the new GUI fixes almost nothing that was wrong with the old one, and breaks many things that were right. The "cleaner" more modern look is in my very strong opinion a step backwards: it feels like an attempt to copy the other dumbed-down UXs. Just because Google's UX design group goes "clean" doesn't mean it's the right or useful thing for everyone else.
FWIW: I understand if the new GUI reflects an underlying change to the CSS/PHPmechanics, but it should have been refactored without designing away the existing look-feel.
FWIW #2: I know I should be involved more and complain less, and I want to; but currently I must focus my energy on other battles.
Broken / bad changes:
- Table views no longer have vertical grid markers, which really helped to define empty columns and create "negative white space"
- Table rows no longer have alternating background shades. Thanks for making long rows harder to read! (Yeah, you can roll over them, but the point is, before, you didn't have to... a screen shot could make nice, easy-to-read reports.)
- Item filter no wtakes up most of the page. Gone is the succinct compactness it previously had. The subsections ("APPLICATIONS", "STATUS") are in the same font as the filters ("Disabled") but are in a smaller font, and grayish, making them hard to read. The number count by each filter item, again in gray, is confusing and distracting.
- No more breadcrumbs? I can understand why this behavior is thought to be outmoded, but it should at least be a UX option.
- Typically-bookmarked pages such as _dashboard.php_ really should have a redirect to their new page.
- Top-level hot-selection via rollover. This made sense to me and I thought was a big improvement in 1.6 or 1.8 or whenever. Was it a problem for peeps?
Good / useful changes: (from 2.2)
- Editing an itemFull itemid/hostid in URL. The session-specific stuff was obviously a fail. Sometimes it's really useful to edit multiple hosts' items side-by-side in different browser tabs, and the session-anchoring led to errors and misconfigurations.
- Table header rows and items are more compact and easier to read. However, a minor grudge: the selected sorting field will be of the exact same font and color as the data elements in the rows below.
- Able to jump directly to a hosts' main configuration page from one of its configuration sub-pages. I think this was missing in 2.2.
- Host view Filtering options.

Still not fixed, dammit!
See next post. Apparently I can't have so many lists in a post.
Comment