Ticket #28 (closed: wontfix)
New context menu is worse
| Reported by: | mbiebl | Owned by: | alwin |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | All | Version: | |
| Severity: | feature | Keywords: | |
| Cc: |
Description
I don't like the the new context menu where all items are grouped in submenus. A context menu should provide quick access to the most common actions. Take konqueror for example: The context menu provides quick access to the 5-7 most used actions and only moves actions into submenus that are used less often. Good candidates for direct access would be:
Add Delete Revert Diff against head
Attachments
Change History
comment:1 Changed 8 years ago by mbiebl
- Owner changed from anonymous to alwin
- Status changed from new to assigned
comment:2 Changed 8 years ago by niko
imho the menu is better than before - but not perfect :D
my candidates would be
- update
- commit
- Full Log
- Diff against head
- Blame(?)
and people that use locking will need these items very often.
....so i think everybody will need different items - TortoiseSVN makes it configurable which is a good solution imho
comment:3 Changed 8 years ago by mbiebl
Sorry, didn't want to sound so harsh...
- commit
- Full Log
- Diff against head
I would second that, this points seem reasonable, too. I just wanted to make my point a little bit clearer with my suggestions.
Although I have to admit that I like your first idea (bug #0000020) about dynamic context menus best. So for example unversionied files would only have to have Add and Ignore in their context menu and for versionied files Add could be dropped.
comment:4 Changed 8 years ago by alwin
Sorry, didn't want to sound so harsh...
Ah no, you didn't ;)
Well - as said: its hard to implement. I have no idea that moment. Hard that way, which items to select for which state. 'cause listview is multiselectable there are a lot of possible combinations, include that one where items are using EXCLUDING items. eg. some files are unversioned, some must commited, some are stateless (== no changes against repostiorie) and so on.
So I think, I'll should reduce it to up to 5 entries them would always same:
- working copy:
- update to head
- commit
- full log
- diff
- blame
- repository:
- full log
- checkout current path
- export current path
- blame
- cat head
What about, guys?
comment:5 Changed 8 years ago by niko
nice!
all other commands are still avaliable through the toolbar and/or menubar - thats the purpose of a context-menu.
comment:6 Changed 8 years ago by alwin
- Keywords RESOLVED added
- Status changed from assigned to closed
- Resolution set to fixed
no protests anymore - mark it as fixed.
comment:7 Changed 7 years ago by DHauptmann
- Keywords FEEDBACK added; RESOLVED removed
- Status changed from closed to assigned
- Resolution fixed deleted
In version 0.9.2 the 'blame' entry is missing. Bug or Feature?
comment:8 Changed 7 years ago by alwin
more a "please don't overload the contextmenu with features" problem. And seems that blaming isn't that used like the other entries. Of course it would nicer having a editor for contextmenus like for toolbars, but this is more a kde "problem".
comment:9 Changed 7 years ago by viewit
- Keywords FEEDBACK removed
Ok. no problem. I assign a keyboard shortcut. you can close the problem
comment:10 Changed 6 years ago by alwin
- Status changed from assigned to closed
- Resolution set to wontfix
