Hi,
I've loaded the new GeoServer UI. Generally speaking the color
theme follows the guidelines, but I have the impressions there
is lack of overall balance and contrast.
Please have a look at how it renders on my XP box, as rendered by
Firefox 3, attached. (font antialiasing disable from small size fonts, I don't like the foggy appearance of antialiased ones).
Issues:
- the "important" informations do not stand out. In particular,
- the current page in the breadcrumbs is hard to read, too light,
and too small
- the link portion (admin/config/demo) is smaller than the
descriptive text, and does not have a good contrast with
the background, making it harder to locate
- most of the descriptive text, that you usually read just once,
stands out just like the rest of the capabilities link, and more
than the navigation menu ones
- I'm not really fond of the double color bar at the top (green/blue
one)... seems like a shadow effect, but there is no displacement.
Oh well, just an impression
- Fonts seem almost bold, this makes the lack of antialiasing very
visible. But maybe they are just too big? Any chance the list of
fonts in the CSS can include some ClearType font as well?
Cheers
Andrea
PS: the antialiased/sharp fonts issue is a long standing one, I am
part of that minority that hates the fuzzyness of antialiased
fonts and prefers a well hinted non antialised one instead,
see here: http://www.sharpfonts.com/
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
(attachments)
Andrea Aime ha scritto:
Hi,
I've loaded the new GeoServer UI.
Today I was playing with the GeoServer UI for unrelated stuff
and found out this as well:
http://www.flickr.com/photos/29110296@anonymised.com/3043364594/
It seems there is some problem with how ' are balanced in the
javascript code and a </script> that should have been considered
as a string is interpreted as the end tag for the javascript...
It's just that it really seems ok to me, and in fact Chrome
and IE work fine, it's just FF3 that breaks (but it was working
fine before the style changes... maybe the switch forced it
out of quirks mode and now it's interpreting the contents of
the page in a different way?).
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime ha scritto:
Hi,
I've loaded the new GeoServer UI.
Found an issue with labels as well:
Old coverage data store list page:
http://www.flickr.com/photos/29110296@anonymised.com/3043401482/
New coverage data store list page:
http://www.flickr.com/photos/29110296@anonymised.com/3042563347/
That label going on the new line does not look very nice.
Also mind that the interface is internationalized so there is
no telling how long labels might be, the interface better be
elastic and adapt.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime ha scritto:
Hi,
I've loaded the new GeoServer UI.
Issues in the feature type editor page as well:
New UI
http://www.flickr.com/photos/29110296@anonymised.com/3042576831/
Old UI:
http://www.flickr.com/photos/29110296@anonymised.com/3043417504/
The accessory information such as the SRS wkt has
become more important than the real stuff. There
was a reason the fonts were small and grayed out.
Also notice how the fonts of the edit boxes
are small compared to the rest, again this makes
the real stuff harder to find... I guess the user
is more interested in the values of whatever he
can control than in descriptive text (that you
start ignoring once you have learnt how to use the UI).
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime ha scritto:
Hi,
I've loaded the new GeoServer UI.
Oh, btw, while we're at it, is it possible to improve the
demo page appearance in IE:
http://www.flickr.com/photos/29110296@anonymised.com/3043423100/
(this is not a regression, it looked this bad even before
the style changes).
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.