From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Shirley Wang <swang(at)pivotal(dot)io> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: [PlumAdmin][Weekly Design Update] |
Date: | 2017-02-23 17:16:44 |
Message-ID: | CA+OCxowAVxOo+sM68fJzw=dzv2Ypfw1GcbEa+RJ1RGPraAzkww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
On Thu, Feb 23, 2017 at 5:09 PM, Shirley Wang <swang(at)pivotal(dot)io> wrote:
> Thanks, Dave!
>
> On Thu, Feb 23, 2017 at 4:23 AM Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>
>> Hi
>>
>> On Wed, Feb 22, 2017 at 4:29 PM, Shirley Wang <swang(at)pivotal(dot)io> wrote:
>>
>> Why don't you use the subnode control that we use when expanding rows in
>> other grids? That will provide consistency in design which is key to a good
>> user experience.
>
>
> I'm not sure what the subnode control is, would you be able to attach an
> image of what you mean?
See attached. It's the panel that expands when the Edit icon on a row
is clicked (in this case, the c1 column). We discussed it in our call
last week.
> Yep, from our interviews we found that the reason people want to see recent
> queries is to iterate on it. So being able to see the full query and
> manipulate it somehow is important.
>
>>
>>
>> I prefer that layout.
>
>
> Any particular reason why?
It seems like a more natural position - away from the text so it's not
intrusive, but still highly visible.
Regards, Dave.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment | Content-Type | Size |
---|---|---|
Screen Shot 2017-02-23 at 17.14.12.png | image/png | 80.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Sarah McAlear | 2017-02-23 22:58:51 | [Patch] Organize Vendorized Assets |
Previous Message | Shirley Wang | 2017-02-23 17:09:45 | Re: [PlumAdmin][Weekly Design Update] |