Re: [Design update] Style guide for pgAdmin4

On Mon, May 22, 2017 at 5:49 PM, Shirley Wang <swang(at)pivotal(dot)io> wrote:

>
>>> In most cases where I've seen a text field with options, usually a drop
>>> down appears automagically without a need for a dropdown icon or x
>>>
>>> [image: googlesearch.gif]
>>>
>>>
>>>
>>> [image: text_field_dropdowns.gif]
>>>
>>
>> Yes, I think that would be an improvement, if it can be done
>> appropriately. I think the reason it's not done that way now is that unlike
>> the examples you gave, in pgAdmin we're searching for one of the existing
>> values in the list, rather than entering a free-type value that might be
>> auto-completed.
>>
>
> That's what the Yelp example shows: they have a list of options
> (Restaurants, Bars, Food, Delivery, Pickup, and Reservations) that show as
> default when there are no options typed. There's just additional features
> included in the GIF, sorry for the confusion. We can ignore the
> auto-completed examples for free type values, and have auto-complete for
> values that exist in the list.
>
> Mainly, if we're enabling users to type, I don't think we need icons
> within each field as the drop down appearing is enough context. However, if
> we are not enabling a user to type, then a drop down icon should appear to
> show that only clicking is allowed to select an option. Thoughts?
>

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.

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

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