[Design] [Cosmo] [Bug 8081] New: account setup information in signup dialog possibly incorrect or in need of reorganization

[Mimi Yin]

Forwarding to the list to discuss design options there...See below  
for questions.

Begin forwarded message:

> From: bug-comment at osafoundation.org
> Date: February 12, 2007 11:03:52 AM PST
> To: mimi at osafoundation.org
> Subject: [Bug 8081]  New: account setup information in signup  
> dialog possibly incorrect or in need of reorganization
>
> http://bugzilla.osafoundation.org/show_bug.cgi?id=8081
>
>            Summary: account setup information in signup dialog  
> possibly
>                     incorrect or in need of reorganization
>            Product: Cosmo
>            Version: 0.6.1
>           Platform: All
>         OS/Version: All
>             Status: NEW
>           Severity: normal
>           Priority: P3
>          Component: UI Design
>         AssignedTo: priscilla at osafoundation.org
>         ReportedBy: bcm at osafoundation.org
>
>
> when the signup dialog is used to create an account, it displays a  
> table of
> information used to set up sharing accounts in client applications.  
> this table
> includes "path" and "full URL". in 0.6.1 these indicate the dav  
> path/URL of the
> account's home collection. it's not clear if these two fields are  
> useful
> anymore.
>
> preview chandler will not use either of these infos; it will get  
> any protocol
> information it needs out of the user's USD.

USD?

>
> the situation is more complicated for caldav users. as we've seen  
> in the past,
> users often try to plug their dav home collection url (the one  
> labeled "full
> URL" in the signup dialog) into their caldav program, thinking the  
> home
> collection is actually a calendar, when it's not. the right  
> solution for caldav
> users is probably to autocreate a calendar and display the url to  
> that.

What are the other URL options? Is this in the Account Browser? I  
wasn't able to find the 'full URL'.

>
> the signup dialog should probably provide or at least link to
> application-specific instructions for client setup. if these  
> instructions are
> to be dynamic in any way (for example, using the account's  
> username, the
> server's host and port, etc), then this probably requires auto- 
> login on
> successful signup.

This is in regards to how to configure your client in order to  
publish and subscribe from there, as opposed to signing up for an  
account to use the web app. I understand there's no real technical  
difference because people can both, but users will be coming to the  
Sign-up UI with potentially very different expectations and goals for  
what they can do.

I'm not following the last sentence? If the instructions are dynamic?  
as in different instructions for different clients? Not following why  
this requires auto-login. How would auto-login interact with email  
confirmation?

Mimi


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20070215/c58172b0/attachment.html