| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Disabled or Not applicable Tabs design |
| Date: | 2025-02-21 09:50:56 |
| Message-ID: | CA+OCxowh9naNcC9Kc8g+ej9XDEynAhOzFZU1zYxpwuzyc_FBSg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
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?
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zaid Shabbir | 2025-02-21 10:11:47 | Re: Disabled or Not applicable Tabs design |
| Previous Message | Aditya Toshniwal | 2025-02-21 09:37:40 | Disabled or Not applicable Tabs design |