Ticket #416 (closed Enhancement: fixed)

Opened 7 years ago

Last modified 4 years ago

include "edit" function in context menu and/or automaticly just by clicking into the field

Reported by: JuergeN Owned by: jri
Priority: Major Milestone:
Component: DeepaMehta Standard Distribution Version: 4.0.14
Keywords: Cc: dgf, Malte
Complexity: 3 Area: GUI / Usability
Module: deepamehta-webclient

Description

The "edit" function and other context based functions that appear in the buttom of the details panel (e.g. "open URL", etc.) should be included in the context menu (right click on topic) for usability reasons. Another option would be to enter "edit" mode just by clicking into the row/field in the details panel, if user has the right to edit the topic.

From my observation many people just try to edit a field by clicking into it and do not "see" the edit button at the bottom of the page. Same is true for "open URL" etc.

Change History

comment:1 Changed 7 years ago by jri

  • Owner set to jri
  • Cc dgf, Malte added
  • Status changed from new to accepted
  • Milestone set to Release 4.1

That's an interesting observation. Thank you for that!

Yes, the context menu brings the commands close to the objects. This is a strong advantage, cognition-wise. On the other hand it is *invisible*. That's a strong disadvantage. I often see normal users who never get the idea to right-click something when there is no visible affordance. They want *see* before they click. Those users complain just in the other direction: they want all context menu commands, e.g. "Delete", as *visible* buttons in the lower toolbar.

Perhaps on-mouse-over "Command Halos" (see #15) can combine the respective strengths of both approaches.

Anyway, for the DM developer its very easy to place commands a) in the context menu, b) in the lower toolbar, or c) in both locations. Should possibly *all* commands available in both locations? (I don't know.)

I will start with putting the "Edit" command in the context menu. More commands will follow.

Your other aspect (enter "edit" mode just by clicking into the row/field) is very interesting too! I think we should target for this. Some details remain to be discussed. 1) Should only the clicked field enter edit mode, or all fields? 2) How to "confirm"? Is there still an "OK" button? (However, confirmation is not strictly required as all content is auto-saved anyway).

Thanks, JuergeN!

Last edited 7 years ago by jri (previous) (diff)

comment:2 Changed 7 years ago by jri

BTW: the "Open URL" and "Open URL in new windows" commands appear already at both locations: context menu and lower toolbar. Make sure to right-click an "URL" topic, not a "Web Resource" topic.
(Having the parent topic to adopt the child topic's commands would be imaginable. We could open another ticket for that.)

comment:3 Changed 7 years ago by Jörg Richter

Webclient: "Edit" command in context menu (#416).

The "Edit" command appears in the context menu (additionally to lower toolbar).

See ticket 416.

comment:4 Changed 7 years ago by JuergeN

The edit and retype commands should also be included in the context menu of associations. As of today this did not seem to be implemented yet.

Last edited 7 years ago by JuergeN (previous) (diff)

comment:5 Changed 7 years ago by jri

Oh, you're right. I forgot to put "Edit" in the association context menu.

However, "Retype" is different. Associations have no explicit Retype command. Instead retype is part of edit. This is because the association type and the corresponding role types are typically edited together. For associations retyping takes place in the detail panel. In contrast, Topic retyping takes place in a separate dialog box. The thought here is that topics are retyped much more rarely than associations. On the other hand topic content is much more often edited than association content. So it seemed not reasonable to mix topic edit and topic retype in the same panel. That's why topics have an explicit Retype command but associations have not.

comment:6 Changed 7 years ago by Jörg Richter

Webclient fix: Edit in assoc context menu (#416).

The "Edit" command appears in the association's context menu (additionally to lower toolbar).

Webclient public client-side API:

2 new methods in AssociationType? model class:

  • is_hidden()
  • is_locked()

See ticket 416.

comment:7 Changed 7 years ago by jri

  • Milestone changed from Release 4.1 to Release 4.2

comment:8 Changed 6 years ago by jri

  • Milestone Release 4.2 deleted

comment:9 Changed 4 years ago by JuergeN

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.