Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bkY0M-00011H-Aa for pgadmin-hackers@arkaria.postgresql.org; Thu, 15 Sep 2016 14:51:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bkY0L-00042m-H0 for pgadmin-hackers@arkaria.postgresql.org; Thu, 15 Sep 2016 14:51:09 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bkY0K-00042d-TF for pgadmin-hackers@postgresql.org; Thu, 15 Sep 2016 14:51:09 +0000 Received: from mail-qk0-x233.google.com ([2607:f8b0:400d:c09::233]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bkY0D-0003xv-7J for pgadmin-hackers@postgresql.org; Thu, 15 Sep 2016 14:51:07 +0000 Received: by mail-qk0-x233.google.com with SMTP id w204so54281817qka.0 for ; Thu, 15 Sep 2016 07:51:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=j4i1YuSJucbjOxNlSMPtHxZDahHARlN0qEpjW+b3Qc8=; b=T4JcQ4CyJZHkp896y5yrgOh+HxoJGbjRhomklP4WY7yVNwRUmdteKfsp1HCURmM25l JnCdC/d7k7A1LQZ7/7neIfv6/x0/bvcu6PBLPjWII1eK1E1BRIMO7kK2X9JHQ1M54ms8 yD7ClgydtHAG9z83yQ/GNmCWehFjOo7I7/mQ8vibubKjww60AQ+9GSP4HbUHnTk5dDl7 FDLHz4+H42eN6BLrI/VhqTEqg2NSJsgUBUYcPpZDsKElLN/rxU5TZ8Uf/6nrbPjnFv8i YsgH5wboDufiifWo6a8pJrfZSJ/Xz/sjeSErKfAHzQfXC5cnBU7/FQRddSWJ8USNQYxU O6/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=j4i1YuSJucbjOxNlSMPtHxZDahHARlN0qEpjW+b3Qc8=; b=ZKT2eIG+R6Y4iKkbzgKlZInqQ3Fp/X51+UIhzmFbnOY/GD6GvOhS7dgtWBUy1QKzGB lupVXGsV490TT9UTpjXAHgXgR1PsbL7JcXTUxL468N9k1zXzOm3/So51Y3snkhFJdS5k LViCtHCdzl4kh6qhg2SLbsn9kp8JSPy0xn0DoTRRgiGcsPE18eTYnz9A37Z/c3JUbEhJ SPxFHG5v3njWjk3opw3X2jnhaUhmeXOToLbd93OHn9hEr93YnflnhMzBvL7VsfcW+9h+ 8Cw00xUQ+775Z129+/n2Ya15g8VeFqfT+w+FRT/eQADySRDseFpLq7d0XeoIyKsh94pd JjmQ== X-Gm-Message-State: AE9vXwOFfKBxasezZGz+ogHPpny17pwf6PryDcozOhWkjrZbD6jaq+sDJl8UTauf3nLZz25na/uXhYaLAUws/g== X-Received: by 10.55.39.215 with SMTP id n206mr10157743qkn.249.1473951059368; Thu, 15 Sep 2016 07:50:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.53.229 with HTTP; Thu, 15 Sep 2016 07:50:58 -0700 (PDT) From: Magnus Hagander Date: Thu, 15 Sep 2016 16:50:58 +0200 Message-ID: Subject: Lack of activity indicator over slow connections (pgadmin4) To: pgadmin-hackers Content-Type: multipart/alternative; boundary=94eb2c09545e4f73d4053c8cf9b5 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --94eb2c09545e4f73d4053c8cf9b5 Content-Type: text/plain; charset=UTF-8 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/ --94eb2c09545e4f73d4053c8cf9b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I've been using pgadmin4 a bit recently over really sl= ow and in particular long-latency connections (double-vpns across the atlan= tic..)

What I've noticed is that there appears to be= zero feedback while things are running. In this case, the slow link was be= tween pgadmin4 and the database it's connected do, but I'd expect s= imilar 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 op= en up developer mode. Which, in fact, I did a couple of times to look at th= e 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 ex= actly the kind of thing that end users will do.

I think that's going to cause a *lot* of confusion. There should real= ly be *some* level of feedback.

I think a very goo= d 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 t= hat it's actually *doing* something.=C2=A0
--94eb2c09545e4f73d4053c8cf9b5--