[Erp5-report] r14633 - in /erp5/trunk/utils/oood: MAINTAINERS.txt README

[nobody at svn.erp5.org]

Author: bartek
Date: Mon May 28 15:39:36 2007
New Revision: 14633

URL: http://svn.erp5.org?rev=14633&view=rev
Log:
Updated README

Modified:
    erp5/trunk/utils/oood/MAINTAINERS.txt
    erp5/trunk/utils/oood/README

Modified: erp5/trunk/utils/oood/MAINTAINERS.txt
URL: http://svn.erp5.org/erp5/trunk/utils/oood/MAINTAINERS.txt?rev=14633&r1=14632&r2=14633&view=diff
==============================================================================
--- erp5/trunk/utils/oood/MAINTAINERS.txt (original)
+++ erp5/trunk/utils/oood/MAINTAINERS.txt Mon May 28 15:39:36 2007
@@ -1,1 +1,1 @@
-bartek
+Bartlomiej Gorny <bartek at erp5.pl>

Modified: erp5/trunk/utils/oood/README
URL: http://svn.erp5.org/erp5/trunk/utils/oood/README?rev=14633&r1=14632&r2=14633&view=diff
==============================================================================
--- erp5/trunk/utils/oood/README (original)
+++ erp5/trunk/utils/oood/README Mon May 28 15:39:36 2007
@@ -1,31 +1,9 @@
-NEWS
-
-April 21, 2007
-The Dispatcher is basically working - it passes
-testOoodBasicOperations.py and survives if worker is destroyed manually
-and if OOo instance is killed. However, there is still a long way to go.
-To use the new implementation, set "implementation" in config.py to 2
-(default is 1). Backward compatibility is maintained. If you use
-implementation 2, there is no need to run start.py --init, OOo instances
-are started by the daemon.
-
-April 18th, 2007
-New method "printDocument" - prints the given document directly from the
-daemon's OOo instance, so if the printer is available for the serwer,
-the doc does not need to be converted and returned to be printed.
-
-
-April 11th, 2007
-The request handling part is going to be rewritten completely - the
-serw. Procesor class will be replaced by Dispatcher, which will be the
-only handler for timeouts and exceptions.
-
 DESCRIPTION
 
 A server for converting docs from other formats to OOo, generating pdf
-files, keeping unchangeable snapshots in pdf format, getting and setting
-metadata. To be used together with ERP5 Document business template,
-although can be run standalone for any other client application.
+files, , getting and setting metadata. To be used together with ERP5
+system for generating reports and converting documents for DMS, although
+can be run standalone for any other client application.
 
 It returns a file in a desired format; html files are zipped because
 they often consist of more than one file.
@@ -37,7 +15,10 @@
 A combination of Python 2.5 and OpenOffice 2.1 does NOT work because of
 incompatibility of pyuno.
 
-INSTALLATION:
+A combination of Python 2.5 and OpenOffice 2.2 should work, but is not
+fully tested yet.
+
+INSTALLATION AND SETUP
 
 Refer to http://wiki.erp5.org/HowToUseOood for most up-to-date
 instruction about setting up the environment and installing oood.
@@ -45,15 +26,11 @@
 If you install from source, remember to create a writable tmp directory
 under your oood base dir.
 
-SETUP:
-
-Done in config.py. Important parts are:
+Setup is done in oood.conf. Important parts are:
 
 - server_host, server_port
 
 - paths to programs
-
-- pool_size - how many OpenOffice instances you want to start
 
 - instance_load_time - how long it takes for your machine to load an OOo
   instance; this is important because when it is restarted, a script
@@ -65,6 +42,20 @@
   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.
 
+- file formats which you want to use, or which you want to hide; it
+  doesn't affect the abilities of oood, only limits the list of allwed
+  conversion target formats, which is rather long and contains many
+  formats you may never need
+
+USAGE
+
+Refer to the /samples directory for examples of client usage in various
+programming languages:
+
+- Python
+- PHP
+- Java
+- C++