5

Hi all,
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.

arkascha

I know this post is a bit old. I however like it.I have a bit different use case, but the feature arkascha is describing is the same.

My use case is CMake superproject with many subprojects (CMake projects called through add_subdirectory from another CMake project).

Colors can be automatically generated (later can be adjusted and stored within KDevelop project configuration).

Anyone interested?

EDIT: Ok, by digging to source code I found WidgetColorizer which then leads me to the Settings=>User Interface=>(Coloring) "Color widgets based on project affiliation".

It did not worked until I cleaned all KDevelop configuration (*kdev*) files in my home folder.

It works for "standard" and also for "cmake" based projects.

Unfortunately it does not work on CMake sub-projects as described in my use-case above.