Label / Name of workspace in file browser

[JuergeN]

As a user I find it confusing that the directory that is created for each workspace is not labeled / named as the workspace, but as the workspace-id. As ist has a path and a name, why can't the name on the canvas (not the filepath!) just equal the workspace name?

[jri]

The label of a Folder topic as displayed on the canvas is always the name of the underlying directory.

The per-workspace root directories are named according to the workspace ID, and not the workspace name, because

• A workspace name may change. As a consequence the per-workspace root directory must be renamed then. A published URL to a workspace repo file would break then.
• Workspace names are not forced to be unique. On the other hand the names of the per-workspace root directories must be unique.

Yes, making the workspace ID visible on the canvas is not nice as it is not informative to the user.
I worked hard with implementing another solution but I got into devils kitchen. At the moment I know no better solution.

[jri]

Replying to jri:

The label of a Folder topic as displayed on the canvas is always the name of the underlying directory.

Aah, only now I understand what you mean: A Folder topic has a "Folder Name" and a "Path". The Folder Name must not be strictly derived from the Path but could have a programmatic value. Sounds reasonable :-)

[JuergeN]

Replying to jri:

Aah, only now I understand what you mean: A Folder topic has a "Folder Name" and a "Path". The Folder Name must not be strictly derived from the Path but could have a programmatic value. Sounds reasonable :-)

Exactly! :)

[Jörg Richter <jri@…>]

In e0efa872ee15111144d6a29ed652bca61b92ac79/deepamehta:

Files: use workspace name as Folder Name (#850).

A Folder topic that represents a workspace root directory uses the workspace name as Folder Name.
This is more intuitive as the workspace ID have no meaning to the user.

This applies only if per-workspace file repos are activated, that is:

dm4.filerepo.per_workspace=true

A migration that transforms existing Folder topics is provided.

Thank you, JuergeN, for coming up with this usability improvement!
:-)

See #850.