Re: Appreciation for pgAdmin 4's progress

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Avin Kavish <avinkavish(at)gmail(dot)com>
Cc: Michel Feinstein <michelfeinstein(at)gmail(dot)com>, richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>, Dave Caughey <caugheyd(at)gmail(dot)com>, Mike Martin <redtux1(at)gmail(dot)com>, Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>, Chin <chinho(dot)dev(at)gmail(dot)com>, "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: Re: Appreciation for pgAdmin 4's progress
Date: 2019-07-31 08:09:33
Message-ID: CA+OCxowDfPhjRxiJ_6rg_dvWjECshvPPwTGQR9BP6FQxUYcDqQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Wed, Jul 31, 2019 at 4:04 AM Avin Kavish <avinkavish(at)gmail(dot)com> wrote:

> First of all since this is an appreciation thread, I want to mention one
> of my favourite features - the map !!! Being able to view GIS data on a
> visual map of earth is the best thing ever. It has saved me from countless
> hours of messing up SRIDs and struggling to get everything right. I can
> always check the map to see if I've made any mistakes with the st_..
> functions. Besides, it's just fun to look at maps :)
>
> I have to plus one better context menus, even as a developer who slams the
> keyboard quite violently, there are times when I power down, lean back and
> use one hand to do copy-pastes. But programmatic access to the users
> clipboard has been limited in web browsers. There's a recent Clipboard API
> <https://developer.mozilla.org/en-US/docs/Web/API/Clipboard_API> addition
> with basic support which maybe worth a look.
>
> Question: Why would a*nyone* ever want to 'Remove Panel', 'Detach
>> Panel', or 'Add Panel' (the only options in the current query tool context
>> menu)?
>
>
> Yeah, why are these options everywhere, wouldn't it suffice to have them
> on the tabs and show different *context* menus elsewhere? Maybe instead
> of hijacking the right click on the query editor just let the click pass
> through and be handled with the default context menu shown by browsers.
>

They are put there by the underlying layout library. Patches are welcome to
change that.

>
>
>
>
> On Tue, Jul 30, 2019 at 11:26 PM Michel Feinstein <
> michelfeinstein(at)gmail(dot)com> wrote:
>
>> I always have one hand at the mouse and one at the keyboard, once I
>> select stuff with the mouse, I hit cntrl+c with the other hand, it's a lot
>> quicker. At least if you don't have any disabilities or are left handed,
>> ctrl+c is at the bottom right corner, where my left hand already rests.
>>
>> On Tue, Jul 30, 2019, 14:49 richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>
>> wrote:
>>
>>> I concur. Ctrl-C/Ctrl-V is basically muscle memory at this point.
>>> Unfortunately though there are times when it's particularly jarring.
>>> Selecting things are done in pgAdmin4 with the mouse/track ball/etc. so
>>> your hand is already off the keyboard. So for example; you select an sql
>>> statement to copy/paste/make a small change/run a process I do all the time
>>> in pgAdmin4. Select->right-click->grumble about *useless options*->Ctrl-C->move
>>> to another area with mouse->Ctrl-V.
>>>
>>> It seems especially strange since if you select a cell in the results
>>> pane the copy / paste options are in *that* context menu.
>>>
>>> Question: Why would a*nyone* ever want to 'Remove Panel', 'Detach
>>> Panel', or 'Add Panel' (the only options in the current query tool context
>>> menu)?
>>>
>>> - You can't move them outside of the tab and only within a of a
>>> smallish portion of the current tab.
>>> - You can't reattach them, so trying to use that option to rearrange
>>> them doesn't work.
>>> - The only way to *fix* it, if you've accidentally selected it is
>>> the *nuclear *option of 'Reset Layout'.
>>>
>>> There are just certain items that people *expect* in a context menu,
>>> especially one that's associated with a text editor. *None* of them
>>> currently exist in the context menu of the query tool. It would be
>>> *nice* if that could be addressed, sooner as opposed to later.
>>>
>>> Thanks,
>>>
>>> rik.
>>>
>>>
>>> On Tue, Jul 30, 2019 at 12:26 PM Dave Caughey <caugheyd(at)gmail(dot)com>
>>> wrote:
>>>
>>>> Correct. But the absence of support in the context menu is a basic UI
>>>> usability issue. Instead we only have "remove panel", "detach panel", "add
>>>> panel".
>>>>
>>>> Context menus are an essential usability feature. A context menu is
>>>> intended to allow the user to quickly access the basic operations that
>>>> apply to whatever is clicked on / selected (i.e., the "context"), and the
>>>> menu items should be biased towards very commonly used actions (e.g., e.g.,
>>>> copy/paste, new, etc.). The most frequently used should be situated near
>>>> the top of the context menu to minimize the mouse movement required to get
>>>> to the desired operation. Less frequently-used stuff should be buried in
>>>> submenus because the usability hit required to get to these uncommon
>>>> operations is a big deal, compared with making it easier to get to the
>>>> common operations.
>>>>
>>>> I totally understand that you don't think it's a big issue because
>>>> (clearly) you're happy to use keyboard shortcuts. But that's that way you
>>>> prefer to work. But many (most?) people rely on context menus, and it's
>>>> just an unnecessary usability irritant when the stuff that you expect to
>>>> find in a context menu is missing (e.g., #4229) or when the context menu
>>>> hasn't had any thought given to the relative frequency of the operations
>>>> (e.g., right-click on a table in the navigation pane, and you'll see
>>>> less-frequently used operations like "Reset Statistics", "Drop Cascaded",
>>>> "Maintenance", all above the super-common operations that are buried under
>>>> "View/Edit Data..." way down at the bottom of the context menu. I.e., the
>>>> table context menu is just about as far from optimal as possible!)
>>>>
>>>> Is the absence/presence and thoughtful layout of context items a major
>>>> functionality gap? No. But is it a *completely unnecessary* every-day
>>>> usability irritant? Yes.
>>>>
>>>> Cheers,
>>>> Dave
>>>>
>>>>
>>>>
>>>> On Tue, Jul 30, 2019 at 11:52 AM Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Tue, Jul 30, 2019 at 4:45 PM Dave Caughey <caugheyd(at)gmail(dot)com>
>>>>> wrote:
>>>>>
>>>>>> No, it doesn't work. It's logged as #4229. It would be *really*
>>>>>> nice if this were fixed.
>>>>>>
>>>>>
>>>>> 4229 is about adding a context menu for it. It works without though -
>>>>> just use Ctrl/Cmd+C and Ctrl/Cmd+V. You can copy query text, cell values,
>>>>> entire rows, or sets of rows.
>>>>>
>>>>> --
>>>>> Dave Page
>>>>> Blog: http://pgsnake.blogspot.com
>>>>> Twitter: @pgsnake
>>>>>
>>>>> EnterpriseDB UK: http://www.enterprisedb.com
>>>>> The Enterprise PostgreSQL Company
>>>>>
>>>>

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Basques, Bob (CI-StPaul) 2019-07-31 14:23:56 How can I add a custom EPSG to the Map (Geometry) Viewer in PGAdmin4,
Previous Message Avin Kavish 2019-07-31 03:04:44 Re: Appreciation for pgAdmin 4's progress