Re: [Design update] Style guide for pgAdmin4

From: Shirley Wang <swang(at)pivotal(dot)io>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: [Design update] Style guide for pgAdmin4
Date: 2017-05-31 13:27:50
Message-ID: CAPG3WN6siK1rz8MzDZTLcsfAUkQ8aGb+b9QrrH4-BPNcj8YT5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

>
>
> When you say "icon" here, are you talking about the combo box arrow, or
> icons on the items themselves? The latter are often useful if you have
> items of different types in the same list.
>
> I think we should have the combo box arrow, to show the user they don't
> have to type if they don't want to.
>

I'm talking about the combo box arrow. I think that's fine, but in that
case users shouldn't be able type, they should only be able to select from
a group of options, like this:

[image: options.png]
From what I understand, the text field where a user can type in is for
searching through options available to them. If we know that people tend to
search by typing more than scrolling, we should use the precedent for type
ahead dropdowns <https://twitter.github.io/typeahead.js/examples/>.

If people don't typically type to search or there are usually only a few
options, it can just be a dropdown.

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2017-05-31 15:48:20 pgAdmin 4 commit: Fix permissions on some files.
Previous Message Murtuza Zabuawala 2017-05-31 12:31:33 [pgAdmin4][PATCH] To fix the issue in index or exclusion contrarians node