Re: Rename context "Properties..." menu to "Edit Object..."

From: Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>
To: Dave Page <dave(dot)page(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Rename context "Properties..." menu to "Edit Object..."
Date: 2023-03-29 10:54:40
Message-ID: CAM9w-_=fwNrR48WikFh1RW2bOoDw7kL8akd25UxUy3zQUL7vGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Dave,

On Wed, Mar 29, 2023 at 3:59 PM Dave Page <dave(dot)page(at)enterprisedb(dot)com>
wrote:

>
>
> On Wed, 29 Mar 2023 at 11:11, Aditya Toshniwal <
> aditya(dot)toshniwal(at)enterprisedb(dot)com> wrote:
>
>> Hi Hackers,
>>
>> One of the users had raised a concern regarding confusing "Properties"
>> label - one on the tab (read only) and another one on context(to edit) -
>> https://github.com/pgadmin-org/pgadmin4/issues/4734. We are using the
>> label "Edit the object" on the Edit button of the properties tab already.
>> So I suggest we should rename the context "Properties..." to "Edit
>> Object..."
>> for consistency as well as to make it more meaningful.
>>
>> Thoughts?
>>
>
> I disagree. "Properties" is the standard name for that type of dialogue
> throughout Windows and many/most Linux windowing systems (e.g. Gnome). On
> macOS, the equivalent is "Get Info". I don't think we should deviate from
> a few decades of use of that name based on a single ticket (if anything,
> maybe we should make it say "Get Info" when the UI is displayed on a mac).
>
> Dave's point in his bug report is mostly that we also use the term
> "Properties" for the panel in the main UI in which we display some
> properties (but not all, and sometimes extra, over what is in the
> dialogue). I would not object to renaming that panel to "Object Summary" or
> similar, to correspond with "Object Explorer".
>
> Which then leads to another thought - we've used one-word naming in the
> past for tabs. We now have "Object Explorer", and I just suggested "Object
> Summary" - but those imply we should also have "Object Dependencies",
> "Object Dependents", and "Object SQL", which I definitely do not like.
>
> So maybe everything should have a one word label?
>
I am fine with renaming the tab instead of the context menu. We can rename
the "Properties" tab to just "Summary"/"Info" and everything works as
before. We don't need to add "Object" to tabs.

>
> --
> Dave Page
> VP, Chief Architect, Database Infrastructure
> Blog: https://www.enterprisedb.com/dave-page
> Twitter: @pgsnake
>
> EDB: https://www.enterprisedb.com
>

--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | *edbpostgres.com*
<http://edbpostgres.com>
"Don't Complain about Heat, Plant a TREE"

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message dependabot[bot] 2023-03-29 11:05:26 [pgadmin-org/pgadmin4] c81636: Python dependency: Bump eslint from 6.8.0 to 8.37....
Previous Message Dave Page 2023-03-29 10:29:15 Re: Rename context "Properties..." menu to "Edit Object..."