I'd also like to add that while providing instructions on how to
subscribe in various applications with the various formats can be really
nice for the user, it takes dedication to keep that info up-to-date as
the apps change where stuff is located, what formats they support, and
what degree of support they offer.
This is the main reason I said I'm kind of uneasy about calling out
specific apps like that. When stuff changes, the instructions we offer
are then actually wrong (for the people with the new version only, of
course). I prefer having no information to having incorrect information.
If we have someone whose responsibility it is to keep that stuff
up-to-date, fine -- or if it ultimately points to some sort of
community-maintained documentation, all the better. But I have seen
multiple cases where an app-/version-specific help system like that gets
built, and then rots.
Priscilla Chung wrote:
=====
Collection name: [xxxxxxxxxxxxxxx] [Bookmark this]
----------------------------------------------------------------------
Subscribe with Chandler --> Dialog expands to display the following -
Copy and Paste this URL to the Collection>>Subscribe... menu item in
Chandler:
URL: [xxxxxxxxxxxxx] [Copy to Clipboard] [Help]
Subscribe with iCal2x --> Dialog expands to display the following -
Copy and Paste this URL to the Calendar>>Subscribe... menu item in iCal:
URL: [xxxxxxxxxxxxx] *[Subscribe]* [Copy to Clipboard] [Help]
Subscribe with Feed Reader --> Dialog expands to display the following -
URL: [xxxxxxxxxxxxx] *[Subscribe]* [Copy to Clipboard] [Help]
Download calendar and tasks --> *Downloads .ics file to Desktop*
*
*
*Other --> *Displays the following in the dialog -
Find out which protocols your application supports and subscribe with
the appropriate URL:
CalDAV: [xxxxxxxxxxxxx]
WebCal: [xxxxxxxxxxxxx]
Atom: [xxxxxxxxxxxxx]
=====
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
