strepsirrhini/office-gobmx
9
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

INTEGRATION: CWS chart2mst3 (1.3.4); FILE MERGED

Browse source 
2005/10/07 11:05:57 bm 1.3.4.4: RESYNC: (1.3-1.4); FILE MERGED
2004/04/23 13:55:44 bm 1.3.4.3: remote string for office added
2004/03/25 16:51:30 bm 1.3.4.2: chart2.rdb has to be delivered before running dmake
2004/02/13 16:51:06 bm 1.3.4.1: join from changes on branch bm_post_chart01
This commit is contained in:
Vladimir Glazounov 2007-05-22 15:44:35 +00:00
parent c191733837
commit e233271012
1 changed files with 19 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
chart2/NOTES
View file

@ -4,9 +4,9 @@
#
# $RCSfile: NOTES,v $
#
# $Revision: 1.4 $
# $Revision: 1.5 $
#
# last change: $Author: rt $ $Date: 2005-09-07 23:36:31 $
# last change: $Author: vg $ $Date: 2007-05-22 16:44:35 $
#
# The Contents of this file are made available subject to
# the terms of GNU Lesser General Public License Version 2.1.
@ -50,10 +50,10 @@ HOW-TO:
* Open the file Common.xcu of the Registry.
Location on Unix:
$HOME/StarOffice7/user/registry/data/org/openoffice/Office/Common.xcu
$HOME/StarOffice8/user/registry/data/org/openoffice/Office/Common.xcu
Location on Windows:
"%UserProfile%\Application Data\StarOffice7\user\registry\data\org\openoffice\Office\Common.xcu"
"%UserProfile%\Application Data\StarOffice8\user\registry\data\org\openoffice\Office\Common.xcu"
* Under the configuration-node "Internal" (see <node oor:name="Internal"> tag)
you have to add the property "DevelopmentChart" and set this to "true":
@ -116,4 +116,18 @@ Testing
* You can also create a chart from spreadsheet data.
* To run a test for the old API run "dmake" in the qa subdirectory.
* To run a test for the old API run "dmake" in the qa subdirectory. Note that
you have to deliver the private chart2.rdb (just type "deliver") and call the
workbench/officeintegration/install.pl script for registering the private
Chart API at the global registry in order to run the test. Currently the test
has to use new API, but in the future this will of course no longer be
necessary.
For running the API-test you must have a running office with the correct
parameters that allow remote access from external components (like the API
test). Use the following command-line argument:
"-accept=socket,host=0,port=8100;urp"
With host=0 you allow access only from your local machine, so this should be
no network security problem.