On Sep 19, 2007, at 10:30 AM, Brian Moseley wrote:
but oh no, that's a mc url, which looks slightly different than 1) the
pim url with ticket (#2 above) that the desktop gives you as the
"chandler sharing" url and 2) the same pim url with ticket that the
web ui would give you if you were looking at the web ui in ticket view
rather than logged-in view.
i disagree that this is confusing - how many regular non-geek people
actually try to understand what the components of a url signify? - but
as a thought exercise, i'll accept that it is to somebody.
It's not so much that users will be confused because they notice that
the /pim/ and /mc/ URLs are different. It's more that it's confusing
that the URL they use to subscribe to a share from Chandler Desktop
is different than the URL they might give a friend to subscribe to
the same share from Chandler Desktop.
but if we can't live in the real world, then i suppose i'd prefer
option B - web ui provides a ticketed pim url, desktop uses that to
find the ticketed mc url and then drops the ticket from the mc url.
ideally we'd add the single-ticket limitation so the web ui doesn't
have to make any choices about which ticket to use, but if we can't do
that either, then the web ui could choose the first ticket with read
privilege it finds for the item.
Yes, this approach sounds like it would support the kind of workflow
experience I was describing.
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
