Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cWi1M-0001Y2-Vy for pgadmin-hackers@arkaria.postgresql.org; Thu, 26 Jan 2017 11:15:17 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cWi1L-00063E-NN for pgadmin-hackers@arkaria.postgresql.org; Thu, 26 Jan 2017 11:15:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cWi16-0005mC-DF for pgadmin-hackers@postgresql.org; Thu, 26 Jan 2017 11:15:00 +0000 Received: from mail-it0-x22e.google.com ([2607:f8b0:4001:c0b::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cWi0w-0000sX-Us for pgadmin-hackers@postgresql.org; Thu, 26 Jan 2017 11:14:59 +0000 Received: by mail-it0-x22e.google.com with SMTP id c7so127552643itd.1 for ; Thu, 26 Jan 2017 03:14:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lgGzX7vDwOtBiCutFg0zC72F8XNxlc3xoX72vAIm8+I=; b=tJhxkOuC0dhcw+VBfx3T1w2nvcUaCUkyeBHFrG7mUro2CoENH7MW3KeO0GBL0Z8hX6 IGM8NOc4/uaSreq2JHy2Di7PSpln/+PltaJS5VO53YCuLicoP3dE3Pwd2UZZyvXek0g4 OmpAuxqlbOi+gYuUgFePmxeJlThmbURZU418w0aH0HFS3jZgBCKNBpGGaXQ8Qg7aqDt8 XmilA6OZoP9wkIGbbb7Trv9RsPe6TSmrOgLCafNGONdiC4dGhOExgCulhq3ZSZEMbUkG cMz50UQOPAK2wDJVst7MXM5S6Owtad5koUIVWMQiAmZslqBZ5lP/HIYqrEvJR5t0t0Ns e3vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lgGzX7vDwOtBiCutFg0zC72F8XNxlc3xoX72vAIm8+I=; b=Jom3Y2Gk0Mx/U5praIoT3k54n8NO1035kHxIgvxgsQf4ZBKAsUtOYyWA0zQ5Mt4Mg6 OMLlxP8sVF1+bkkrnnvo0m2OXl8to+3dGwoEi3V+jprpgvvrf6Z9B885ulNSiC4vua1R Ub1cAiPNYE32G55Pm67Mf7exo9JY5YmHKtKGTn3WyPPuoumLN/gy/BynuvpfejsEj3GB StWDDihbNK02gsD0TJNbeW1vqVeztGbsyeoHjt+U7RUtB4podg5s/Ew9LgdMs7afh3ap 5ZI9ieAFkHRzHRP4FOzTFgEPLg4yfePoX7aAKGuhnY/Di2jkpalm53nt2025sY8ANMwG nADA== X-Gm-Message-State: AIkVDXJ1yGpYjmXOPh6QVGpl3M59HVKkw0ayjvWQm/09bHy56ojY5t+HUNyZropKkn99UBxI77nUN8Ur9PZtgw== X-Received: by 10.107.18.230 with SMTP id 99mr2056627ios.45.1485429288228; Thu, 26 Jan 2017 03:14:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.224.198 with HTTP; Thu, 26 Jan 2017 03:14:47 -0800 (PST) In-Reply-To: References: From: Dave Page Date: Thu, 26 Jan 2017 11:14:47 +0000 Message-ID: Subject: Re: User Research Findings into PgAdmin To: Raffi Holzer Cc: Robert Eckhardt , pgadmin-hackers , Shirley Wang , Edgar Gonzalez Content-Type: multipart/alternative; boundary=001a113fd398106f920546fd75d9 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 --001a113fd398106f920546fd75d9 Content-Type: text/plain; charset=UTF-8 Hi On Wed, Jan 25, 2017 at 8:02 PM, Raffi Holzer wrote: > As a summary of our findings in writing: > > Below is a table of user needs we discovered and solutions we or the > customers suggested. Some of the "missing" features people complained about > are not missing at all (such as auto-complete or syntax highlighting) but > the fact that people didn't know about them points to a discoverability > issue we believe we can address through design. > > > Needs > > Suggested Solutions > > Users need a reliable way to save their queries frequently > > Autosave, Persisting & Complete History, Persisting Un-run queries after > disconnect > Please add feature requests for: - Auto-saving of queries (I believe this would implement persisting un-run queries as well). - Saving of previous queries (implemented in pgAdmin III as a combo box at the top of the editor) > Users need a more efficient way to type > > Auto-discoverable Autocomplete, Customize shortcuts, more visible syntax > highlighting > Please add feature requests for: - Hint mechanism, to display balloon hints that can be triggered during certain tasks to inform the user of functionality they might want to use - Customisable shortcuts (a panel under Preferences -> [Tool Name] to allow customisation of shortcuts in each tool) - Customisable syntax highlight colours > Users need a process to share query output with others > > Copy and Paste into Excel with proper formatting, Export button to MS XML > Please add a feature request for: - Allow customisation of the data copy formatting as found in pgAdmin III. The defaults should be changed to not quote strings and use a tab as the delimiter to allow pasting into Excel/Numbers. Note that tabs cannot be represented in TSV data, so we need to deal with that and warn the user. Pasting back into pgAdmin also needs to support format changes. - Add a drop-down menu to the Export button that the user can use to select data format (the default remaining CSV). This can include XML, JSON and the user-defined copy format (per above). > Users need a way to quickly input content into pgAdmin > > Edit within graphic table > I don't understand that - you can already add/edit/delete data in a grid. > Users need query output to be stored to reuse results > > Results stored in history > Typically users would use multiple query tool windows for that. Saving the results in the history doesn't seem feasible - they can easily run into 10s of MB or more. > Users need an easier way to find saved queries > > Workspace, Search > This would need much more definition. In pgAdmin III we had Macros that allowed you to insert standard queries you had saved in response to a shortcut key, and Favourites that allowed you to store a library of favourite queries and load or inject them into the editor. Plus of course, you can save queries to the file system. What would help here? Oh, and before you ask: https://redmine.postgresql.org/projects/pgadmin4/issues/new :-) Thanks. > > On Wed, Jan 25, 2017 at 10:08 AM, Robert Eckhardt > wrote: > >> My main concern is making the right decisions on what to change, and >>> focussing efforts in the areas where we gain most benefit. Of course, >>> the resources to do the work are also critical - the current team >>> already have a good years worth of work in various additional features >>> and improvements. >>> >> >> Absolutely our concern as well which is why we don't want to work in a >> vacuum. >> >> -- Rob >> >> >>> >>> -- >>> Dave Page >>> Blog: http://pgsnake.blogspot.com >>> Twitter: @pgsnake >>> >>> EnterpriseDB UK: http://www.enterprisedb.com >>> The Enterprise PostgreSQL Company >>> >> >> > > > -- > Raffi Holzer > Product Manager > Pivotal Labs > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --001a113fd398106f920546fd75d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi

On Wed, Jan 25, 2017 at 8:02 PM, Raffi Holzer <<= a href=3D"mailto:rholzer@pivotal.io" target=3D"_blank">rholzer@pivotal.io> wrote:
<= div dir=3D"ltr">As a summary of our findings in writing:=C2=A0

Below is a table of user needs we discovered and solutions we or the= customers suggested. Some of the "missing" features people compl= ained about are not missing at all (such as auto-complete or syntax highlig= hting) but the fact that people didn't know about them points to a disc= overability issue we believe we can address through design.
=C2=A0<= /tbody>

Needs

Sugges= ted Solutions

Users need a reliable way to save their queries frequently

Autosave, Persisting & Complet= e History, Persisting Un-run queries after disconnect


Please a= dd feature requests for:

- Auto-saving of queries = (I believe this would implement persisting un-run queries as well).

- Saving of previous queries (implemented in pgAdmin III = as a combo box at the top of the editor)

=C2=A0
=
Users nee= d a more efficient way to type

Auto-discoverable Autocomplete, Customize shortcuts, more visible syntax= highlighting


Please add feature requests for:
<= br>
- Hint mechanism, to display balloon hints that can be trigge= red during certain tasks to inform the user of functionality they might wan= t to use

- Customisable shortcuts (a panel under P= references -> [Tool Name] to allow customisation of shortcuts in each to= ol)

- Customisable syntax highlight colours
<= div>
=C2=A0

Please add a featu= re request for:

- Allow customisation of the data = copy formatting as found in pgAdmin III. The defaults should be changed to = not quote strings and use a tab as the delimiter to allow pasting into Exce= l/Numbers. Note that tabs cannot be represented in TSV data, so we need to = deal with that and warn the user. Pasting back into pgAdmin also needs to s= upport format changes.

- Add a drop-down menu to t= he Export button that the user can use to select data format (the default r= emaining CSV). This can include XML, JSON and the user-defined copy format = (per above).
=C2=A0

Users need a process to share query output with others

Copy and Paste into Excel with= proper formatting, Export button to MS XML

=

Users need a way to quickly input content into pg= Admin

Edit within graphic tab= le


I don't understand that - you can already add/edit/dele= te data in a grid.
=C2=A0

Users need query output to be stored to reuse = results

Results stored in his= tory


Typically users would use multiple query tool windows for= that. Saving the results in the history doesn't seem feasible - they c= an easily run into 10s of MB or more.
=C2=A0

Users need an easier way to= find saved queries

Workspace= , Search


This would need much more definition. In pgAdmin III = we had Macros that allowed you to insert standard queries you had saved in = response to a shortcut key, and Favourites that allowed you to store a libr= ary of favourite queries and load or inject them into the editor. Plus of c= ourse, you can save queries to the file system. What would help here?
=


Thanks.
=C2=A0

On Wed, Jan 25, 2017 at 10:08 AM, Robert Eckhardt &= lt;reckhardt@pivo= tal.io> wrote:
My main concern = is making the right decisions on what to change, and
focussing efforts in the areas where we gain most benefit. Of course,
the resources to do the work are also critical - the current team
already have a good years worth of work in various additional features
and improvements.

Absolutely our= concern as well which is why we don't want to work in a vacuum.=C2=A0<= /div>

-- Rob
=C2=A0

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

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




--
Raffi Holzer
Product Manager
Pivotal = Labs



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

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Compan= y
--001a113fd398106f920546fd75d9--