Hi,
I am having trouble understanding the reasoning behind the 2.0 menu architecture. Currently the vertical layout makes seem like server options trump services trump data. I think it would be a great improvement to the interface to make the menus collapsible/accordion.
Thanks,
Alyssa.
I think it would be a great improvement to the interface to make the menus collapsible/accordion.
+1 on this (collapsed by default), if it's possible.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
alyssa wright wrote:
Hi,
I am having trouble understanding the reasoning behind the 2.0 menu architecture. Currently the vertical layout makes seem like server options trump services trump data. I think it would be a great improvement to the interface to make the menus collapsible/accordion.
Thanks,
Alyssa.------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Could you create a JIRA ticket for this?
--
David Winslow
OpenGeo - http://opengeo.org/
On Tue, 2009-06-23 at 16:50 -0400, alyssa wright wrote:
Hi,
I am having trouble understanding the reasoning behind the 2.0 menu
architecture. Currently the vertical layout makes seem like server
options trump services trump data. I think it would be a great
improvement to the interface to make the menus collapsible/accordion.Thanks,
Alyssa.------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Done and done:
http://jira.codehaus.org/browse/GEOS-3189
David Winslow wrote:
Could you create a JIRA ticket for this?
--
David Winslow OpenGeo - http://opengeo.org/On Tue, 2009-06-23 at 16:50 -0400, alyssa wright wrote:
Hi,
I am having trouble understanding the reasoning behind the 2.0 menu architecture. Currently the vertical layout makes seem like server options trump services trump data. I think it would be a great improvement to the interface to make the menus collapsible/accordion.
Thanks,
Alyssa.------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
alyssa wright ha scritto:
Hi,
I am having trouble understanding the reasoning behind the 2.0 menu architecture. Currently the vertical layout makes seem like server options trump services trump data. I think it would be a great improvement to the interface to make the menus collapsible/accordion.
I would find that a regression unless the menu items become really
really many. Why do I have to click twice to get anywhere?
Cheers
Andrea
I see what you mean, Andrea, but my response would be:
"So I don't get confused/overwhelmed and so I can see only what I want to see"
I'd be fine having it "remember" whether the menus are collapsed or not, so that fearless pros can expand them once (and then never have to click twice again) and those who don't need to expand everything won't have to.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
Andrea Aime wrote:
alyssa wright ha scritto:
Hi,
I am having trouble understanding the reasoning behind the 2.0 menu architecture. Currently the vertical layout makes seem like server options trump services trump data. I think it would be a great improvement to the interface to make the menus collapsible/accordion.
I would find that a regression unless the menu items become really
really many. Why do I have to click twice to get anywhere?Cheers
Andrea------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Mike Pumphrey ha scritto:
I see what you mean, Andrea, but my response would be:
"So I don't get confused/overwhelmed and so I can see only what I
want to see"I'd be fine having it "remember" whether the menus are collapsed or
not, so that fearless pros can expand them once (and then never have
to click twice again) and those who don't need to expand everything
won't have to.
Err.... I fail to see how looking at a 10-12 items menu requires a pro... if you look at 4 items menu you still need to figure out
what the classification schema used is. "where I would put the
layer configuration? would it be in data or services?"
(if you know nothing about how geoserver is made both are legit)
Cheers
Andrea
For historical reference, the reason we decided to make them all up front is because the current 'hospital green' UI hide everything and is very frustrating to newbies and power users alike. Most people enter GeoServer with a specific task in mind—putting all the nav items out there facilitates getting in, getting it done, and getting out. What' the rationale for hiding them?
On Jun 24, 2009, at 5:32 AM, Andrea Aime wrote:
Mike Pumphrey ha scritto:
I see what you mean, Andrea, but my response would be:
"So I don't get confused/overwhelmed and so I can see only what I
want to see"I'd be fine having it "remember" whether the menus are collapsed or
not, so that fearless pros can expand them once (and then never have
to click twice again) and those who don't need to expand everything
won't have to.Err.... I fail to see how looking at a 10-12 items menu requires a
pro... if you look at 4 items menu you still need to figure out
what the classification schema used is. "where I would put the
layer configuration? would it be in data or services?"
(if you know nothing about how geoserver is made both are legit)Cheers
Andrea------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
for me the rational in hiding them, is not about overwhelm. rather, its about the hierarchy of options. the current hierarchy doesn't sync with how i use geoserver. for me, data is the most active part of my geoserver time, yet its all the way on the bottom. server details are not things im going to change, yet its all the way on the top. this may not be what people use geoserver for--data work--but its how i use geoserver.
having the menu be collapsible doesn't mean we're hiding things deep within subpages, as in the current UI. it means those 4/5 iteams on the top level carry equal weight.
and, as an aside, the about geoserver seems too far hidden in a submenu.
again, just my 2 cents.
alyssa.
Rolando Peñate wrote:
For historical reference, the reason we decided to make them all up front is because the current 'hospital green' UI hide everything and is very frustrating to newbies and power users alike. Most people enter GeoServer with a specific task in mind—putting all the nav items out there facilitates getting in, getting it done, and getting out. What' the rationale for hiding them?
On Jun 24, 2009, at 5:32 AM, Andrea Aime wrote:
Mike Pumphrey ha scritto:
I see what you mean, Andrea, but my response would be:
"So I don't get confused/overwhelmed and so I can see only what I
want to see"I'd be fine having it "remember" whether the menus are collapsed or
not, so that fearless pros can expand them once (and then never have
to click twice again) and those who don't need to expand everything
won't have to.
Err.... I fail to see how looking at a 10-12 items menu requires a
pro... if you look at 4 items menu you still need to figure out
what the classification schema used is. "where I would put the
layer configuration? would it be in data or services?"
(if you know nothing about how geoserver is made both are legit)Cheers
Andrea------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
alyssa wright ha scritto:
for me the rational in hiding them, is not about overwhelm. rather, its about the hierarchy of options. the current hierarchy doesn't sync with how i use geoserver. for me, data is the most active part of my geoserver time, yet its all the way on the bottom. server details are not things im going to change, yet its all the way on the top. this may not be what people use geoserver for--data work--but its how i use geoserver.
You have a point there. But we could solve it by reordering the menu
and putting data near the top.
Cheers
Andrea
Andrea Aime wrote:
alyssa wright ha scritto:
for me the rational in hiding them, is not about overwhelm. rather, its about the hierarchy of options. the current hierarchy doesn't sync with how i use geoserver. for me, data is the most active part of my geoserver time, yet its all the way on the bottom. server details are not things im going to change, yet its all the way on the top. this may not be what people use geoserver for--data work--but its how i use geoserver.
You have a point there. But we could solve it by reordering the menu
and putting data near the top.
+1, as long as that's easy to do. If not can revisit for the next release, I think we're targeting bigger UI improvements for that, this release is more about replacing the UI technology and making things a bit better.
Cheers
Andrea------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Chris Holmes
OpenGeo - http://opengeo.org
Expert service straight from the developers.
i would be into that.
just so you know, its hard for me to make hard and fast recommendations for geoserver, as i'm still determining how people use it. (as i said to mike yesterday, what's the heart of geoserver? or something like that.) so these suggestions are coming from a beginner's perspective. which had value in and of itself, of course. but is obviously not the only--or even most important--consideration.
hope everyone is well,
alyssa.
Andrea Aime wrote:
alyssa wright ha scritto:
for me the rational in hiding them, is not about overwhelm. rather, its about the hierarchy of options. the current hierarchy doesn't sync with how i use geoserver. for me, data is the most active part of my geoserver time, yet its all the way on the bottom. server details are not things im going to change, yet its all the way on the top. this may not be what people use geoserver for--data work--but its how i use geoserver.
You have a point there. But we could solve it by reordering the menu
and putting data near the top.Cheers
Andrea
alyssa wright ha scritto:
i would be into that.
just so you know, its hard for me to make hard and fast recommendations for geoserver, as i'm still determining how people use it. (as i said to mike yesterday, what's the heart of geoserver? or something like that.) so these suggestions are coming from a beginner's perspective. which had value in and of itself, of course. but is obviously not the only--or even most important--consideration.
hope everyone is well,
So, would it be better if the menu looked like in the attached screenshot? It's a matter of changing 3 lines.
I tried to sort it from most used to less used in terms of sections.
Cheers
Andrea
Been chatting with Jody, Justin, Gabriel and a bunch of users - we had
an idea which might be relevant here...
Role-based wizards - this would address the concerns here in two ways:
1) you show the options most relevant to the role of the user -
service deployer vs system admin vs developer vs configuration
designer vs data expert vs presentation.
2) the wizard allows you to hide or demote stuff you've already completed
Jody says there are wizard workflow support hooks in wicket, maybe
there is a sort of pluggable wizard so we can have community modules
for different roles, so people can make the workflow and layout that
matches the different requirements.
Rob
On Thu, Jun 25, 2009 at 3:30 AM, Andrea Aime<aaime@anonymised.com> wrote:
alyssa wright ha scritto:
i would be into that.
just so you know, its hard for me to make hard and fast recommendations
for geoserver, as i'm still determining how people use it. (as i said to
mike yesterday, what's the heart of geoserver? or something like that.) so
these suggestions are coming from a beginner's perspective. which had value
in and of itself, of course. but is obviously not the only--or even most
important--consideration.hope everyone is well,
So, would it be better if the menu looked like in the attached screenshot?
It's a matter of changing 3 lines.
I tried to sort it from most used to less used in terms of sections.Cheers
Andrea------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel