[Design] Auto-Export Collection and Settings Dialog

Mimi Yin mimi at osafoundation.org
Mon Nov 19 17:04:37 PST 2007

Hi Heikki,

My feeling is that the pop-up we have now won't solve the scenarios  
you're describing either.

Presumably, admins and users alike will run into the 'Export'  
instructions when they go to the File>>Upgrade... menu item to check  
to see if a new version of Chandler has been released?

Will we be able to automatically migrate data from version to version  
in the future?


On Nov 19, 2007, at 2:45 PM, Heikki Toivonen wrote:

> Mimi Yin wrote:
>> On Nov 15, 2007, at 3:14 PM, Heikki Toivonen wrote:
>>> Mimi Yin wrote:
>>>> I downloaded the latest end-user trunk build and I noticed the new
>>>> 'Automatically export your collections and settings so you can  
>>>> migrat=
> e'
>>>> dialog. It popped up when I tried to quit Chandler.
>>>> The pop-up felt a little out of place.
>>> I believe that is the safest place for it. And if you check the  
>>> never
>>> ask again box, you won't see that dialog again.
>> =20
>> I'm not confident that we have the user's attention when the  
>> dialog pop=
> s
>> up. It appears out of context. It possible that it pops up before the
>> user has even entered any data.
> You mean a user starts Chandler for the first time (or with fresh  
> repo),
> does not do anything, then quits? I don't think it is such a big  
> deal in
> that case. Or have you seen it in some other situation?
>>>> Perhaps instead, we should change the 'Export Collections and
>>>> Settings...' menu item to an 'Upgrade...' menu item that pops up  
>>>> the
>>>> following dialog:
>>> Unfortunately that won't work as well as the current system;
>>> specifically it breaks in cases where multiple users use the same
>>> Chandler on a system (administrator can upgrade chandler and  
>>> leave use=
> rs
>>> unable to migrate their data). It also breaks in a case where a  
>>> single=
>>> user uses Chandler occasionally, then stops using it for a while,
>>> notices an upgrade and installs it before migrating their old data.
>> =20
>> The 'Your data is incompatible with this version of Chandler' dialog
>> addresses this issue, no?
> No. If there is no old Chandler installation on the computer, you  
> can't
> migrate.
>> I agree that the real solution is automatic updates. A way to prompt
>> users to update when a new version of Chandler is available.
> That does not cover multi-user systems, so it can only be advisory.
> --=20
>   Heikki Toivonen
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design

More information about the Design mailing list