Right, I think it's going to be tricky to explain the subtleties of
calendaring standards to users.
What I think people will understand is:
+ Subscribing to a share versus Downloading the data onto their hard
drive.
+ Subscribing with one app versus another.
I don't think we should rely on people understanding which protocol
they should subscribe with.
I don't think we should rely on people understanding which file
format they can or can't download.
Outlook for example can't subscribe to CalDAV shares but can
import .ics files and can spit out invitations with .ics files.
Apple iCal could subscribe to Cosmo calendars even though it wasn't a
CalDAV client, correct?
So that brings me back to: what are all the different clients we need
to support?
And where do we put the download file link?
Finally, do we need all of this for 0.6, Preview or Post-Preview.
Adding all of these options will likely make the Subscribe UI /
workflow more complicated. For example, if we do want to have all
these different ways to subscribe and download, we should probably
revisit the original design which had one big fat subscribe button
which took users to a 2nd page where they could figure out what app
they were subscribing with and which URL they needed.
Maybe we could have 1st order buttons for subscribing with Cosmo and
Chandler. And then have a more options button for all the various
other ways you might be able to subscribe, download the event data.
Priscilla has advocated a version of this proposal in the past.
Mimi
On Dec 6, 2006, at 10:51 AM, Ted Leung wrote:
On Dec 6, 2006, at 8:41 AM, Mimi Yin wrote:
Something came out in yesterday's Cosmo Design Session that was a
little worrisome to me so I thought I'd follow up on the list:
What do people think this button means in the mock-ups for
Subscribing to Collections via Cosmo UI? http://
wiki.osafoundation.org/bin/view/Journal/
StrawpersonProposalForMinimumPreviewCosmoUIElements#AlternateSubscrib
e
1. Subscribe to this share with Apple iCal?
If you are on a Mac and know what iCal is, then you might suspect this
2. Subscribe to this share with any CalDAV compliant calendar app?
If so, which ones are we looking to support in Preview?
I doubt that the majority of users would associate iCal with
CalDAV. Most will not even know what CalDAV is.
3. Download the tasks and events in this share as .ics files?
How many people will know what a .ics file is and which
applications might understand one?
1. is the most likely if you are on a Mac, but all of them look
like jibba jabba to the uninitiated.
Ted
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
