Hi,
I’d like to discuss a potential change in the UI for the sake of consistency.
Once upon a time the UI concept was listing items in tables from container to contained, e.g.,
workspace/store/feature type
However during the years a different paradigm snuck in, listing object name first, and then
its context/containers… and now we have a mix. Here are some examples of the two cases.
Name first, containers/context later
Styles page:
Layer groups:
Layers page:
Picking layers to be added in layer group:
Picking layer groups to be added as child in a parent layer group:
From container to contained
Stores page:
Style association in style editor:
Preview layer chooser:
Observations
The container to contained style makes more sense to me when the container is guaranteed
to be there (it also reads the same way things are named in services, with prefixes).
The name + context style seems to make more sense when the context is optional
(styles, layer groups).
I don’t think we’ll reach a consensus on which direction to take, but wanted to discuss it anyways,
just in case. Personally the ones that bother me now are:
- The current layer page layout, even after years since the change I keep on getting on the store page when I want to open the layer one (am I the only one?) [1]. If the majority likes best the current layout, wouldn’t it makes sense to flip the store page too then?
- The layer group and style preview popups, they are serving the same function with opposite layouts
Cheers
Andrea
[1]: this change was done during the Wicket code sprint , I disagreed with it, but it was done anyways without public discussion
···
== GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.