My reply inline:
On Apr 17, 2007, at 1:19 PM, Mimi Yin wrote:
What about just having the pulldown right there?
Publish to Chandler Hub with: | Chandler Desktop | v |
Sure, that's fine. I think my point is to not repeat the word
'Chandler Hub' in the same sentence. I realize it is the same thing,
but I think it sounds odd to me. For example:
[Start using Chandler Hub] or publish to Chandler Hub with: |
Chandler Desktop | v |
Here is a sketch of what I'm thinking: http://wiki.osafoundation.org/
Journal/SignUpForAnAccountForOtherCalendaringClients#GatewayPage
The table of information would change according to the selection.
This sketch may favor the web UI users more because of the workflow
I'm thinking of, but we can modify it so it's more balanced. This is
a sketch and I realize I'm looking at it from the web UI sign up
workflow.
Besides, the table of information is not so much for Chandler desktop
users as it is for iCal, Sunbird & other users wanting to put up
their calendaring information on the server.
If the user is coming from setting up the desktop, it might make
sense to display instructions on what to do next step by step on the
desktop application now that I have a hub account. Opposed to just
displaying the table of information. This is similar to the
instructions you created when we were working on the bookmarkable
URL: http://wiki.osafoundation.org/pub/Journal/
CosmoMagicURLStoryboardsTake2/07Subscribe_with_Chandler_ins.png
I guess what I'm getting at is: To a new user, what's the
difference between Using Chandler Hub and Publishing? Publishing
sounds like a subset of Using?
Well yes, I agree there are different types of uses for Chandler Hub,
publishing being one of them. The three I'm thinking of are:
1. Those who expect to use the web UI after signing up when someone
had sent them a bookmarkable URL.
2. Users who were signing up for an account from the desktop and
would need instructions on how to finish setting up their account on
the desktop.
3. Users who wish to use their own desktop application and just
publish their info on on the server of 'Chandler Hub', and not use
the web UI.
The confusion here might be that I'm focused on the first set of
users and I'm making a separation on the web UI hub use based on the
workflows, even though it's all the same thing.
In addition, I would expect eventually creating an account on the
desktop will be done seamlessly for it's user community. Ideally they
will never have to go to a web site to sign up for an account and see
this page.
We should make it more generic than calendar?
I think that's why originally I stated 'publish (set up) from an
external application'. So now I changed it back in the mock up.
Focusing on the third set users, I'm currently not convinced that
there are other applications that are 'beyond' calendaring which ppl
will use the hub for. Even for feed readers, aren't you just reading
updates on other ppls events? Though understandably, I may be wrong
and ppl will put all sorts of stuff on the hub—I guess we'll just
wait and see once preview is out.
-Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
