Community
Participate
Working Groups
I typically work on multiple branches at the same time often to back port files. It is possible to get confused with which project the file you are currently editing belongs since the navigator window is very large for both projects when one is open the other is not visible nor is the top level of the project so you have to scroll up to see. One way to solve this would be to allow users to define colors on a per project basis. Perhaps having the file open tab a different color dependant on the project that file is associated with. Eclipse is the best IDE !!! Keep up the awesome work.
With "file open tab" are you refering to the editor tab that shows the file name? When you hover the mouse over the tab a tool tip shows the full path including project name. Would it be sufficient if the editor tab tool tip showed a fully decorated label, i.e., including the CVS label decorator if you have it enabled in the preferences? This would allow you to configure the amount and type of information displayed.
Yeah I am talking about the editor tab. I did notice the hovering with tool tip but I wanted something I didn't have to work for, such as a color differentiation. I am not sure the decorators would make a difference. If I am just looking at the two files, one in each project - where each project is a different branch, both are under revision control and I could be editing both of them. So I am not sure how the decorators would help me? Can I configure decorators on a per project basis now?
How do you check out the same project from different streams? Do you check it out and use a different name ("checkout as")? I was thinking we could show the CVS decorated name in the editor tab hover but I don't see how you can have the same project from different streams in one workspace.
Yeah the normal workflow is to work on the trunk in cvs. As with most s/w companies we release versions of our products and we have people working on different versions at different times and often multiple versions at the same time. So if we are working on 3.0 as the trunk then 2.0 and 1.0 are both branches off the cvs tree. Now if we identify a problem in 2.0 which needs to be fixed and 2.0 and 3.0 are recently branched then I first fix the problem in the trunk which is the project named "product". I then test and back port to the project which was checked out as "product-codename[2.0]" based on the branch tag. In which case I have two copies of the same file open trunk-file1 and codename-file1 both with the same name and both potentially modified. Hope that makes sense.
Distinguishing files with the same name is a problem in general and not really specific to CVS branches. I've had other scenarios where I had two files open with the same name in different projects. I'm not sure I like the color coding per project approach though. I would like to see something automatic that doesn't require any action on my part. Perhaps the full path could be displayed in the status line when the editor has focus. Just like it's done in the Navigator and Package Explorer. This is an editor management or editors issue.
Just saw that Simon now owns editor management
We have no plans for release 3.0 to address this particular issue. We will be looking into editor management in general, but it will probably not address your specific corcerns. Using only colour is a problem for people who are colour blind or have a disability that affects their vision. If you want, you can fix this problem yourself and provide a patch to the UI team. You would need to let us know your are interested in doing this by annotating this bug report. You could work with the community to determine the scope of the problem that needs to be address (i.e use cases), and come up with a proposal on how it could be solved (may include more than one solution). Then annotate this bug report again and post to the platform-ui-dev. Once you get the go ahead from the ui team, you could implement the solution and provide a patch (maybe someone else in the community will want to help with the coding)
I'd like to consider this as a duplicate of Bug 19812. Please append your comments there. *** This bug has been marked as a duplicate of 19812 ***
