Re: Disabled or Not applicable Tabs design

Hello,

Comments inline..

On Fri, 21 Feb 2025 at 2:51 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:

>
>
> On Fri, 21 Feb 2025 at 09:38, Aditya Toshniwal <
> aditya(dot)toshniwal(at)enterprisedb(dot)com> wrote:
>
>> Hi Hackers,
>>
>> I've been working on a new feature to restore a plain SQL using the
>> pgAdmin restore dialog. Internally, it will select pg_restore or psql based
>> on the format.
>>
>> Now, when restoring plain format the tabs like Data Options,
>> Query Options are not applicable. So instead of going and disabling all the
>> fields under these tabs, I think we can simply disable the complete tab.
>>
>> I've come up with the following UI design for the disabled tabs. The tabs
>> will enable/disable based on the format selected.
>>
>> Please share your feedback on this.
>>
>>
>> [image: image.png]
>>
>
> Normally when something is disabled, it is simply greyed out and made to
> not respond to input. Why not do the same here instead of designing a new
> way of indicating disabled state?
>

*Agreed with Dave. We need to follow the GUI standards while designing, so
that it’s more usable.*

*With the disabled gray label, we might change the disabled tab colour to
dark gray, and on pointer move event, we can show the reason of
disablement.*

*The use of semiotics on tabs may complex or provide a heavy look and feel.*

>

> --
> Dave Page
> pgAdmin: https://www.pgadmin.org
> PostgreSQL: https://www.postgresql.org
> pgEdge: https://www.pgedge.com
>
>