This is why I mentioned:
All OS's have the potential for multiple users running Chandler, so
we should be scanning all of /home/*/.chandler, or wherever the
default location for user data is.
To be clear, that means searching for Chandler data in the standard
location for every user on the machine. For user "xxx", on a Mac that
would be "/Users/xxx/Library/Application\ Support/Open\ Source\
Applications\ Foundation/Chandler", while on Windows it's something
like "C:\Documents and Settings\xxx\Application Data\Open Source
Applications Foundation\Chandler", while on Ubuntu, it's "/home/
xxx/.chandler".
Reid
On Oct 20, 2007, at 8:11, Mike Dawson wrote:
Another scenario where migration of user data is necessary:
* The Chandler Desktop installation is managed centrally by a
network administrator.
* 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.
Mike
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
