Re: [Re-Proposal] Import/Export, Export/Reload Consolidated

Replying to Davor and Heikki together.

I think a single dialog that changes depending on what you've done is  
preferable to 2 separate dialogs that pop-up one after the other. The  
Publish dialog is a good example of this. The user experience is  
pretty smooth.

See more in-line.

On Nov 22, 2007, at 10:33 AM, Davor Cubranic wrote:
> This workflow really looks like it should be done in a wizard. I know
> that this was something that you wanted to avoid, but I think the
> alternative is even worse. Trying to cram all the options into a  
> single
> dialog whose contents change depending on the selected file will only
> make it more confusing for the user to discover the available
> functionality.
>
> Also, if a wizard is used, it becomes much easier for plugins to
> contribute their own import/export functionality -- Eclipse is an
> excellent example of how this could be done. (And perhaps the RSS  
> plugin
> could be used to demonstrate this by importing feeds from a Firefox
> bookmarks file.)
>
> Davor

On Nov 26, 2007, at 10:50 AM, Heikki Toivonen wrote:

> Mimi Yin wrote:
>> ===
>> *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]
>> ===
>
> Why make it this complex? Just launch the native file picker. Then, if
> the suffix was .ics, present the .ics import dialog. There  
> currently is
> no further dialog for .chex import so I see no need to add one now.

Heikki, don't we still need to pop-up a warning dialog when  
reloading .chex files?

>
>> ===
>> *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]
>> ===
>
> I think it is bad to include the suffix in this dialog. I'd say
> something like:
>
> Export:
>
> (*) All data and settings for import into Chandler.
> ( ) Only tasks and events for import into iCalendar.

How about this:

(*) All data and settings for import into Chandler.
( ) Only tasks and events for import into another Calendar application.

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design