Paint Your Files to Make Them Stand Out

Posted on by Eugene Toporov

Most definitely you’ve ever created big websites, right? Then you might have opened more than one index.html, index.php files in the editor. How to tell one from another and understand which part of your website they belong to?

WebStorm/PhpStorm help you make files with similar names stand out at a glance: press Ctrl+Alt+S / ⌘ , to open the Settings dialog, and choose File Colors.

First, let’s break our application or project into smaller chunks — scopes. Click Manage Scopes button, and create a scope for each project chunk:

Next, associate each scope with its own color:


Now you will never get lost among the files of your application:


Enjoy! And be sure to let us know if you like this feature.

-JetBrains Team

Comments below can no longer be edited.

4 Responses to Paint Your Files to Make Them Stand Out

  1. MaziLLa says:

    April 8, 2010

    How do this colorization if project has got many content root directories. E.g.:

    project/
        project/
            src/
            tests/
        lib/

    And direcrories src, tests and lib has different colors?

  2. Eugene Toporov says:

    April 13, 2010

    @MaziLLa: you just need to define scopes appropriately. They should allow you to configure what you want.

  3. MaziLLa says:

    April 22, 2010

    Извиняюсь за назойливость, но попробую сформулировать проблемму на родном языке.

    У меня есть папка /www/project/ – это мой проект. И есть папка /www/lib/ – это некие библиотеки. Как видно, lib НЕ является подпапкой для project. Но lib подключен к project через Settings->Directories->Add Content Root.

    При этом, в диалоге создания Scope, когда я выбираю lib и жму на Include Recursively, PhpStorm добавляет в текущий scope обе папки: и lib и project. Pattern: file[project]:*/. То же самое, если нажать Exclude Recursively – исключаются обе папки, но выбрана при этом только одна из них.

    PS. Юзаю билд 95.57.

  4. anet says:

    April 26, 2010

    It is not possible to distinguish content roots now. If you can place your lib in “project_libs” direcory then scope file:lib//* would work. Or you can enumerate your libraries one by one.
    Sorry for the inconvenience