Tables: why are menus so inconsistent?

I just installed the new 0.6.0 version of Tables, and I have to say I’m totally impressed with the progress, kudos to the devs!

However, I noticed that there are context menus for tables/views at several different places, and all of them are slightly different for some reason. There’s some differences I can understand (e.g. don’t offer the “create column” operation unless the table/view is actually displayed, and the current columns can be seen), but as for the others, I’m really confused. To begin with, why are some context menus divided into categories, while on others, the same items are just dumped there?

And for something that’s missing and I think we should have it: clone table (with/without data).

For reference, I created a summary of the different context menus I could find:

table - left pane
  • edit
  • create view
  • share
  • import
  • integration
  • delete
table - top right corner
manage:
  • edit
  • create view
  • create column
integration:
  • import
  • export CSV
  • share
  • integration
view - left pane
  • edit
  • duplicate
  • share
  • import
  • integration
  • delete
view - top right corner
manage:
  • edit
  • create column
integration:
  • import
  • export CSV
  • share
  • integration
view - in list of views of a table
  • edit
  • share
  • integration
  • delete

Hi,

thanks for your feedback here.
For feature requests, feel free to open well described feature requests on github.

About the menus. The idea is:

  • to keep them short and simple!
  • focus on managing the table/view etc in the left nav
  • focus on managing the data inside a table/view etc
  • allow all action without having the left navigation (on smaller screens)

Is that reasonable for you?
Do you have a concrete suggestion how it could look like?

cheers

I see where you’re coming from. But unfortunately, just by looking at the UI, this logic can’t be deduced, and it is thus quite confusing.

Having different subsets of items of the same context menu at different places doesn’t feel logical. I would expect to see the same menu, when it comes to actions involving the same subject (e.g., table scope all the same, just accessed from either the left pane or the top right).

Also, if these would be menus with dozens of potential items, then it would make some sense to try and shorten them based on “managing the table” vs. “managing the data”. But they having no more than 6 items, this doesn’t seem to be a concern to me either.

It’s totally up to you of course, this is just a UX issue ultimately. But I definitely felt confused enough by the layout to go ahead and construct this post.

Hi,

I am always interested in feedback and design and ux is a very important thing.
I am very busy atm, let check this in detail next week.

But I will remove the “bug” label from the github issue, as this is no bug and more a discussion…

Btw: As an ux interested person, may I ask you for a feedback for this? https://github.com/nextcloud/tables/pull/446#issuecomment-1806816456

regards