[Erp5-report] r13908 - /erp5/trunk/utils/oood/README

[nobody at svn.erp5.org]

Author: bartek
Date: Tue Apr  3 18:13:22 2007
New Revision: 13908

URL: http://svn.erp5.org?rev=13908&view=rev
Log:
trimmed and updated

Modified:
    erp5/trunk/utils/oood/README

Modified: erp5/trunk/utils/oood/README
URL: http://svn.erp5.org/erp5/trunk/utils/oood/README?rev=13908&r1=13907&r2=13908&view=diff
==============================================================================
--- erp5/trunk/utils/oood/README (original)
+++ erp5/trunk/utils/oood/README Tue Apr  3 18:13:22 2007
@@ -5,19 +5,15 @@
 metadata. To be used together with ERP5 Document business template,
 although can be run standalone for any other client application.
 
-Server tested using OOo 2.0.3, and everything works. Some files created
-in OOo 2.0.2 may crash - this is a known issue. Files created in OOo
-2.0.3 and MS Office normally go through with no problems.
-
 It returns a file in a desired format; html files are zipped because
 they often consist of more than one file.
 
 INSTALLATION:
 
-Patch your SimpleXMLRPCServer.py with this:
-https://sourceforge.net/tracker/?func=detail&atid=305470&aid=893642&group_id=5470
+Refer to http://wiki.erp5.org/HowToUseOood for most up-to-date
+instruction about setting up the environment and installing oood.
 
-Download the source code from svn. Create a writable tmp directory under
+If you install from source, remember to create a writable tmp directory under
 your oood base dir.
 
 SETUP:
@@ -34,28 +30,7 @@
 
 - instance_timeout - when an OOo instance we called does not return for too long, we decide it has crashed; we kill it and start another one. This is the time after which we undertake this drastic action.
 
-SETTING UP OOo INSTANCES
 
-When run, the server starts a configured number of OOo instances as different users (user_0, user_1 etc), each having its own settings. By default, instances are run in "headless" mode (they don't produce visible windows). Initially, the time it takes OOo to load is very long - this is because instances can not find Java. For the first time you may therefore want to start every instance in a "normal" mode (by removing "headless" parameter in start.py) and set up Java path in OOo options - this reduces the required loadtime from about half a minute to a few seconds.
-
-USAGE:
-
-Start your OOo instances by running
-service oood start
-or
-/var/lib/oood/start.py --init
-and when it is finished:
-/var/lib/oood/runserw.py --start
-
-TESTING:
-
-Run testOoodBasicOperations.py to check if it works.
-Run testOoodOldFormats.py to check if older OpenOffice and StarOffice
-formats are really supported. 
-Run testOoodHighLoad.py to see how it performs. This test takes a long
-time to run, and even longer to set up when run for the first time; but
-it does its best to strangle oood. Consult documentation in source code
-for more information.
 
 
 # vi:tw=72 ai ft=txt