Aparna Kadakia wrote: > I think having the ics or icalendar or iCal notation in the above menu > items might help users understand what format the export and import > deals with. Especially for people looking for ics compatibility. To > tell you about my experience when I first experimented with Google > calendar, one of the first things I wanted to try was import my ics > calendar into Google. Even though the link says "Import Calendar" as > soon as you are on that screen, it says "Choose the file that contains > your events. Google Calendar can import event information in iCal or CSV > (MS Outlook) format." > I knew I was in the right place. Just saying "Import/Export Tasks and > Events.." might confuse the users since the subsequent dialog doesn't > explain what format it takes.
What if we provided just Import... and Export... menu items, and determined the type of import automatically from file extension (default suffix mask should contain all defaults we support, other options to limit by type, and of course the * option)? For ics we can then pop up the warning that this will only do the job for tasks and events. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
