[Chandler-dev] Improving the migration experience

[D John Anderson]

+1

I think we all agreed that this is how we wanted it to work, however,  
it was deemed too too much work for the time we had to implement it.  
Perhaps now that we have more time we can fix it.

John

On Oct 19, 2007, at 2:47 PM, Reid Ellis wrote:

> Ideally, Chandler would check for updates, and when it finds there  
> is one:
> * ask the user if they want to upgrade
> * if so, the new Chandler is downloaded
> * data is backed up
> * the new Chandler launched with flags(?) to load the backed-up data.
>
> That's how most of my apps self-update.
>
> Reid
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev