Collaboration Workspace tree redesign

[Phillipus]

Aims:

• to have a flexible tree structure of Groups and aliases to Repositories
• to not physically move files and folders around when arranging (drag and drop) the objects in the tree. (The repository files might be open in a process or being updated in the background. It could be a lengthy process moving many git files. If the model is open in Archi it would have to be closed first.)
• A "Group" is virtual in the tree and does not represent a folder on the file system
• A "Repository" is a reference to a folder containing the git repository
• The tree structure is stored in a "repositories.xml" file (similar to Archi's "models.xml" file)

The first version of this asks the user for a folder to store the repository. If we don't want to bother the user with folders then here's another proposal:

• Have a top-level "model-repository" folder as in coArchi 1.
• Each repository exists in a direct sub-folder as in coArchi 1.

User can add virtual Groups in the tree and drag and drop the references to the repo folders to add or remove them from Groups.

But:

We need a sub-folder name for each repository. In coArchi 1 we used the last part of the repo's URL string. But we are now allowing the user to optionally not enter the repo's URL and add it later. So do we:

• ask the user for a sub-folder name in the dialog?
• generate a random sub-folder name?

And there is the question of deleting/removing a tree entry. If a Repository is removed/deleted from the tree is the repo folder also deleted? And if a Group is removed/deleted are all child repos deleted as well?

[Phillipus]

Now:

• The Clone repo and Add model to workspace actions don't ask for a folder. A sub-folder with random UUID name is created in the model-repository folder
• All other behaviour is the same. You can still add other repo folders to the tree if you want to