Dear Aparna:
I like completely the idea of separating in different folders, app to
repository.
Recalling what happened, Chandler crashed (don´t know the reason).
I could not even force quit it.
Don´t remember what exactly did I do but the thing is that I probably
ended with a corrupted repository.
If this is so, wouldn´t it be a nice feature (depending on the size) to
have a BKP repository from the previous session?
The other, the error message has to do with the installation process.
When I do a clean install, one usually forgets that the installation is
already opening Chandler.
So sometimes, I double click Chandlers´ icon and I am opening two
instances of the same program.
This has to do undoubtedly with the opening time discussion.
Some visual clue right at first would do the trick
I hope this info was useful.
Daniel
PS It would be nice instead of saying in the installer that it will
uninstall first to install later, just to say that the installer is
doing a clean install compared to an install like in Mac OS.
For the end user I would prefer that term.
Aparna Kadakia wrote:
Daniel,
The error message you have attached is seen when you have try launching
2 instances of Chandler on the same repository. Our repository now
lives in a different directory than the Chandler install as you have
noticed. On windows the default location is something like :
C:\Documents and Settings\username\Application Data\Open Source
Applications Foundation\Chandler\uIQwZD4O.default
(You can look up more info on profile directory here :
http://wiki.osafoundation.org/bin/view/Projects/ProfileDirectory)
The idea is when you do a fresh install of Chandler it doesn't delete
your repository directory so you could keep installing newer versions
of Chandler to use against the same repository. Since our repository is
still evolving, Chandler might prompt you to refresh the repository
during install and that's something we have decided to live with for
this release.
So the installer did the right thing by not cleaning up the repository
directory..that's by design.
The real confusion is why the installer did not prompt you to refresh
your repository during install and I am wondering if it had anything to
do with repository having been corrupted from a previous use.
On a side note, the installer is being enhanced to deal to with old
installs. That's bug 3191.
http://bugzilla.osafoundation.org/show_bug.cgi?id=3191
Thanks for your feedback,
Aparna
Philippe Bossut wrote:
Hi
Daniel,
Daniel Vareika wrote:
The
solution was:
to delete the folder named "Open Source Aplication Foundation" under
documents and settings and to delete the application itself from the
programs folder.
I thought that was something a clean install was supposed to do.
Hmmm... Looks like something we should be testing again before
releasing 0.6.
Thanks for the feedback, it really helps.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
