Bug 312083 - Feature request: background colors for projects
Summary: Feature request: background colors for projects
Status: RESOLVED DUPLICATE of bug 269704
Alias: None
Product: kdevelop
Classification: Applications
Component: UI: IDEAl (show other bugs)
Version: unspecified
Platform: Other All
: NOR wishlist
Target Milestone: 4.3.0
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-22 21:12 UTC by Christian Reiner
Modified: 2013-04-11 14:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Reiner 2012-12-22 21:12:40 UTC
This is the text of a suggestion I filed in the kde forum a long time ago. 
Since the contributions there are mostly ignored I post the text here again. 
it is a feature request, not more, not less. 

I have a number of projects defined in kdevelop. This might be separate applications / libraries, but often also different versions of such, for example different branches. Very often I have to open a file from a project different to the one I am currently working on. Or I am working on two projects at the same time, since they depend on each other (e.g. client and server components). It is a great feature of kdevelop to offer handling several projects at once, however this also leads to confusion: often I confuse which project an open file belongs to, for example when the projects contain files with the same name. Currently the only way to clearly see which project an opened file belongs to is by reading the windows title when having the open file in focus. This is very inconvenient. 

My suggestion: 
Enhance the project options by an optional background color. That color would be used at two places: in the project manager side bar and in the tabs on top of the open files. This would allow an intuitive association of files to their project. 


Reproducible: Always
Comment 1 Aleix Pol 2013-04-11 14:28:11 UTC

*** This bug has been marked as a duplicate of bug 269704 ***