Sorry, I am just catching up on some old threads.

I don't think this really is an edge case. I use multiple servers all the time - for demos to help test etc. The default account "Sharing", I change in the accounts setup to "OSAF Server" (or something like that). I agree that "Sharing" isn't a good description and perhaps we should change the default to something else although I don't think we should prevent user's from changing this to whatever is meaningful to them. I will also add new accounts for let's say "Sheila's Server", "Morgen's Server" etc. 

As far as the display in the manage share dialog goes, I have sometimes used this dialog to see what server this share is on. Particularly if there is a sharing error of some kind. I did this just today because I ran Chandler for the first time in a while and had an error icon next to the collection name in the sidebar. I couldn't remember if I had published it or had subscribed to some ticket.

Sheila

On Jun 28, 2006, at 2:21 PM, Ted Leung wrote:


On Jun 27, 2006, at 11:24 AM, Priscilla Chung wrote:

Please see my notes inline:

On Jun 27, 2006, at 10:04 AM, Mimi Yin wrote:

I'm not sure that having the Sharing account in and of itself in the Manage share dialog is inherently confusing. It's there as supplementary information. It doesn't replace the Collection name, which is still the primary way users identify shares. It's simply part of the profile of the share.

Right but why display supplementary (or as I would call it, secondary) information unless the user can do something with it like you can in the 'Accounts' area. Especially, as you said it, the primary way users identify shares is by the collection name. 

Perhaps 'confusing' isn't the correct term, but more like why show additional information that doesn't really help the user? It just ends up 'cluttering' up what you want the user to do, which is to manage his/her collection share. 

It's fine if you don't think it confuses the user. The supplementary information just doesn't seem like it's necessary to the user to identity the collection.

I may be an edge case here, but I currently have calendars from 3 different servers in my Chandler, so account information is useful to me in recalling what came from where.

Ted
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to