Ticket #114 (closed: fixed)
Blame-Window: Enhancements
| Reported by: | DHauptmann | Owned by: | alwin |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11.x |
| Component: | All | Version: | |
| Severity: | feature | Keywords: | RESOLVED |
| Cc: |
Description
In the blame window I am very interested in the following features
- Tooltips (or as an extra column?) for commit-messages (when hoovering on the revision number) (as in cervisia)
- Color-codes for 'same' revision numbers instead of altenating the color every line. From dark to light for the distance of the revision to the current revision or the selected line in the table.
- New column with change date/time
advanced feature: Slider to change to another revision
Attachments
Change History
comment:1 Changed 7 years ago by DHauptmann
- Owner changed from anonymous to alwin
- Status changed from new to assigned
comment:2 Changed 7 years ago by alwin
Well, I have no cervisia with that feature, so I can not see what you mean.
tooltips
possible, but may cost a lot traffic. The log information will not come with blame so I have to get them extra. but is a reason more for implementing a local log-cache.
Color-codes
Hm. May take a while longer.
Slider
What do you mean with that? Blame is always a range, mostly start -> head. The Peg-revision? Eg., annotate from start to peg? Well, I'm not sure if this is a good idea, the blame must calculate and transfered always when this range and peg is changed. And this is not a just in time operation simply filter out not wanted revisions (if other programs do something like that, be sure - the result is wrong) In that case it is better retrieving a new blame from within the logwindow as you wished in #0000113
comment:3 Changed 7 years ago by DHauptmann
local log-cache.
without the log message the blame window in my opinion is pretty useless. This is a general svn issue (see 'svn blame')
slider
Just as an easy way to jump between revisions. but I think it is not easy to implement. Perforce does it but may have a much faster way to access all the neccessary information from the backend.
other badly needed features are:
- Syntax highlighting (switchable) in the blame window. QTextEdit has facilities to do this... (see alse kate)
- 'Goto line' input field
- Line number column
- 'Search text' input field
comment:4 Changed 7 years ago by DHauptmann
By the way: slider and color codes are just an idea. The other request are very important for us.
comment:5 Changed 7 years ago by alwin
Syntax-highlighting?
For that kdesvn has to know something about the content. But it doesn't. And simply taking the highlighting-modules from kate or such will not work (in fact the current display isn't a textdisplay anymore).
So this moment I have no idea for that.
