Hi All,
I had some UI confusion with the initial workspace page. I didn't realize that check boxes are only used for deleting workspaces. When looking to view workspaces I would check the boxes, and then select the link. I would like to suggest having an X box instead of a check box that clearly indicates that the workspace is marked for deletion. Or perhaps, even having the delete icon besides each work space would work. I'm not sure what's the best solution. . but as it stands now, I think the interface is confusing.
Let me know if this warrants a Jira thing.
Best,
Alyssa.
alyssa wright ha scritto:
Hi All,
I had some UI confusion with the initial workspace page. I didn't realize that check boxes are only used for deleting workspaces. When looking to view workspaces I would check the boxes, and then select the link.
What selecting the box and clicking the link accomplish? (which link btw)
The "check to mark for multiple actions" is a well known paradigm, Google mail uses exactly the same to perform deletion or marking
for spam (with checks, not x), I'm positive other mail services
do the same (our internal web mail works the same way for example).
I would like to suggest having an X box instead of a check box that clearly indicates that the workspace is marked for deletion.
I see. A red X might be clearer for the time being, at least up until we decide to use the marks for make some other kind of mass operation (mass
change the srs or something like that).
Or perhaps, even having the delete icon besides each work space would work.
We had a delete per row and it was terrible, how do you remove more
than one layer, one by one?
Consider the needs of people managing tens of layers,
not the usual dozen demo ones.
Also, focusing on workspaces is problematic, the table like interface
is one for every page. What we do for workspaces we do for everything
else both for consistency sake and to avoid having to maintain different
code for each page.
Cheers
Andrea
i see your point. . but i still think there's a disconnect between selecting multiple workspaces and knowing what actions are available once selected. i'm not sure how it could best be resolved. but, maybe we need to make the delete buttons closer to the table? if we're modeling after google, they have the scroll through pages at the same level as the delete option, not below.
best,
alyssa.
Andrea Aime wrote:
alyssa wright ha scritto:
Hi All,
I had some UI confusion with the initial workspace page. I didn't realize that check boxes are only used for deleting workspaces. When looking to view workspaces I would check the boxes, and then select the link.
What selecting the box and clicking the link accomplish? (which link btw)
The "check to mark for multiple actions" is a well known paradigm, Google mail uses exactly the same to perform deletion or marking
for spam (with checks, not x), I'm positive other mail services
do the same (our internal web mail works the same way for example).
I would like to suggest having an X box instead of a check box that clearly indicates that the workspace is marked for deletion.
I see. A red X might be clearer for the time being, at least up until we decide to use the marks for make some other kind of mass operation (mass
change the srs or something like that).
Or perhaps, even having the delete icon besides each work space would work.
We had a delete per row and it was terrible, how do you remove more
than one layer, one by one?
Consider the needs of people managing tens of layers,
not the usual dozen demo ones.
Also, focusing on workspaces is problematic, the table like interface
is one for every page. What we do for workspaces we do for everything
else both for consistency sake and to avoid having to maintain different
code for each page.
Cheers
Andrea
alyssa wright ha scritto:
i see your point. . but i still think there's a disconnect between selecting multiple workspaces and knowing what actions are available once selected. i'm not sure how it could best be resolved. but, maybe we need to make the delete buttons closer to the table? if we're modeling after google, they have the scroll through pages at the same level as the delete option, not below.
This has been iterated over quite some times already, so I'm not
sure how to improve it. It just works fine for me.
I'll leave the decision to the design/interaction people.
Cheers
Andrea
I think a way around this is to move the textual link that says "Remove selected ___" to be a button right below (or above) the checkbox column with a simple "Remove". Right now the << < 1 > >> is in between so the eye (well, my eye) doesn't travel to the Remove area.
I'm actually fine with the "Add new ____" being on top of the << < 1 > >>, though, since it's not directly related to the list of existing things.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
Andrea Aime wrote:
alyssa wright ha scritto:
i see your point. . but i still think there's a disconnect between selecting multiple workspaces and knowing what actions are available once selected. i'm not sure how it could best be resolved. but, maybe we need to make the delete buttons closer to the table? if we're modeling after google, they have the scroll through pages at the same level as the delete option, not below.
This has been iterated over quite some times already, so I'm not
sure how to improve it. It just works fine for me.
I'll leave the decision to the design/interaction people.
Cheers
Andrea
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Yes agreed. That what I meant to imply (at least in one point). Apologies for any lack of clarity.
Hope everyone is well,
Alyssa.
Mike Pumphrey wrote:
I think a way around this is to move the textual link that says "Remove selected ___" to be a button right below (or above) the checkbox column with a simple "Remove". Right now the << < 1 > >> is in between so the eye (well, my eye) doesn't travel to the Remove area.
I'm actually fine with the "Add new ____" being on top of the << < 1 > >>, though, since it's not directly related to the list of existing things.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
Andrea Aime wrote:
alyssa wright ha scritto:
i see your point. . but i still think there's a disconnect between selecting multiple workspaces and knowing what actions are available once selected. i'm not sure how it could best be resolved. but, maybe we need to make the delete buttons closer to the table? if we're modeling after google, they have the scroll through pages at the same level as the delete option, not below.
This has been iterated over quite some times already, so I'm not
sure how to improve it. It just works fine for me.
I'll leave the decision to the design/interaction people.
Cheers
Andrea
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel