On 1 Oct, 2008, at 14:16, Jeffrey Harris wrote:
Hi Mimi,
I beefed up the troubleshooting directions for how to use the
change_tz.py file. Jeffrey or Grant, could you take a look to make
sure
I didn't get something completely wrong.
I know the instructions can be more generic, but I wanted them to be
understandable by someone who has never done stuff in the command
line
before.
http://chandlerproject.org/Projects/TroubleshootChandler#(UTC)%20Events%20I%20imported%20show%20up
c:\programs\chandler won't work on Windows. Something like:
c:\progra~1\chandler1.0
might work for 1.0 versions of Chandler. You've also got a spurious
extra space between the directory and the filename, which is liable to
confuse people.
Hmm ...
1) Not all windows keyboards have a windows button (e.g. my thinkpad
doesn't). It might be better to say to use the "Run..." item in the
Start menu.
2) In that case, I can enter C:\Program Files\Chandler\release
\RunPython.bat to run Chandler 1.0.x's python. (A long time ago, I
changed my install path to be Chandler, not Chandler + version; unless
you change it yourself, the windows installer will forever install
into the directory you first installed into).
3) Note that the above RunPython is in the release dir, not release\bin.
4) The c:\progra1~ business is using DOS-style path mangling; I'm not
sure if that is consistent across machines. I also don't think it's
necessary in general(?); it certainly isn't for me.
5) The Mac instructions won't work unless you have vobject installed
into your system python (Most people won't, I'd guess). Instead of
"python" in the instructions, it should be something like:
/Applications/Chandler.app/Contents/Resources/release/RunPython
(depending on where you put your Chandler.app, and what you named it).
--Grant
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
