Bug 84135 - CVS Resource History should indicate which file is checked out
Summary: CVS Resource History should indicate which file is checked out
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-02-01 09:47 EST by Dani Megert CLA
Modified: 2006-06-20 08:33 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2005-02-01 09:47:55 EST
I20050201-0800

When I open the CVS Resource History view (or use linking) it show the current
file with * in fron and bold but I cannot see which version of the file is
actually checked out into my workspace (or if it even is in my workspace).

We could indicate the selected file in bold and the checked out one with a *.
Comment 1 Michael Valenta CLA 2005-02-01 10:03:19 EST
The resource history view does show the checked out version of a file in bold 
and with an asterix (or at least it is supposed to). Are you not seeing this? 
If so, you will need to provide the steps to reproduce, because this works for 
me (or perhaps I am misunderstaning what you are saying, in which case, please 
clearify). 
Comment 2 Dani Megert CLA 2005-02-01 10:12:29 EST
1. open the resource history for a file
2. enable linking
3. double-click on a different revision
==> the resource history updates and marks the opened bold with *
Comment 3 Michael Valenta CLA 2005-02-07 14:11:49 EST
Unfortunately, there are a coupld of things that make this impractical:

1) There can be multiple local copies of a file
2) If the history view is opened on a remote file, finding the local one would 
require a complete traversal of al projects mapped to that repository as it is 
possible to configure local workspaces to be rearrangements of the remote 
structure.
Comment 4 Dani Megert CLA 2005-02-08 03:09:04 EST
Of course I agree with scenario 1) but for me the 80% use case where I'm
interested in that info is either having a local file open (==> info is known)
or looking at an outgoing/incoming change (==> local info is know too).

In comment 1 you wrote:
The resource history view does show the checked out version of a file in bold 
and with an asterix (or at least it is supposed to).

;-)

Please reconsider.
Comment 5 Dani Megert CLA 2005-08-18 06:35:01 EDT
Here's a simpler solution that would fit most needs: what selecting the revision
that was selected to feed the view (i.e. the input)?
Comment 6 Michael Valenta CLA 2005-08-18 09:22:16 EDT
OK, that makes sense to me. Just to summarize:

- if a local file is used to populate the history view, it should remain 
highlighted with the * indicating that it is the local copy in you workspace

- as other versions are opened, the bolded revision would indicate the version 
that is in the active editor

An additional behavior could be that the asterix only appears when the view is 
seeded by a local file or if a local file is contained in the active editor 
(to cover the case where the file may be in twp projects).
Comment 7 Dani Megert CLA 2005-08-18 09:40:35 EDT
Just to clarify whether I understood it correctly:
- currently * and bold always denote the same entry, right? This would be changed
  so that * would mark the local file if it was used to seed the view. I like
  the additional behavior mentioned in comment 6.
  
>- as other versions are opened, the bolded revision would indicate the version 
>that is in the active editor
Yes if opened from the CVS History view; the * remains with the local file.

In addition, if editor tracking is enabled, it should be smart enough to handle
switching between local file and versions of that same local file i.e. not start
to seed the input from scratch.
Comment 8 Michael Valenta CLA 2006-06-19 13:41:36 EDT
In 3.2, the * now tracks the last local copy that was used to populate the view and uses selection to idnciate the revision for the active editor or selection.
Comment 9 Dani Megert CLA 2006-06-20 04:25:53 EDT
It now fits most of my needs. The only scenario that's a bit strange is when the input itself is a revision and then this revision gets a (*). Maybe we could put the (*) only if the input is in the workspace.
Comment 10 Michael Valenta CLA 2006-06-20 08:15:33 EDT
Makes sense. Could you open a new enhancement request for that?
Comment 11 Dani Megert CLA 2006-06-20 08:33:12 EDT
Sure, it's bug 147857.