When working with the project selector (old "recent projects" list) I feel that it's time to make it behave like an ordinary file list, i.e. instead of opening projects with a single click, it should take a double-click. This allows for selecting projects without opening them. I could then enable users to use a wide array of project-specific menu options without first opening the project. This would also allow for select-as-you-type, i.e. to select projects by typing the first few letters in the project's name.

What do you think? Would it backfire with existing users if they now need to double-click (or click+enter) to open projects? One can always make it another option, but I prefer to avoid options if we truly believe this is a better behaviour.

Yes, I can make that available for testing before I implement everything.

Would it be better, or more confusing, if there was a toggle icon(triangle) at the right of the project name field. Clicking on the name selects the project, clicking on the icon opens it.

When making this change, I also plan to use an ordinary List component for presenting the projects (I get a lot of good built-in behaviour that way). This would also imply that the currently opened project would no longer show up in the middle of the list, but would instead be pinned just above the project list. It would then no longer scroll away if you scroll down the list. The only downside by making that change would be that opened projects with many sub folders would consume much vertical space from the rest of the project list. Alternatively, I could allow the currently selected project to "scroll up" along with the project list if the user scrolls down the list, but I think it's better to have it pinned to the top, otherwise I'd need to scroll the list to the top when a user double-clicks to open a project. I think that behaviour would confuse users.

I could enable the collapsing of the opened project folder tree by introducing a root node for it