Good work, alexk!
One little side note, though:
the project directory structure I proposed was only an example, to allow users to specify their own directory structure. There should probably be just one base path, in which the user can make subdirectories to their own wishes, and save his files in any of the subdirectories, or subdirectories of the subdirectories. Because there is generally no way of knowing how they set up the structure of their project. Many people like their directory structure to reflect the structure of their project. For example, if the project is part of a bigger project. (eg: a project with several sub-projects). A directory structure could look like this:
Server and client would be two separate projects, and "common" would be code shared between both the server and the client (this is a very common approach). The project-file of both the server and the client would have to be able to include the common source into their project.
It would probably be possible as it is now, by making the common code a separate project as well, but in the real world this is a bit impractical.
I guess my point just is, that the directory structure shouldn't be hard-coded but completely up to the user. And the IDE should be able to handle whatever the user makes his directory structure like, for example by showing separate folders in the project-tree, representing the user-created subdirectories.