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

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?

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

EDB: https://www.enterprisedb.com