Independent Projects

[bkonia]

Presently, all projects share the common desktop ancestor and are therefore related to one another in many ways. For instance, if you add a proxy object, it allows you to proxy any object from any project. Also, when you setup resource types, locations, etc... this is done globally in the application preferences; there's no way to configure this individually for each project.

In the case where the projects are actually related to one another, this is beneficial. However, there are many use cases in which the projects have nothing to do with one another. For example, a user might be managing projects for multiple clients in different companies. Therefore, I'd like to propose that you replicate all the global settings, into the top-level project folder. So items like those mentioned above, can be configured either globally for all projects, or individually for each project. Additionally, within each project, you should be able to specify whether to display the entire hierarchy of all projects, or to start the hierarchy display at the project's top level.

I realize that the concept of a "project" in inShort is currently for the sake of convenience and that projects are really just folders, so currently, there's nothing special about the top-level projects. My proposal is that you treat these top-level projects as actual projects that have their own settings independent of the application settings.

[shortki]

The inShort application is suited for personal use, so it is initially assumed that all projects considered have something in common — the user.
Therefore, the context of execution of all projects and the shared resources are of common nature and are separated only by the boundaries of the folders.
In principle, it is possible to provide a filter that will show the resources used by a particular project, as it is done in workflow.link, it may partially solve your problem.