Better (mostly visual) support for multiple paths

[mehcode]

• [ ] Adding/Removing a path to a project makes a new project with the current path set joined with the new path. It leaves the old project in the project finder.

This is intended behavior in the state store of atom (as states are keyed by the path array). This is not necessarily a bad thing for crash restore.. but it's a bit odd.

Still mulling about how to fix this nicely. My current idea is to add a listener to when a path gets added/removed to the project and archive the old state. This would mean it still exists for atom (and crash restore) but it wouldn't exist for the finder. We could add a property to the project state ("+archive": true perhaps).

---

• [x] Projects that share paths could look similar in finder. The finder just uses project.paths[0] for the visual part of it.

We should at least indicate that it contains multiple projects in the primary title.

[mehcode]

Would love some ideas on how to make the finder look nice for multi-path projects.

[VincentGuinaudeau]

Here is one idea.

In order to keep the simplicity of the display, you add a little indicator like "(and N more)" on the right of the basepath. If the user want to see the full list of path, a command (bind to the right arrow ?) will expand the tile to display all the paths. A tree view could be use to improve readability.