This is an automated email from the ASF dual-hosted git repository.
mseidel pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
The following commit(s) were added to refs/heads/main by this push:
new abc4a64 Updated page and one link
abc4a64 is described below
commit abc4a645ebbdbc22c6e6a2216eaf5daf27dcb9e6
Author: mseidel <msei...@apache.org>
AuthorDate: Tue May 4 17:19:52 2021 +0200
Updated page and one link
---
.../scripting/scriptingf1/developer-guide.html | 59 +++++++++++-----------
1 file changed, 29 insertions(+), 30 deletions(-)
diff --git a/content/framework/scripting/scriptingf1/developer-guide.html
b/content/framework/scripting/scriptingf1/developer-guide.html
index 4900524..f7a3a56 100644
--- a/content/framework/scripting/scriptingf1/developer-guide.html
+++ b/content/framework/scripting/scriptingf1/developer-guide.html
@@ -26,11 +26,11 @@
<p><a href="#java">Hello World in Java</a> </p>
</li>
<li>
- <p><a href="#context">Writing OpenOffice.org Scripts and the XScriptContext
+ <p><a href="#context">Writing OpenOffice Scripts and the XScriptContext
type</a> </p>
</li>
<li>
- <p><a href="#tips">Tips on writing OpenOffice.org scripts</a> </p>
+ <p><a href="#tips">Tips on writing OpenOffice scripts</a> </p>
</li>
<li>
<p><a href="#dtd">Parcel Descriptor DTD and sample XML</a> </p>
@@ -39,7 +39,7 @@ type</a> </p>
<a name="bsh"></a>
<h2>Hello World in BeanShell</h2>
Here's a BeanShell script that inserts Hello World at the start of an
-OpenOffice.org Writer document:
+OpenOffice Writer document:
<p> </p>
<pre>
import com.sun.star.frame.XModel;
@@ -47,22 +47,22 @@ OpenOffice.org Writer document:
import com.sun.star.uno.UnoRuntime;
import drafts.com.sun.star.script.provider.XScriptContext;
- model = context.getDocument();
+ model = context.getDocument();
textdoc = (XTextDocument)
UnoRuntime.queryInterface(XTextDocument.class, model);
- oText = textdoc.getText();
- oCursor = oText.createTextCursor();
+ oText = textdoc.getText();
+ oCursor = oText.createTextCursor();
oText.insertString(oCursor, "Hello World", false)
</pre>
<a href="#top">Top</a> <a name="bshinvoke"></a>
<h2>Trying out your BeanShell script</h2>
Trying out your Hello World BeanShell script is easy:
<ul>
- <li>Start OpenOffice.org and open a new Writer document. </li>
+ <li>Start OpenOffice and open a new Writer document. </li>
<li>Select the Tools/Configure... menu item. </li>
<li>Select the menu tab. In the Category section select
- OpenOffice.org Scripts/share/Java/selector
+ OpenOffice Scripts/share/Java/selector
<li>In the Function list select ScriptSelector.showOrganizer
<li>Now click the New button to create a menu item for this script. You can
rename the menu item by clicking on it in the Menu entries list, and
@@ -70,7 +70,7 @@ Trying out your Hello World BeanShell script is easy:
<li>Click OK to apply your change
<li>Select your new menu item
<li>A Script dialog appears, browse to a BeanShell script
- eg. Root/share/BeanShell/Highlight/highlighter.bsh and click Edit.
+ e.g. Root/share/BeanShell/Highlight/highlighter.bsh and click Edit.
<li>A BeanShell Debugger window will appear. Click Clear to clear the window
and copy in the text of your Hello World example
<br><div style="text-align: center;"><img src="beanshell.gif" title=""
@@ -82,10 +82,10 @@ Trying out your Hello World BeanShell script is easy:
</ul>
<p>
-If you are new to the OpenOffice.org API this is a great way to experiment
+If you are new to the OpenOffice API this is a great way to experiment
with it. </p>
<p> When you are happy with your BeanShell script, you can create a
-Script Parcel which can be deployed to OpenOffice.org installations or
+Script Parcel which can be deployed to OpenOffice installations or
documents for use by others. This can be done <a
href="netbeans-devguide.html">using NetBeans</a> or <a
href="commandline-devguide.html">from the command line</a>. </p>
@@ -95,15 +95,15 @@ documents for use by others. This can be done <a
<a name="js">
<h2>Hello World in JavaScript</h2>
</a> Here's a JavaScript script that inserts Hello World at the start of
-an OpenOffice.org Writer document: </p>
+an OpenOffice Writer document: </p>
<pre>
importClass(Packages.com.sun.star.uno.UnoRuntime);
importClass(Packages.com.sun.star.text.XTextDocument);
- var oModel = XSCRIPTCONTEXT.getDocument();
+ var oModel = XSCRIPTCONTEXT.getDocument();
var oTextdoc = UnoRuntime.queryInterface(XTextDocument, oModel);
- var oText = oTextdoc.getText();
- var oCursor = oText.createTextCursor();
+ var oText = oTextdoc.getText();
+ var oCursor = oText.createTextCursor();
oText.insertString(oCursor, "Hello World", false);
</pre>
@@ -111,14 +111,14 @@ an OpenOffice.org Writer document: </p>
<p> The XSCRIPTCONTEXT variable above is a global instance of the
XScriptContext type which is available to all JavaScript scripts
executed by the Scripting Framework. See <a href="#context">Writing
-OpenOffice.org Scripts and the XScriptContext type</a> for the methods
available
+OpenOffice Scripts and the XScriptContext type</a> for the methods available
for the XScriptContext type. </p>
<p> <a href="#top">Top</a> </p>
<h2> <a name="jsinvoke"> Trying out a JavaScript script in
-OpenOffice.org </a></h2>
+OpenOffice </a></h2>
Once again you can use the Edit/Debug Scripts dialog to open a
JavaScript script in an editor. The Rhino JavaScript Editor from the <a
- href="http://mozilla.org/rhino";>Mozilla Rhino project</a> can be used
+
href="https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino";>Mozilla
Rhino project</a> can be used
to debug and test your JavaScript scripts.
<ul>
<li>Create a menu item for the Script dialog as described in the
@@ -168,17 +168,17 @@ Here's the Hello World script in Java:
}
</pre>
</font> </p>
-<p> OpenOffice.org scripts in Java need to be compiled in order to execute
them.
+<p> OpenOffice scripts in Java need to be compiled in order to execute them.
See the <a href="netbeans-devguide.html">Developing Scripts in NetBeans</a>
and <a href="commandline-devguide.html">Developing Scripts on the
command line</a> guides for instructions on how to compile and deploy
-OpenOffice.org scripts in Java. </p>
+OpenOffice scripts in Java. </p>
<p> <a href="#top">Top</a> <a name="context"></a> </p>
-<h2>Writing OpenOffice.org scripts and the XScriptContext type</h2>
+<h2>Writing OpenOffice scripts and the XScriptContext type</h2>
The XScriptContext type is used to obtain the the document context,
-desktop and component factory from an OpenOffice.org script. Any public Java
+desktop and component factory from an OpenOffice script. Any public Java
method which accepts XScriptContext as it's first parameter can be
-executed as an OpenOffice.org script. For BeanShell scripts, an instance of
+executed as an OpenOffice script. For BeanShell scripts, an instance of
XScriptContext is available in a global variable called "context" which
can be used by the script.
<p> The following accessor methods are available on the XScriptContext
@@ -190,7 +190,7 @@ script was invoked
Instance>.getDocument()</font> <br>
returns <font face="Courier, monospace"
size="2">::com::sun::star::frame::XModel</font> </p>
</li>
- <li>OpenOffice.org Desktop - access the desktop of the running OpenOffice.org
+ <li>OpenOffice Desktop - access the desktop of the running OpenOffice
<p> <font face="Courier, monospace" size="2"> <XScriptContext
Instance>.getDesktop()</font> <br>
returns <font face="Courier, monospace" size="2">
@@ -210,7 +210,7 @@ using the following import directive: <font face="Courier,
monospace"
<pre> import drafts.com.sun.star.script.provider.XScriptContext;<br></pre>
</font>
<p> <a href="#top">Top</a> <a name="tips"></a> </p>
-<h2>Tips on writing OpenOffice.org scripts</h2>
+<h2>Tips on writing OpenOffice scripts</h2>
<ul>
<li>
<p><b>Performance:</b> Currently scripts are being loaded by the
@@ -218,7 +218,7 @@ Scripting Framework each time they are run. As such it is
important to
keep the size of your scripts and any dependent jar files they are using
reasonably small. In future releases this script loading will be
optimised by changing the point at which the scripts are loaded by
-OpenOffice.org and using various caching schemes once they are loaded.
+OpenOffice and using various caching schemes once they are loaded.
However, the initial load will always be effected by the script and
it's dependent jar/class file sizes. </p>
</li>
@@ -229,7 +229,7 @@ user interaction via a dialog for instance, then it is your
responsibility to spawn a thread in the running script which can manage
this process or interaction and let the script return promptly. Within
this running thread you should follow the normal UNO component
-threading guidelines to ensure that they do not deadlock OpenOffice.org
+threading guidelines to ensure that they do not deadlock OpenOffice
through inappropriate use of the UNO API. </p>
</li>
</ul>
@@ -241,7 +241,7 @@ parcel-descriptor.xml follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?>
-<!-- DTD for Parcel Meta data for use in the OpenOffice.org Scripting
Framework Project -->
+<!-- DTD for Parcel Meta data for use in the OpenOffice Scripting Framework
Project -->
<!ELEMENT description (#PCDATA)>
<!ELEMENT displayname EMPTY>
@@ -279,7 +279,7 @@ used to extend the JVM's classpath.
<pre>
<?xml version="1.0" encoding="UTF-8"?>
-<!--Sample Meta Data for use with the Scripting Framework Project in
OpenOffice.org -->
+<!--Sample Meta Data for use with the Scripting Framework Project in
OpenOffice -->
<!DOCTYPE parcel SYSTEM "parcel.dtd">
<parcel language="Java">
@@ -297,6 +297,5 @@ used to extend the JVM's classpath.
</pre>
<a href="#top">Top</a>
-<hr> Last Modified: Nov 28 2003
</body>
</html>
