[dolphin] [Bug 429251] New: Use Consistent Command for the Same Action

[Andres Betts]

https://bugs.kde.org/show_bug.cgi?id=429251

            Bug ID: 429251
           Summary: Use Consistent Command for the Same Action
           Product: dolphin
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: anditosan1000 at gmail.com
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY
In Dolphin, there are various actions that need a semantic parallel to let the
user know more consistently about what actions they are taking and what that
means. For example:

We have the delete action:

1. Delete
2. Move to trash
3. Trash operation complete
4. Undo trash

This section should probably have stronger indications that to Trash is to send
files to the trash bin, while the Delete action skips the trash bin and erases
a file from the system.

Here are some suggestions:
1. Delete forever
2. Move to trash
3. Moving to trash complete
4. Undo move to trash

This way, the user gets a sense of the differences in approach.

Another is the Properties right click menu item:

Properties is non-specific and can be difficult to understand the properties of
"what" you are reviewing. If the user right clicks the folder pane in an empty
area, the menu item says "Properties". If you right click a folder the menu
item says "Properties". If you right click a file, the menu says "Properties.
While consistent, it is also non-specific.

I suggest adding a modal word next to it that identifies the element. For
example:

File Properties
Folder Properties


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are on the CC list for the bug.