Confusing/cumbersome root path link in vdrive web view. #77

Closed
opened 2007-07-01 04:47:23 +00:00 by nejucomo · 2 comments

The path display in the vdrive web interface contains a link to each ancestor in a given path.

Yet the root link (always the first slash) returns to the main client page whereas I expected it to point to "$CLIENT_URL/global_vdrive/" for consistency.

Also, a single slash is a very small area to click, perhaps this could be replaced with "/" or something similar.

The path display in the vdrive web interface contains a link to each ancestor in a given path. Yet the root link (always the first slash) returns to the main client page whereas I expected it to point to "$CLIENT_URL/global_vdrive/" for consistency. Also, a single slash is a very small area to click, perhaps this could be replaced with "<root>/" or something similar.
nejucomo added the
code
minor
defect
0.4.0
labels 2007-07-01 04:47:23 +00:00

yeah, that first-slash thing is a bug.. I threw in the ancestor links just before the release, and didn't notice that one.

I kind of like the idea, although the question is which is more important: to be able to jump to the root directory in a single click, or to have that /foo/bar/blah.txt string be cut-and-pasteable into the upcoming command-line interface.

yeah, that first-slash thing is a bug.. I threw in the ancestor links just before the release, and didn't notice that one. I kind of like the <root> idea, although the question is which is more important: to be able to jump to the root directory in a single click, or to have that /foo/bar/blah.txt string be cut-and-pasteable into the upcoming command-line interface.

This one has been fixed with the new source:docs/webapi.txt -based web page. Now the first component of that path line is either or , and I think I fixed the bug too.

This one has been fixed with the new source:docs/webapi.txt -based web page. Now the first component of that path line is either <global> or <private>, and I think I fixed the bug too.
warner added the
fixed
label 2007-07-11 22:28:39 +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#77
No description provided.