I'm not as opposed to showing globally unique identifiers as you are. I'm also not optimistic about having good, fluid drag-and-drop in a web interface. Doing good, clean drag-and-drop in the web would be a major undertaking.<div>
<br></div><div>That said, a "good user experience" for Tahoe seems to be creeping farther away rather than drawing nearer.</div><div><br></div><div>jody<br clear="all">----<br>- Think carefully.<br>- Contra mundum - "Against the world" (St. Athanasius)<br>
- Credo ut intelliga - "I believe that I may know" (St. Augustin of Hippo)<br>
<br><br><div class="gmail_quote">On Thu, Feb 4, 2010 at 4:50 PM, James A. Donald <span dir="ltr"><<a href="mailto:jamesd@echeque.com">jamesd@echeque.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">Jody Harris wrote:<br>
> Barriers continued....<br>
><br>
> These are comments from my users:<br>
><br>
> (Speaking of command line...) "cryptic they are. They need to move more<br>
> of the functionality into the web gui and do automatical aliasing and show<br>
> that in the web GUI. At least the top and maybe first trees in the<br>
> structure."<br>
><br>
> "...why not include a web app - complete with logins and groups?"<br>
><br>
> "Interesting decision not to include [a web wrapper]...seems an obvious<br>
> oversight?"<br>
><br>
> These users seem to have very little patience for understanding the broader<br>
> context of what tahoe was designed for.<br>
><br>
> Perhaps I'm just trying to roll this out in the context of the wrong users.<br>
<br>
</div></div>I suspect that any user will have similar reactions to a tool that<br>
shoves globally unique identifiers in his face.<br>
<br>
What I interpret these users as requesting, when they ask for a "web<br>
app" or a "web wrapper", that does "automatical aliasing" is a web page<br>
that they can log into (thus obtaining their root capability) and on<br>
that web page they see the "aliases" (petnames, links) for the<br>
capabilities that they have already created, and they can drag and drop<br>
files onto that web page, thereby creating more capabilities,<br>
represented by more "aliases" (user petnames)<br>
<br>
I think "automatical aliasing" may perhaps mean the same thing as I mean<br>
when I say, "never show an end user a globally unique identifier."<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@allmydata.org">tahoe-dev@allmydata.org</a><br>
<a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
</div></div></blockquote></div><br></div>