From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>, Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>, Surinder Kumar <surinder(dot)kumar(at)enterprisedb(dot)com> |
Subject: | Re: Lack of activity indicator over slow connections (pgadmin4) |
Date: | 2016-09-16 08:35:17 |
Message-ID: | CA+OCxow5nvt8yBjx_Oh-6Upa3O4HrR5t14Y7OTiQ1quXxUfscw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Ashesh, Murtuza, Surinder,
Any thoughts on how we can achieve this easily, and where we're
lacking notifications? We did have activity notification in the
treeview, but that never worked overly well and now I come to think of
it, I don't recall seeing it recently. I'm thinking we need something:
- On treeview node click
- On dialogue open and OK
- On Wizard steps
- Possibly in the debugger, when stepping?
I would think all that we need is to set the mouse cursor to 'progress'.
Thoughts?
On Thu, Sep 15, 2016 at 3:50 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> I've been using pgadmin4 a bit recently over really slow and in particular
> long-latency connections (double-vpns across the atlantic..)
>
> What I've noticed is that there appears to be zero feedback while things are
> running. In this case, the slow link was between pgadmin4 and the database
> it's connected do, but I'd expect similar issues when it's pgadmin that's
> far away from the browser.
>
> Basically, clicking on a node in the tree, it took 15-20 seconds before the
> SQL pane updated (or the properties pane). During this time, there is *zero*
> feedback that something is going on, unless I open up developer mode. Which,
> in fact, I did a couple of times to look at the console thinking it had
> crashed rather than was just doing something.
>
> In my case I did the "classic end user" and ended up clicking at a couple of
> different things to see if anything works at all, which of course made
> things even more confusing. But that's exactly the kind of thing that end
> users will do.
>
> I think that's going to cause a *lot* of confusion. There should really be
> *some* level of feedback.
>
> I think a very good choice would be if it's possible to make it do nothing
> by default but if a request takes more than say 1 second, a spinner can show
> up to show that it's actually *doing* something.
>
> --
> Magnus Hagander
> Me: http://www.hagander.net/
> Work: http://www.redpill-linpro.com/
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Seçkin Alan | 2016-09-16 08:42:45 | Re: Finalizing pgadmin4 RPM work |
Previous Message | Devrim Gündüz | 2016-09-16 08:17:04 | Re: Finalizing pgadmin4 RPM work |