I do agree that manual migration is annoying. Trying to read an old repo
is a good idea. Saving a .chex on quit however struck me as too much
(it's really slow on my machine), borderline weird (why do we have a
persistence repo if we need to double back with a chex?) I know why we
do this but I'm sure that most users are going to look at that as
downright bizarre.
That being said, I do not have a better idea...
Cheers,
- Philippe
Heikki Toivonen wrote:
The manual migration really grates on me. It is an expectation in modern
day software that migration happens automatically. So what could we do?
I noticed that when we released 0.7.1, it was actually compatible with
0.7.0.1 data, so there would have been no need for migration. This
probably won't happen often, but it is possible with short release
cycles. I think we should change the Chandler startup such that if
Chandler does not find a repository where it expects one to be (like no
0.7.2 profile dir), it could check for prior profile dirs first and try
to open the latest of those. If it opened fine, great. If it raised a
schema error, we'd need to do something else.
We could also make it an option to have Chandler automatically export a
.chex file when quitting. This takes quite a bit of time, though, so we
should ask the first time the user is quitting if they would like to do
this. At that point we could tell them that this would automate
upgrading; otherwise they would need to follow the manual migration
instructions. Assuming the user was automatically exporting a .chex file
(in their profile dir), chandler startup code could check for the
existence of the .chex file and load from there. If it could not find
the .chex file, the migration dialog could have an option for the user
to specify it manually.
Thoughts?
------------------------------------------------------------------------
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
