Confusing UI Terminology: "Add Shared Directory" #74

Closed
opened 2007-07-01 04:13:29 +00:00 by nejucomo · 3 comments

What does "Add Shared Directory" do?

Is the "Name to place incoming directory" a path on the vdrive or my client's filesystem?

Does "Mount shared directory" create a new mount binding on my client's filesystem?

What does "Add Shared Directory" do? Is the "Name to place incoming directory" a path on the vdrive or my client's filesystem? Does "Mount shared directory" create a new mount binding on my client's filesystem?
nejucomo added the
code
major
defect
0.4.0
labels 2007-07-01 04:13:29 +00:00

good things to fix

Really this is "add URI as a child of the given name", where the URI could either point to a directory or to a single file. I used the words "Add Shared Directory" to match the text at the top of each directory page that offers the URI for that directory, to give people the idea that you cut from one and paste into the other.

"Name to place incoming directory" is a single pathname component (no slashes) and means that we will create a child of the current directory with that name. The child will point to the thing being linked. This is the equivalent of 'cp ... ./Name', or 'ln -s ... ./Name', or 'mount ... ./Name'. This is completely unrelated to the disk-based filesystem of the host on which your client is running.

'Mount shared directory' does not touch the disk-based filesystem of your client's host. It only affects your vdrive.

The only thing which touches the your host's disk is the upload file button.

Now, how to summarize all of these notes into a concise and expressive webish.py directory page.

Also, note that eventually we will have professional web UI designers replace this. webish.py is purely an engineering interface, so I feel it's ok if it requires a bit of engineering explanation to understand completely.

good things to fix Really this is "add URI as a child of the given name", where the URI could either point to a directory or to a single file. I used the words "Add Shared Directory" to match the text at the top of each directory page that offers the URI for that directory, to give people the idea that you cut from one and paste into the other. "Name to place incoming directory" is a single pathname component (no slashes) and means that we will create a child **of the current directory** with that name. The child will point to the thing being linked. This is the equivalent of 'cp ... ./Name', or 'ln -s ... ./Name', or 'mount ... ./Name'. This is completely unrelated to the disk-based filesystem of the host on which your client is running. 'Mount shared directory' does not touch the disk-based filesystem of your client's host. It only affects your vdrive. The only thing which touches the your host's disk is the upload file button. Now, how to summarize all of these notes into a concise and expressive webish.py directory page. Also, note that eventually we will have professional web UI designers replace this. webish.py is purely an engineering interface, so I feel it's ok if it requires a bit of engineering explanation to understand completely.

The current box is labeled "Attach a file or directory (by URI) to this directory", and has two boxes, labeled "New child name:" and "URI of new child:".

Is this any better?

The current box is labeled "Attach a file or directory (by URI) to this directory", and has two boxes, labeled "New child name:" and "URI of new child:". Is this any better?
warner added
minor
and removed
major
labels 2007-07-16 19:21:37 +00:00
warner added
code-frontend-web
and removed
code
labels 2007-08-14 18:56:38 +00:00
warner modified the milestone from 0.5.0 to undecided 2007-08-15 18:31:27 +00:00
Author

The current labels make much more sense to me. After seeing them, the old labels also make sense, but I think these are much easier to comprehend off the bat.

Closing this.

The current labels make much more sense to me. After seeing them, the old labels also make sense, but I think these are much easier to comprehend off the bat. Closing this.
nejucomo added the
fixed
label 2007-08-17 00:53:19 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#74
No description provided.