Hi,
one thing tha bothers me about the new UI is that all
the ajax-y action give the user no actual feedback on
the fact the call is running, doing something.
Then I stumbled into this blog:
http://blog.ehour.nl/index.php/archives/18
(see the very bottom of it).
Long story short, it's not hard to show a spinning
animated GIF somewhere in the UI (maybe play an
animation with the very GeoServer logo?).
But we'd have to provide a GeoServer specific subclass
for links and buttons that adds the callback
decorator and replace the usage in all the UI
code.
What do you think?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Seems worth the work to me. This would apply to any AjaxLink we link we use? I know that there is code that uses AjaxLink vs AjaxButton and vice versa. Would this apply to both? Or do need to choose one over the other?
Andrea Aime wrote:
Hi,
one thing tha bothers me about the new UI is that all
the ajax-y action give the user no actual feedback on
the fact the call is running, doing something.
Then I stumbled into this blog:
http://blog.ehour.nl/index.php/archives/18
(see the very bottom of it).
Long story short, it's not hard to show a spinning
animated GIF somewhere in the UI (maybe play an
animation with the very GeoServer logo?).
But we'd have to provide a GeoServer specific subclass
for links and buttons that adds the callback
decorator and replace the usage in all the UI
code.
What do you think?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Seems worth the work to me. This would apply to any AjaxLink we link we use? I know that there is code that uses AjaxLink vs AjaxButton and vice versa. Would this apply to both? Or do need to choose one over the other?
It would apply to both. Actually, to anything that has an ajax behavior
attached to it.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Seems worth the work to me. This would apply to any AjaxLink we link we use? I know that there is code that uses AjaxLink vs AjaxButton and vice versa. Would this apply to both? Or do need to choose one over the other?
It would apply to both. Actually, to anything that has an ajax behavior
attached to it.
Cool, i would say open a jira and file it under the usability and improvements issue?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Hi Andrea,
I do very much share the concern. Yet, earlier this month I tried another way of doing so (you gave me the link to the example), which I accidentally committed and then reverted. So we have a diff:
<http://fisheye.codehaus.org/changelog/geoserver/?cs=12533>
Look at the diff, the only thing needed would be to replace the "<h1>Can't touch this</h1>" by the actual animated "processing" icon.
Now, this is a lot less work, but I'm not sure how the other approach might be better. Perhaps you know since you're the one that got to both solutions?
Cheers,
Gabriel
Andrea Aime wrote:
Hi,
one thing tha bothers me about the new UI is that all
the ajax-y action give the user no actual feedback on
the fact the call is running, doing something.
Then I stumbled into this blog:
http://blog.ehour.nl/index.php/archives/18
(see the very bottom of it).
Long story short, it's not hard to show a spinning
animated GIF somewhere in the UI (maybe play an
animation with the very GeoServer logo?).
But we'd have to provide a GeoServer specific subclass
for links and buttons that adds the callback
decorator and replace the usage in all the UI
code.
What do you think?
Cheers
Andrea
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
These are the direct links to the changes:
<http://fisheye.codehaus.org/browse/geoserver/trunk/src/community/web2/core/src/main/java/org/geoserver/web/GeoServerBasePage.html?r1=12532&r2=12533>
<http://fisheye.codehaus.org/browse/geoserver/trunk/src/community/web2/core/src/main/java/org/geoserver/web/GeoServerBasePage.java?r1=12532&r2=12533>
Gabriel Roldan wrote:
Hi Andrea,
I do very much share the concern. Yet, earlier this month I tried another way of doing so (you gave me the link to the example), which I accidentally committed and then reverted. So we have a diff:
<http://fisheye.codehaus.org/changelog/geoserver/?cs=12533>
Look at the diff, the only thing needed would be to replace the "<h1>Can't touch this</h1>" by the actual animated "processing" icon.
Now, this is a lot less work, but I'm not sure how the other approach might be better. Perhaps you know since you're the one that got to both solutions?
Cheers,
Gabriel
Andrea Aime wrote:
Hi,
one thing tha bothers me about the new UI is that all
the ajax-y action give the user no actual feedback on
the fact the call is running, doing something.
Then I stumbled into this blog:
http://blog.ehour.nl/index.php/archives/18
(see the very bottom of it).
Long story short, it's not hard to show a spinning
animated GIF somewhere in the UI (maybe play an
animation with the very GeoServer logo?).
But we'd have to provide a GeoServer specific subclass
for links and buttons that adds the callback
decorator and replace the usage in all the UI
code.
What do you think?
Cheers
Andrea
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Gabriel Roldan ha scritto:
Hi Andrea,
I do very much share the concern. Yet, earlier this month I tried another way of doing so (you gave me the link to the example), which I accidentally committed and then reverted. So we have a diff:
<http://fisheye.codehaus.org/changelog/geoserver/?cs=12533>
Look at the diff, the only thing needed would be to replace the "<h1>Can't touch this</h1>" by the actual animated "processing" icon.
Now, this is a lot less work, but I'm not sure how the other approach might be better. Perhaps you know since you're the one that got to both solutions?
Actually I thought the one I gave you the link for was setting a veil
on top of the ajax component, did not realize it was working also
page wide.
So yeah, it looks like a winner
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.