Hi Heikki,
We could do the following:
(Could we have more of a margin around these dialogs? 15 points or
pixels?)
===
Import
-----
File: [ ] [Browse]
-----<IF .ICS FILE IS SELECTED>
Import:
[ ] Event status
[ ] Alarms
Import into: [ New collection | v ]
[ ] Keep out of Dashboard
[Cancel] [Import]
-----<IF .CHEX FILE IS SELECTED>
Warning: xxxxx
[Cancel] [Import]
===
===
Export
-----
Export to:
(x) .chex for re-import into another version of Chandler.
(All data and settings will be exported.)
( ) .ics (iCal format) for re-import into another Calendar
application.
(Only tasks and events will be exported.)
[Cancel] [Export]
===
On Nov 21, 2007, at 11:39 AM, Heikki Toivonen wrote:
Aparna Kadakia wrote:
FWIW, I like Mimi's proposal as she put it in the last email. It's
much
clearer to the user what the outcome of the different actions will
be.
If I am trying to import .chex and .ics, using the same 'Import'
option
for both may not be exactly intuitive to most users.
To me this design below requires users to choose up front WHAT they
want
to import from what FORMATs. I'd argue most users have no clue.
Maybe when exporting you'd need to present the user with a dialog
first
to choose what to export, which will explain/show what format the info
can be exported into. Seems like exporting would be harder to do in an
easy to understand way.
File>>
+ Import>>
++ Import Tasks and Events from .ics File...
++ Reload Chandler Data from .chex File...
+ Export>>
++ Export Tasks and Events to .ics File
++ Export Chandler Data to .chex File
Additionally, suppose you add 10 import/export plugins... Now your
submenu has ballooned to a length of 12.
--
Heikki Toivonen
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
