[Chandler-dev] Improving the migration experience
mdawson at totton.ac.uk
Sat Oct 20 05:11:10 PDT 2007
Another scenario where migration of user data is necessary:
* The Chandler Desktop installation is managed centrally by a network
* Chandler Desktop user data could be on any workstation or network
drive. The application administrator doesn't necessarily have access to
it, even if they know the location.
In this case the migration has to be checked for and take place at
run-time. It's also the kind of situation where you're likely to have
the least tech savvy users.
If the migration process does have to be separate though, perhaps it
would be nice if it were possible to run it at the start of a script
which launches the app, with enough configuration possible by the
administrator to avoid frightening the user.
More information about the chandler-dev