|
OpenOffice2_3_workaround
This page describe steps needed to proper work of older AddOn versions with !OOo 2.3. Instead of read how to make older versions work you better download newest possible version of AddOn from here In OpenOffice.org 2.3 AddOn doesn't work after simple installing of OXT file. Until more comfortable solution won't be available pleas use this workaround. Install AddOn (from here) Download file libs.zip and extract it into some directory (assume that it will be (under Windows) C:\Program Files\GDOCS\), after this you should have in this directory files:
Start OpenOffice.org Writer. From menu choose Tools -> Options -> Java -> Class Path. Add all files from libs.zip to Class Path (as a result you should see 4 JAR files in Window with Class Path). Click OK and OK, and restart OpenOffice.org (you must also exit from Quickstarter). After this start again OpenOffice.org, everything should works well. Here you may find presentation describing whole process of workaround - presentation hosted on Google Docs |
Sign in to add a comment
I followed the workaround in windows Vista, still the same message, sorry!
Can you verify if you have had 4 JARs on ClassPath as shown on Page 10 of this presentation?
Hi Przemelek,
I would like to thank you sincerely for creating such a useful add-on for those of us who use both OO and Google Docs. THANK YOU! with this workaround it works perfectly on XP.
In the future I can see value in continuing to enhance this. Perhaps Google could pick this up and keep developing it. Nice features in the future would be for it to update a document already uploaded etc, etc.
Thank you again!
Kurt
Fix worked after noticing that quick start was on and switched it off accordingly.
Is the password to the account encrypted and secure when stored on the client machine and when interacting the web service?
This workaround isn't needed from version 0.5 or even lower, please go to http://code.google.com/p/ooo2gd/downloads/list and get newest version of AddOn?.
@fromtony: user login and password are encrypted, but its encoded by very easy algorithm, it's rather secure to keep encoded in this way credentials on machine used only by you, but you should consider it if you use shared computer. Some transitions over network are made by HTTPS secured? some by HTTP, I'm not sure but I suppose that login process credentials are sent via network? base on HTTPS.