incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1206297 [19/19] - in /incubator/ooo/ooo-site/trunk/content/framework: documentation/ documentation/devmanual/ documentation/filters/ documentation/filterui/ documentation/mimetypes/ documentation/others/ drafts/ proposals/ proposals/apply/...
Date Fri, 25 Nov 2011 20:02:33 GMT
Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/commandline-devguide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/commandline-devguide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/commandline-devguide.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/commandline-devguide.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,185 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <title>Developing Scripts on the Command Line</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<a name="top"></a>
+<h1>Developing Scripts on the Command Line</h1>
+For users who do not wish to develop their OpenOffice.org scripts using an IDE
+there is a simple command line interface built into the OpenOffice.org Scripting
+module which can be used for the generation and deployment of OpenOffice.org
+Scripts.
+
+<h2>Contents</h2>
+<ul>
+  <li>
+    <p><a href="#prereqs">Prerequisites</a> </p>
+  </li>
+  <li>
+    <p><a href="#usage">The CommandLineTools class</a> </p>
+  </li>
+  <li>
+    <p><a href="#examples">Examples</a> </p>
+  </li>
+</ul>
+
+<h2><a name="prereqs">Prerequisites</a></h2>
+<ul>
+  <li>The Scripting module office.jar file should be included in the
+classpath. You can download this file from <a href="./office.jar">here</a>
+  </li>
+  <li>The main Scripting Framework jar file ScriptFramework.jar also needs
+to be included in the classpath. You can find it in the program/classes
+directory of your OpenOffice.org installation.
+  </li>
+  <li>The CommandLineTools class will only work if an XML parser (such
+as <a href="http://xml.apache.org/xerces2-j/index.html">Apache Xerces</a>)
+is available in the classpath.</li>
+</ul>
+<a name="usage"> </a>
+<h2><a name="usage">The CommandLineTools class</a></h2>
+<a name="usage">The CommandLineTools class takes the following options (<b>Note:</b>
+Options in angle brackets "&lt;&gt;" are required, options in square
+brackets "[]" are optional): </a>
+<blockquote> <a name="usage"><b>[-o Path to OpenOffice.org Installation] -g [Path to Parcel directory] [options]</b> </a>
+  <p> <a name="usage">Generates a Script Parcel for the given the
+parcel directory. The optional -o flag is used to specify that path
+to your OpenOffice.org installation. If it is not provided the CommandLineTools
+class will attempt to discover your OpenOffice.org installation and will print
+an error if it fails. The parcel name will be the name of the parcel
+directory plus the .sxp extension. </a></p>
+  <ul>
+    <li><a name="usage">If a parcel directory is not specified the
+current directory is used. If the parcel directory does not contain a
+directory named Contents an error message is printed. Otherwise a Script
+Parcel (.sxp) file is generated in the parcel directory containing all
+of the files under the Contents directory. The options that may be used
+with the -g option allow the user to specify how the
+parcel-descriptor.xml file for the Script Parcel is generated (see the
+Scripting Framework </a><a href="developer-guide.html">developer guide</a>
+for more information on the parcel-descriptor.xml file). The following
+options are available:
+      <p> <b>[-l language[=supported extension list]]</b> </p>
+      <p> Specifies which language attribute to use for the parcel
+element in the parcel-descriptor.xml file. The supported extension list
+is ignored if the language is Java. Otherwise all files that have one of
+the supported extensions (the list should be separated by the platform
+specific path separator, ":" on Unix, ";" on Windows) will be added as
+script entries to the parcel-descriptor.xml file. </p>
+      <p> Alternatively the user can specify a list of names at the
+command line which will be added as scripts and no search for script
+names will be performed. The following table shows the behaviour of
+CommandLineTools when the -l flag is used: </p>
+      <p>
+      <table border="1">
+        <tbody>
+          <tr>
+            <th>-l flag used? </th>
+            <th>parcel-descriptor.xml exists? </th>
+            <th>result </th>
+          </tr>
+          <tr>
+            <td align="center">no </td>
+            <td align="center">no </td>
+            <td>error message printed </td>
+          </tr>
+          <tr>
+            <td align="center">yes </td>
+            <td align="center">no </td>
+            <td>parcel-descriptor.xml generated<br>
+parcel.sxp generated </td>
+          </tr>
+          <tr>
+            <td align="center">no </td>
+            <td align="center">yes </td>
+            <td>parcel-descriptor.xml not generated<br>
+parcel.sxp generated </td>
+          </tr>
+          <tr>
+            <td align="center">yes </td>
+            <td align="center">yes </td>
+            <td>if <br>
+language is different from parcel-descriptor.xml language, error <br>
+else <br>
+parcel-descriptor.xml regenerated <br>
+parcel.sxp generated </td>
+          </tr>
+        </tbody>
+      </table>
+      </p>
+      <p> <b>[-p name=value]</b> </p>
+      <p> Specifies a name value pair to be added as a language
+dependent property in the parcel-descriptor.xml file </p>
+      <p> <b>[-v]</b> </p>
+      <p> Specifies that verbose output should be displayed. </p>
+    </li>
+  </ul>
+  <p> <b>[-o Path to OpenOffice.org Installation] -d &lt;Path to Script Parcel&gt; &lt;Target
+Directory|Document&gt;</b> </p>
+  <p> Deploys the given Script Parcel to a directory or an
+OpenOffice.org document. The optional -o flag is used to specify that path
+to your OpenOffice.org installation. If it is not provided the CommandLineTools
+class will attempt to discover your OpenOffice.org installation and will print
+an error if it fails. A directory will be created with the name of
+the Parcel and the contents of the Parcel will be put into that
+directory. </p>
+  <ul>
+    <li>If deploying to an OpenOffice.org installation the target
+directory should be the &lt;OpenOffice.org Installation&gt;/user/Scripts or
+&lt;OpenOffice.org Installation&gt;/share/Scripts directory. If the either the
+Script Parcel or the target do not exist an error message is printed.
+Otherwise the Script Parcel is deployed to the target. </li>
+  </ul>
+</blockquote>
+<p><a href="#top">Top</a> <a name="examples"> </a></p>
+<h2><a name="examples">Examples</a></h2>
+<ul>
+  <li>
+    <p><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g myparceldir -l Java </font> </a></p>
+    <p><a name="examples">Generates a myparceldir.sxp file in
+myparceldir automatically exporting all public Java methods which take
+XScriptContext as their first parameter as OpenOffice.org scripts. </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g -l BeanShell=.bsh </font> </a>
+    <p><a name="examples">Generates a script parcel file in the current
+directory automatically exporting all files that end with the .bsh
+extension as BeanShell scripts </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g myparceldir -l BeanShell MyScript.bsh </font> </a>
+    <p><a name="examples">Generates a myparceldir.sxp file in
+myparceldir and exports MyScript.bsh as an OpenOffice.org script. </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g myparceldir -l Java -p classpath=dep1.jar:dep2.jar </font> </a>
+    <p><a name="examples">Generates a myparceldir.sxp file in
+myparceldir, automatically searching for valid OpenOffice.org scripts, and
+adding the classpath property to each OpenOffice.org script. </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g myparceldir -l Java -p classpath=dep1.jar:dep2.jar
+-p secondprop=secondvalue </font> </a>
+    <p><a name="examples">Generates a myparceldir.sxp file in
+myparceldir, automatically searching for valid OpenOffice.org scripts, and
+adding the classpath and the secondprop properties to each OpenOffice.org
+script. </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -d myparceldir.sxp /export/home/MyOffice/user/Scripts </font> </a>
+    <p><a name="examples">Deploys the myparceldir.sxp Script Parcel to
+the specified office directory.</a></p>
+  </li>
+  <li><a name="examples"> <font face="Courier, monospace" size="2">java
+CommandLineTools -g myparceldir -l JavaScript MyScript.js</font></a><br>
+    <a name="examples">Generates a myparceldir.sxp file in myparceldir
+and exports MyScript.js as an OpenOffice.org script.</a></li>
+</ul>
+<p><a href="#top">Top</a> </p>
+<hr> Last Modified: Nov 19 2003
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/commandline-devguide.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/developer-guide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/developer-guide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/developer-guide.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/developer-guide.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,302 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <title>Writing Scripts in BeanShell and Java</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<h1>Writing Scripts in BeanShell, JavaScript and Java</h1>
+<a name="top"></a>
+<h2>Contents</h2>
+<ul>
+  <li>
+    <p><a href="#bsh">Hello World in BeanShell</a> </p>
+  </li>
+  <li>
+    <p><a href="#bshinvoke">Trying out your BeanShell script</a> </p>
+  </li>
+  <li>
+    <p><a href="#js">Hello World in JavaScript</a> </p>
+  </li>
+  <li>
+    <p><a href="#jsinvoke">Trying out a JavaScript script</a> </p>
+  </li>
+  <li>
+    <p><a href="#java">Hello World in Java</a> </p>
+  </li>
+  <li>
+    <p><a href="#context">Writing OpenOffice.org Scripts and the XScriptContext
+type</a> </p>
+  </li>
+  <li>
+    <p><a href="#tips">Tips on writing OpenOffice.org scripts</a> </p>
+  </li>
+  <li>
+    <p><a href="#dtd">Parcel Descriptor DTD and sample XML</a> </p>
+  </li>
+</ul>
+<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:
+<p> </p>
+<pre>
+    import com.sun.star.frame.XModel;
+    import com.sun.star.text.*;
+    import com.sun.star.uno.UnoRuntime;
+    import drafts.com.sun.star.script.provider.XScriptContext;
+
+    model = context.getDocument(); 
+    textdoc = (XTextDocument)
+        UnoRuntime.queryInterface(XTextDocument.class, model);
+
+    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>Select the Tools/Configure... menu item. </li>
+  <li>Select the menu tab. In the Category section select
+      OpenOffice.org 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
+      move it around the menu hierarchy using the arrow buttons.
+  <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.
+  <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=""
+           alt="" style="width: 477px; height: 319px;"><br></div>
+  </li>
+  <li>Now click on the Run button.
+  <li>You should see Hello World appear at the start of the Writer document.
+  <li>Click Close so that the highlighter.bsh script is not overwritten
+</ul>
+
+<p>
+If you are new to the OpenOffice.org 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
+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>
+<p>
+<a href="#top">Top</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>
+<pre>
+    importClass(Packages.com.sun.star.uno.UnoRuntime);
+    importClass(Packages.com.sun.star.text.XTextDocument);
+
+    var oModel = XSCRIPTCONTEXT.getDocument(); 
+    var oTextdoc = UnoRuntime.queryInterface(XTextDocument, oModel);
+    var oText = oTextdoc.getText(); 
+    var oCursor = oText.createTextCursor(); 
+
+    oText.insertString(oCursor, "Hello World", false);
+</pre>
+
+<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
+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>
+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
+to debug and test your JavaScript scripts.
+<ul>
+  <li>Create a menu item for the Script dialog as described in the
+      BeanShell instructions above
+  <li>Open the Script dialog, navigate to
+      Root/share/JavaScript/ExportSheetsToHTML/exportsheetstohtml.hs and
+      click edit.</li>
+  <li>A Rhino Debugger window will appear. Delete the text in the window and
+      paste in the Hello World code
+      <br><div style="text-align: center;"><img src="rhino.gif" title=""
+           alt="" style="width: 640px; height: 646px;"><br> </div>
+  </li>
+  <li>To run the script select File/Run and then click on the Go button.
+</ul>
+<p> The Rhino Debugger also includes debugging functionality, so you can
+set breakpoints in your JavaScript script and step through the code as
+it is executed. </p>
+<p>
+<a href="#top">Top</a>
+
+<a name="java"></a> </p>
+<h2>Hello World in Java</h2>
+Here's the Hello World script in Java:
+<p> <font face="Courier, monospace" size="2">
+<pre>    import com.sun.star.frame.XModel;
+    import com.sun.star.text.*;
+    import com.sun.star.uno.UnoRuntime;
+    import drafts.com.sun.star.script.provider.XScriptContext;
+
+    public class MyClass {
+
+        // The script method must be public
+        // It can either be static or non-static
+
+        public void showForm(XScriptContext xSc) {
+
+            // getting the text document object
+            XModel xmodel = xSc.getDocument();
+
+            XTextDocument xtextdoc = (XTextDocument)
+                UnoRuntime.queryInterface(XTextDocument.class, xmodel);
+            XText xtext = xtextdoc.getText();
+            XTextCursor xtextcursor = xtext.createTextCursor();
+
+            xtext.insertString(xtextcursor, "Hello World", false);
+        }
+    }
+</pre>
+</font> </p>
+<p> OpenOffice.org 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>
+<p> <a href="#top">Top</a> <a name="context"></a> </p>
+<h2>Writing OpenOffice.org 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
+method which accepts XScriptContext as it's first parameter can be
+executed as an OpenOffice.org 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
+type: </p>
+<ul>
+  <li>Current document - access the document context against which the
+script was invoked
+    <p> <font face="Courier, monospace" size="2"> &lt;XScriptContext
+Instance&gt;.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
+    <p> <font face="Courier, monospace" size="2"> &lt;XScriptContext
+Instance&gt;.getDesktop()</font> <br>
+returns <font face="Courier, monospace" size="2">
+::com::sun::star::frame::XDesktop</font> </p>
+  </li>
+  <li>Component Factory - access a ComponentContext factory to create
+other UNO components as required
+    <p> <font face="Courier, monospace" size="2"> &lt;XScriptContext
+Instance&gt;.getComponentContext()</font> <br>
+returns <font face="Courier, monospace" size="2">
+::com::sun::star::uno::XComponentContext</font> </p>
+  </li>
+</ul>
+The Java or BeanShell script must import the XScriptContext interface,
+using the following import directive: <font face="Courier, monospace"
+ size="2">
+<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>
+<ul>
+  <li>
+    <p><b>Performance:</b> Currently scripts are being loaded by the
+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.
+However, the initial load will always be effected by the script and
+it's dependent jar/class file sizes. </p>
+  </li>
+  <li>
+    <p><b>Threading:</b> Scripts are run synchronously by the Scripting
+Framework. If you wish to perform any background task or provide some
+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
+through inappropriate use of the UNO API. </p>
+  </li>
+</ul>
+<a href="#top">Top</a> <a name="dtd"></a>
+<h2>Parcel Descriptor DTD and sample XML</h2>
+Each Script Parcel must contain a parcel-descriptor.xml file which provides
+all the necessary metadata for the script. The DTD for the
+parcel-descriptor.xml follows:
+
+<pre>
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;!-- DTD for Parcel Meta data for use in the OpenOffice.org Scripting Framework Project --&gt;
+
+&lt;!ELEMENT description (#PCDATA)&gt;
+&lt;!ELEMENT displayname EMPTY&gt;
+&lt;!ELEMENT functionname EMPTY&gt;
+&lt;!ELEMENT prop EMPTY&gt;
+&lt;!ELEMENT languagedepprops (prop+)&gt;
+&lt;!ELEMENT script (description, displayname, functionname, languagedepprops*)&gt;
+&lt;!ELEMENT parcel (script+)&gt;
+&lt;!ATTLIST displayname
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST locale
+	lang CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST functionname
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST prop
+	name CDATA #REQUIRED
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST script
+	language CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST parcel
+	language CDATA #REQUIRED
+&gt;
+</pre>
+
+<p>
+
+The following is an example of a parcel-descriptor.xml file that
+defines a script, implemented in Java. The languagedepprops element is
+used to extend the JVM's classpath.
+
+<pre>
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;!--Sample Meta Data for use with the Scripting Framework Project in OpenOffice.org --&gt;
+&lt;!DOCTYPE parcel SYSTEM "parcel.dtd"&gt;
+
+&lt;parcel language="Java"&gt;
+	&lt;script language="Java"&gt;
+		&lt;displayname value="Memory.usage"/&gt;
+		&lt;description&gt;
+			Displays the memory current memory usage
+		&lt;/description&gt;
+		&lt;functionname value="memoryUtils.memoryUsage"/&gt;
+		&lt;languagedepprops&gt;
+			&lt;prop name="classpath" value="/opt/foo.jar:/usr/java/src.jar"/&gt;
+		&lt;/languagedepprops&gt;
+	&lt;/script&gt;
+&lt;/parcel&gt;
+</pre>
+
+<a href="#top">Top</a>
+<hr> Last Modified: Nov 28 2003
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/developer-guide.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/faq.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/faq.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/faq.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/faq.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,97 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+	<TITLE>FAQ</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="CREATED" CONTENT="20021203;15313500">
+	<META NAME="CHANGED" CONTENT="20030318;19405289">
+</HEAD>
+<BODY LANG="en-US">
+<H1><A NAME="top"></A>Frequently Asked Questions for the Office
+Scripting Framework</H1>
+<H2>Questions</H2>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm"><A HREF="#1">What is the
+  OpenOffice.org Scripting Framework?</A> 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm"><A HREF="#2">Why are you developing the
+  OpenOffice.org Scripting Framework?</A> 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm"><A HREF="#3">In what release of
+  OpenOffice.org will the Scripting Framework be released?</A> 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm"><A HREF="#4">Why is there a delay
+	in starting the first script?</A> 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm"><A HREF="#5">
+  I have removed the examples scripts provided with my OpenOffice.org
+  installation and installed my own but the script in ExampleSpreadSheet.sxc
+  still works. Why?</A> 
+	</P>
+</OL>
+<H2>Answers</H2>
+<OL>
+
+	<LI><P><A NAME="1"></A><B>What is the OpenOffice.org Scripting Framework?</B>
+	<P>The Scripting Framework is a project to allow users of OpenOffice.org
+     to write scripts to automate commonly performed tasks in a language
+     of their choice.
+	<P STYLE="margin-bottom: 0cm"><A HREF="#top">Top</A> 
+
+	<LI><P><A NAME="2"></A><B>Why are you developing the OpenOffice.org Scripting Framework?</B>
+	<P>The Scripting Framework is a project to allow users of OpenOffice.org
+     to write scripts to automate commonly performed tasks in a language
+     of their choice.
+  <P>There are currently two ways for users and developers to add
+     functionality to OpenOffice.org, namely macros and UNO components. </p>
+  <P>Macros are a set of instructions which OpenOffice.org can interpret
+     at runtime to carry out a specific set of tasks in OpenOffice.org. Users
+     can create a macro by recording a number of tasks in OpenOffice.org,
+     save this set of tasks as a macro and then bind this macro to a menu or
+     keypress. The macro is run by hitting the bound menu or key. Advanced
+     users can write their own StarBasic macros in an embedded StarBasic IDE
+     if they wish. </p>
+  <P>UNO components are compiled C++ or Java components, which a
+     developer can write using the UNO API to access and manipulate
+     OpenOffice.org. The component is written in an external IDE in C++ or
+     Java (or any language with a supported UNO bridge). The end user needs
+     to install any new component in their OpenOffice.org to make use of this
+     new functionality. UNO component development is supported by the ODK. </p>
+  <P>The Scripting Framework aims to strike a balance between these two
+     approaches of customizing OpenOffice.org. The framework will allow
+     scripts to be written in a variety of languages, deployed into
+     OpenOffice.org installations or documents, loaded at runtime and
+     executed in OpenOffice.org. The framework will allow any number of
+     different scripting languages to be plugged into OpenOffice.org for
+     which there is an UNO bridge. Our focus will be to support languages
+     with a Java implementation, but the framework can be made to work with
+     any scripting langauge with a supported UNO bridge such as the UNO
+     Python bridge. In this way users and developers will be able to write
+	<P STYLE="margin-bottom: 0cm"><A HREF="#top">Top</A> 
+
+	<LI><P><A NAME="3"></A><B>In what release of OpenOffice.org will the
+  Scripting Framework be released?</B>
+	<P>The Scripting Framework will be released as part of OpenOffice.org 2.0. In
+  the meantime completed features will be made available via developer builds.
+	<P STYLE="margin-bottom: 0cm"><A HREF="#top">Top</A> 
+
+	<LI><P><A NAME="4"></A><B>Why is there a delay in starting the first script?</B>
+	<P>The delay is caused by the startup of the inprocess JVM by OpenOffice.org. 
+	<P STYLE="margin-bottom: 0cm"><A HREF="#top">Top</A> 
+
+	<LI><P><A NAME="5"></A><B>I have removed the examples provided with the
+	Script Framework installation and installed my own but the script in
+	ExampleSpreadSheet.sxc still works. Why? </B>
+	</P>
+	<P>Both the script and the Key bindings are contained in the document
+     itself.
+	</P>
+	<P STYLE="margin-bottom: 0cm"><A HREF="#top">Top</A> 
+	</P>
+</OL>
+<HR>
+<P>Last Modified: Nov 19 2003
+</P>
+</BODY>
+</HTML>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/faq.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig1.png
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig1.png?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig1.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig2.png
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig2.png?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig2.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig3.png
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig3.png?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig3.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig4.png
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig4.png?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig4.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig5.png
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig5.png?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig5.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig6.png
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig6.png?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/fig6.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/index.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/index.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/index.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,193 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<h1>OpenOffice.org Scripting Framework</h1>
+
+<p><b>Project Owners:</b> <a href="mailto:john.rice@sun.com">John Rice</a>
+, <a href="mailto:noel.power@sun.com">Noel Power</a>
+
+<p>
+<table style="width: 100%; background-color: rgb(240, 240, 240);"
+ border="0" cellpadding="2" cellspacing="0">
+  <col width="270"> <col width="6"> <col width="220"> <col
+ width="171"> <col width="117"> <col width="36"> <tbody>
+    <tr>
+      <td colspan="6"
+ style="background-color: rgb(0, 49, 90); width: 100%;">
+      <p align="center"><font color="#ffffff"><b>Documentation for the latest release</b> </font> </p>
+      </td>
+    </tr>
+    <tr>
+      <th
+ style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
+      <p align="left"><font color="#00315a"><b>Name</b> </font> </p>
+      </th>
+      <th colspan="5"
+ style="background-color: rgb(153, 204, 255); width: 70%; text-align: left;">
+      <p align="left"><font color="#00315a"><b>Description</b> </font>
+      </p>
+      </th>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p>New Features</p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+        The Scripting Framework is now installed with OpenOffice.org.
+        Basic macros can now be executed as previously or via the
+        Scripting Framework as well as the other languages supported.
+        Scripts are listed and can be assigned in the:
+        <ul>
+          <li>Tools/Configure dialog
+          <li>Basic dialog controls properties editor
+          <li>Form controls properties editor in documents
+          <li>Hyperlinks, Graphics and Objects property dialogs 
+        </ul>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p>Install</p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Just install the OpenOffice.org snapshot developer build 680_m15 from <a href="http://www.openoffice.org/dev_docs/source/680/">here</a></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td rowspan="2" style="width: 30%;">
+      <p>Script User Guides</p>
+      </td>
+      <td colspan="4" style="width: 70%;">
+      <p><a href="./user-guide.html">General User Guide</a></p>
+      </td>
+    </tr>
+    <tr>
+      <td colspan="4" width="395" valign="top">
+      <p><a href="../utilities-download.html">Utility Scripts
+contributed
+by the OpenOffice.org community</a></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td rowspan="3" width="270">
+      <p>Script Developer Guides</p>
+      </td>
+      <td width="220" colspan="4">
+      <p><a href="./developer-guide.html">Writing Scripts in BeanShell, JavaScript and Java</a> </p>
+      </td>
+    </tr>
+    <tr>
+      <td width="220" colspan="4" valign="top">
+      <p><a href="./netbeans-devguide.html">Developing Scripts in NetBeans</a></p>
+      </td>
+    </tr>
+    <tr>
+      <td width="220" colspan="4" valign="top">
+      <p><a href="./commandline-devguide.html">Developing Scripts on the command line</a></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./SFArch.html">Architecture Overview</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Description of Scripting Framework architecture</p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><a href="./faq.html">FAQ</a></td>
+      <td style="vertical-align: top;" colspan="5">Frequently Asked
+Questions for the OpenOffice.org Scripting Framework</td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./whats-next.html">What's Next</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Planned features for the OpenOffice.org Scripting Framework</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<p>
+<table style="width: 100%; background-color: rgb(240, 240, 240);"
+ border="0" cellpadding="2" cellspacing="0">
+  <col width="270"> <col width="6"> <col width="220"> <col
+ width="171"> <col width="117"> <col width="36"> <tbody>
+    <tr>
+      <td colspan="5"
+ style="width: 100%; background-color: rgb(0, 49, 90);">
+      <p align="center"><font color="#ffffff"><b> Previous Releases</b>
+      </font> </p>
+      </td>
+    </tr>
+    <tr>
+      <th style="background-color: rgb(153, 204, 255); width: 70%;">
+      <p align="left"><font color="#00315a"><b>Version</b> </font> </p>
+      </th>
+      <th colspan="5"
+ style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
+      <p align="left"><font color="#00315a"><b>Released</b> </font> </p>
+      </th>
+    </tr>
+    <tr valign="top">
+      <td style="width: 70%;">
+      <p><a href="../release-0.3/index.html">Early Developer Release Version 0.3</a></p>
+      </td>
+      <td colspan="5" style="width: 30%;">
+      <p>June 2003</p>
+      </td>
+    <tr valign="top">
+      <td style="width: 70%;">
+      <p><a href="../release-0.2/index.html">Early Developer Release
+Version 0.2</a></p>
+      </td>
+      <td colspan="5" style="width: 30%;">
+      <p>April 2003</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 70%;">
+      <p><a href="../release-0.1/index.html">Early Developer Release
+Version 0.1</a></p>
+      </td>
+      <td colspan="5" style="width: 30%;">
+      <p>November 2002</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+</p>
+<hr>
+<table cellpadding="4" cellspacing="0" style="width: 100%;">
+  <tbody>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="mailto:dev@framework.openoffice.org">Mailing List</a></p>
+      </td>
+      <td style="width: 70%;">
+      <p>Installation, User or Developer queries on the OpenOffice.org
+Scripting Framework</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p>Issues</p>
+      </td>
+      <td style="width: 70%;">
+      <p>Issues found in the OpenOffice.org Scripting Framework should be
+logged in Issuezilla<br>
+      <b>component:</b> framework<br>
+      <b>subcomponent:</b> scripting</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<p> Last Modified: Nov 19 2003
+</p>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/index.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/netbeans-devguide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/netbeans-devguide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/netbeans-devguide.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/netbeans-devguide.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,242 @@
+<html>
+<head>
+<title>Developing Scripts in NetBeans</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+
+<body>
+<a name="top"></a>     
+
+<h1>Developing Scripts in NetBeans</h1>
+         
+This document describes how to set up NetBeans for OpenOffice.org Scripting
+and how to write a simple script using NetBeans. You can download
+the NetBeans IDE from the <a href="http://www.netbeans.org/ide/download.html">
+NetBeans download page</a>.
+
+<h2>Contents:</h2>
+
+<ul>
+<li><p><a href="#prerequisites">Pre-requisites</a>
+<li><p><a href="#recipe-create">Creating a Parcel Recipe</a>
+<li><p><a href="#recipe-actions">Actions available for Parcel Recipes</a>
+<li><p><a href="#parcel-actions">Actions available for Script Parcels</a>
+<li><p><a href="#document-actions">Actions available for OpenOffice.org Documents</a>
+<li><p><a href="#debugging">Debugging Java OpenOffice.org scripts in NetBeans</a>
+<li><p><a href="#troubleshooting">Troubleshooting</a>
+</ul>
+
+<a name="prerequisites"></a>
+<h2>Pre-requisites</h2>
+
+<ul>
+<!-- <li>You need to install the OpenOffice.org API support module for NetBeans which
+can be obtained from
+<a href="http://api.openoffice.org/common/man/IDEintegration/OfficeNetBeansIntegration.html">here</a>.
+This module must be installed in NetBeans if you wish to use the
+OpenOffice.org API in your scripts.
+-->
+
+<li>Install the <a href="./office.jar">OpenOffice.org Scripting module</a>
+To install this module, shutdown NetBeans and copy the office.jar file to
+your &lt;NetBeans installation&gt;/modules directory.
+
+<li>Create a directory somewhere on your machine in which you will develop
+your scripts.
+
+<li><b>Note:</b> The OpenOffice.org Scripting module has been tested with NetBeans 3.4
+</ul>
+
+Now start NetBeans and mount the directory you created using the
+File/Mount Filesystem menu option. You also need to mount the following
+of the jar files in the &lt;OpenOffice.org installation&gt;/program/classes directory
+in order to access the OpenOffice.org API from your scripts:
+<p>
+unoil.jar, ridl.jar, sandbox.jar, jurt.jar, juh.jar
+
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="recipe-create"></a>
+<h2>Creating a Parcel Recipe</h2>
+
+OpenOffice.org scripts are delivered in Script Parcels. Like OpenOffice.org documents they
+are zip files. Script Parcels have the .sxp extension. Script Parcels are
+generated from Parcel Recipes where all of the files that are necessary
+to create the parcel are put together. To create a new Parcel Recipe:
+
+<ul>
+<li>Right click on your mounted filesystem
+<li>Select New/Office Scripting/Parcel Recipe
+<li>In the New Wizard window that appears enter a name for your Parcel Recipe
+<li>Select a language for your Parcel Recipe from the Initial Script
+Language dropdown list.
+<li>Click the Finish button to create your Parcel Recipe
+</ul>
+                         
+This will create a new directory with the name you chose. In this directory
+you will find a Contents directory where all of your files will
+be placed. An empty stub file will have been placed in the
+Contents directory and can be used as a starting point for your script.
+
+<p>
+<b>Note:</b> To add further empty stub scripts to your Parcel Recipe, right
+click on the Contents directory and use the New/Office Scripting/Empty Script
+menu item.
+
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="recipe-actions"></a>
+<h2>Actions available for Parcel Recipe</h2>
+
+If the user right clicks on the parcel directory they should be
+able to use the following actions:
+
+<ul>
+<li><b>Compile:</b> Compiles all of the .java files in the Parcel Recipe
+
+<li><b>Build:</b> Compiles all of the .java files in the Parcel Recipe.
+It then searches for valid OpenOffice.org scripts in the language you selected
+in the Contents directory files and pops up a dialog
+which allows you to select which Java methods or BeanShell scripts
+you wish to export as OpenOffice.org scripts.
+Once you have finish making your selections, it creates a
+&lt;Parcel Recipe Name&gt;.sxp Script Parcel file in the Parcel
+Recipe directory. You can configure what files are put into the
+Script Parcel using the File Filter property. If you script includes any
+jar files that need to be in the classpath when it is executed you should
+add them to the Classpath property of your Parcel Recipe.
+
+<li><b>Configure:</b> This pops up the Configure dialog, which allows you
+to select what OpenOffice.org scripts to export. Any changes you make in
+this dialog will <b>only</b> appear in your Script Parcel after you run
+Build again.
+</ul>
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="parcel-actions"></a>
+<h2>Actions available for Script Parcels</h2>
+
+Script Parcels supports only one action:
+
+<ul>
+<li><b>Deploy:</b> This will deploy the Script Parcel to an OpenOffice.org Document
+or to an OpenOffice.org installation. If the Script Parcel already exists
+in the target, you will be asked whether you want to overwrite.
+</ul>
+
+<p>
+<b>Note:</b> If you deploy a Script Parcel to an OpenOffice.org
+installation you need to use the Tools/Scripting Add-on's/Refresh All Scripts
+menu item for the new script to appear in the Assign Script dialog.
+
+<p>
+<b>Note:</b> You can also deploy to OpenOffice.org documents within NetBeans
+using drag and drop or cut and paste.
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="document-actions"></a>
+<h2>Actions available for OpenOffice.org Documents</h2>
+
+OpenOffice.org Documents are also recognised by NetBeans. Any parcels contained
+in the document will be displayed as nodes of the OpenOffice.org document. Deleting
+one of these nodes will remove the Script Parcel from the document. You
+should ensure that the document is not open in OpenOffice.org before deleting
+any parcels it may contain.
+
+OpenOffice.org documents support the standard Delete, Cut and Copy actions and
+the following custom actions:
+
+<ul>
+<li><b>Open:</b> This will open the document in OpenOffice.org using the path
+in the Office Settings property to find the OpenOffice.org installation.
+
+<p>
+If the path to OpenOffice.org is not valid, an error dialog will be popped
+up informing the user that they need to set their Path to Office
+Installation property. This setting can be changed by bringing
+up the Tools/Options dialog and changing
+IDE Configuration/Server and External Tool Settings/Office Settings
+</ul>
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="debugging"></a>
+<h2>Debugging Java OpenOffice.org scripts in NetBeans</h2>
+
+<ul>
+<li>Follow the instructions at
+<a href="http://api.openoffice.org/common/man/IDEintegration/OfficeNetBeansIntegration.html#Debugging">
+Debugging Java components in NetBeans/Forte for Java</a>
+to set up your OpenOffice.org installation to allow debugging of the JVM.
+
+<li>Start OpenOffice.org and run one of your Java scripts. This will
+make sure the JVM is running.
+
+<li>Attach to OpenOffice.org JVM using the NetBeans Debug/Start Session/Attach...
+menu option.
+
+<li>Load a script source in NetBeans and set up breakpoints using
+Debug/New Breakpoint... menu option.
+
+<li>Run the script in OpenOffice.org.
+</ul>
+
+<p>
+<b>Note:</b> As the BeanShell scripting language does not support debugging
+it is not possible to debug BeanShell OpenOffice.org scripts from NetBeans. You
+can however use the Interactive BeanShell scripting menu item under the Tools
+menu in OpenOffice.org to test BeanShell code. Just enter any BeanShell code
+and hit the Eval button to execute it.
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="troubleshooting"></a>
+<h2>Troubleshooting</h2>
+
+<ul>
+<li><p>If you encounter problems when developing or deploying scripts in
+NetBeans, one thing you can try is to move your NetBeans settings directory
+(.netbeans on UNIX, netbeans in Windows - can be found in your home
+directory) to another name and restart NetBeans.
+
+<li><p>The Choose What to Export as Scripts dialog <b>only</b> displays
+methods which are defined within class files, it will not display
+methods in class files which are within jar files in the Parcel Recipe.
+
+<li><p>If you include package directives in the Java source files of your
+Parcel Recipe, you should ensure that the source files are in the appropriate
+directories for your package directives. This is because the
+default NetBeans compiler implementation does not use the -d switch to the
+Java compiler. As a result class files do not get placed in the appropriate
+directories and methods in these classes will not appear in the
+Choose What to Export as Scripts dialog.
+
+<p>
+There are a couple of workarounds for this problem:
+
+<p>
+<ol>
+<li>Use the <a href="commandline-devguide.html">command line tools</a>
+<li>Set the Target flag in the Tools/Options window under
+Building/Compiler Types/Internal Compilation
+</ol>
+</ul>
+
+<p>
+<a href="#top">Top</a>
+
+<hr>
+Last Modified: Nov 19 2003
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/netbeans-devguide.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/office.jar
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/office.jar?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/office.jar
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/rhino.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/rhino.gif?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/rhino.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/user-guide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/user-guide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/user-guide.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/user-guide.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,478 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=iso-8859-1">
+  <title></title>
+  <meta name="GENERATOR" content="StarOffice 6.1 Beta 1 (Linux)">
+  <meta name="CREATED" content="20030313;16153200">
+  <meta name="CHANGED" content="20030313;16505100">
+</head>
+<body lang="en-US" dir="ltr">
+<h1><a name="top"></a>User Guide for the OpenOffice.org Scripting
+Framework</h1>
+<h2>Contents</h2>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;"><a href="#prerequisites">Pre-requisites</a></p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;"><a href="#switchon">Configuring
+display of OpenOffice.org Scripts</a></p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;"><a href="#bindscripts">Assiging
+OpenOffice.org Scripts</a> </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;"><a href="#usingsf">Running the
+example OpenOffice.org Scripts</a></p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;"><a
+ href="#Leveraging_StarBasic_Security">OpenOffice.org Security</a></p>
+  </li>
+</ul>
+<h2><a name="prerequisites"></a>Pre-requisites</h2>
+<p>Before you install the Scripting Framework, be aware of the
+following: </p>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;">This is an Early Developer Release
+of the OpenOffice.org Scripting Framework provided for users and
+developers of
+OpenOffice.org to try out and provide feedback. Future releases of the
+Framework may change. </p>
+  </li>
+  <li>
+    <p>The Scripting Framework is currently available in English only. </p>
+  </li>
+</ul>
+<h2><a name="switchon"></a>Configuring display
+of OpenOffice.org scripts</h2>
+<p>As the Scripting Framework project is still in development, display
+of OpenOffice.org scripts is switched off by default in your OpenOffice.org
+installation. To enable the Scripting Framework download one of the following UNO packages:<br>
+</p>
+<ul>
+  <li><a href="../EnableSF.zip">EnableSF.zip</a> simply enables the display of 
+Scripting Framework scripts 
+in parallel with the existing method for listing Basic macros. Note that the 
+Basic macros will also be listed under the Scripting Framework scripts.</li>
+  <li><a href="../EnableSF2.zip">EnableSF2.zip</a> simply enables the display of Scripting Framework scripts 
+instead of the existing method for listing Basic macros.</li>
+</ul>
+The UNO package is then installed using the pkgchk executable found in the OpenOffice.org program directory.<br>
+<font face="Courier, monospace" size="2">pkgchk EnableSF.zip</font>
+<h2><a name="bindscripts"></a>Assigning OpenOffice.org Scripts</h2>
+<p>The execution of OpenOffice.org scripts can be assigned to menu and
+key items
+and also to application, document, object and dialog events.<br>
+</p>
+<p>To assign a script to a new menu item:<br>
+</p>
+<ol>
+  <li>Select the Tools/Configure menu item, and go to the Menu tab.</li>
+  <li>In the Category section of the Menu tab, scroll to the bottom of
+the list and expand the item OpenOffice.org Scripts</li>
+  <li>You should see entries for share (scripts in the share directory
+of your OpenOffice.org installation), user (scripts in the user
+directory of your OpenOffice.org installation), and the current
+document. Expand one of these entries to see the languages for which
+scripts are available</li>
+  <li>Under the language entries you will see entries for script that
+are available. Select one of these entries.</li>
+  <li>A list of the script functions available for assignment will
+appear in the Function list. Select one of the functions.</li>
+  <li>Now click the New button to create a new menu assignment. The new
+menu item will appear in the Menu Entries section of the tab. You can
+rename the new menu item by clicking on it.</li>
+</ol>
+To assign a script to a key combination:<br>
+<ol>
+  <li>Select the Tools/Configure menu item, and go to the Keyboard tab.</li>
+  <li>To select an OpenOffice.org script to assign, follow steps
+2 to 5 for creating menu&nbsp; items. <br>
+  </li>
+  <li>Now select a key combination from the Shortcut Keys section and
+click the Modify button to create a new menu assignment.</li>
+</ol>
+To assign a script to an event:<br>
+<ol>
+  <li>Select the Tools/Configure menu item, and go to the Events tab.</li>
+  <li>To select an OpenOffice.org script, follow steps 2 to 5 for
+creating menu items.<br>
+  </li>
+  <li>Now select an event from the list and click the Assign button to
+assign the selected script to the selected event.</li>
+</ol>
+To assign a script to an event for an embedded Object (eg. a chart):<br>
+<span style="text-decoration: underline;"></span>
+<ol>
+  <li>Select the embedded Object in your document and then select the
+Format/Object... menu item.</li>
+  <li>In the Object dialog that appears select the Macro tab.</li>
+  <li>You should be able to select an OpenOffice.org script and assign
+it to an Object event as in the assign script to event steps above.</li>
+</ol>
+To assign a script to a Hyperlink:<br>
+<ol>
+  <li>Select the Insert/Hyperlink menu item.</li>
+  <li>In the Hyperlink dialog clicking on the Events button will allow
+you to assign an OpenOffice.org script to a hyperlink event.</li>
+</ol>
+To assign a script to a Graphic:<br>
+<ol>
+  <li>Select the Format/Graphics... menu item.</li>
+  <li>In the Graphics dialog you can assign an OpenOffice.org script to
+an event in the Macro tab.</li>
+</ol>
+To assign a script to a Form control:<br>
+<ol>
+  <li>Insert a Form control (eg. a button) into your document by
+clicking on the form functions button on the left hand toolbar,
+selecting a control and then selecting an area in your document to
+create the control.</li>
+  <li>Select the control and then select the Format/Control... menu
+item to bring up a Properties dialog for the control.</li>
+  <li>Select the Events tab of the Properties dialog and click on one
+of the buttons labelled "..." beside the event to which you want to
+assign an OpenOffice.org script.</li>
+  <li>An Assign Macro dialog will pop up in which you can select an
+OpenOffice.org script and assign it to the selected event.<br>
+  </li>
+</ol>
+To assign a script to a control in an OpenOffice.org Basic dialog:<br>
+<ol>
+  <li>Open the OpenOffice.org Basic dialog editor and create a dialog
+with a control on it (eg. a button)</li>
+  <li>Right click on the control and select Properties... on the popup
+menu. <br>
+  </li>
+  <li>Select the Events tab of the Properties dialog and click on one
+of the buttons labelled "..." beside the event to which you want to
+assign an OpenOffice.org script.</li>
+  <li>An Assign Macro dialog will pop up in which you can select an
+OpenOffice.org script and assign it to the selected event.<br>
+  </li>
+</ol>
+<h2><a name="usingsf"></a>Running the example OpenOffice.org Scripts</h2>
+<p>There are three example scripts supplied with the Scripting
+Framework, Highlight, MemoryUsage, and ExportSheetsToHTML.<br>
+</p>
+<p>Highlight is a BeanShell application level
+script for Writer that allows the user to search for a word or phrase.
+It will highlight all instances in red and give a count of the number
+of
+instances. </p>
+<p>The second example, MemoryUsage, is a Java script stored in a Calc
+spreadsheet that checks the current memory usage in the Java Virtual
+Machine and updates cells in the spreadsheet with the usage values. The
+spreadsheet also contains a graph which will update when the cell
+values
+are changed. </p>
+<p>The ExportSheetsToHTML example is a JavaScript application level
+script for Calc which will save each individual sheet in a Calc
+spreadsheet as a separate html file.</p>
+<p><b>Running the Highlight example</b></p>
+<p>To run this example you first need to create a menu item from which
+you can execute the script. </p>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;">Start OpenOffice.org and open an
+existing Writer document or create a new one. </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Follow the steps for creating a menu
+item in the Assigning OpenOffice.org Scripts section. The Highlight
+example is available at OpenOffice.org Scripts/share/BeanShell/Highlight<br>
+    </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Your new menu item will now be
+available and clicking on it will invoke the script. </p>
+  </li>
+  <li>
+    <p>You should see a Highlight Text dialog appear which you can use
+to highlight various text strings you are looking for in the document. </p>
+  </li>
+</ul>
+<p><b>Running the MemoryUsage example</b></p>
+<p>The Java version of the MemoryUsage example is already deployed
+inside an OpenOffice.org document, ExampleSpreadSheet.sxc. To run the
+Java
+example, just open: </p>
+<p>&lt;OpenOffice.org
+Installation&gt;/user/Scripts/java/ExampleSpreadSheet.sxc. </p>
+<p>You can then execute the MemoryUsage script by pressing <b>CTRL+Shift+M</b>
+with the ExampleSpreadSheet.sxc window focused. You should see the
+memory usage values being updated, and the graph should change to
+reflect the new values. You can also find the MemoryUsage example under
+OpenOffice.org Scripts/share/Java/MemoryUsage in the Tools/Configure
+dialog.<br>
+</p>
+<p><span style="font-weight: bold;">Running the ExportSheetsToHTML
+example</span><br>
+</p>
+<p>To run this example you first need to create or open an existing
+spreadsheet document. If you have created a new document save it (eg.
+c:\temp\mycalcdoc.sxc)<br>
+</p>
+<p>Follow the instructions in the Assigning OpenOffice.org Scripts
+section to create a key assignment for the script. You can find the
+ExportSheetsToHTML example at
+OpenOffice.org Scripts/share/JavaScript/ExportSheetsToHTML.</p>
+<ul>
+</ul>
+This will have created a key binding to the ExportSheetsToHTML script.
+Pressing your key binding will now save each sheet in HTML format in
+the
+same
+directory as the original document (eg. c:\temp\mycalcdoc_sheet1.html,
+c:\temp\mycalcdoc_sheet2.html, ...)<br>
+<p><a href="#top">Top</a> </p>
+<h2><a name="Leveraging_StarBasic_Security"></a>OpenOffice.org Security</h2>
+<p style="margin-bottom: 0in;">The Scripting Framework currently uses
+the same
+Security
+settings as OpenOffice.org Basic.&nbsp; The settings allow the user to
+control
+the
+execution of macros present in OpenOffice.org documents. Found in&nbsp;
+the&nbsp; Tools-&gt;Options dialog under&nbsp;
+OpenOffice.org-&gt;Security, these&nbsp; settings allow the user&nbsp;
+to specify the conditions under which it is permissable to execute
+document based OpenOffice.org Basic macros and OpenOffice.org scripts.</p>
+<p style="margin-bottom: 0in;">A full description of how these settings
+work can be found by clicking
+the "Help" button in the dialog, and then clicking "OpenOffice.org",
+and
+"Security" in the left-hand pane of the Help dialog. The possible
+scenarios associated with the security settings are summarised in the
+table below.<br>
+<br>
+</p>
+<table border="2" cellpadding="2" cellspacing="2">
+  <tbody>
+    <tr>
+      <th>
+      <p>"Run Macro"</p>
+      </th>
+      <th>
+      <p>"Confirm in the case of other document sources"</p>
+      </th>
+      <th>
+      <p>"Show Warning before Running"</p>
+      </th>
+      <th>
+      <p>Document path in "Path List"</p>
+      </th>
+      <th>
+      <p>Behaviour</p>
+      </th>
+    </tr>
+    <tr>
+      <td>
+      <p>Never</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>Macros/Scripts never run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Macros/Scripts never run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Macros/Scripts run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Macros/Scripts never run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Warning displayed on document load. If "Run" button clicked
+macros will run, otherwise they will not.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Warning with checkbox to add path to path list is displayed on
+document load. If "Run" button clicked macros/scripts will run,
+otherwise
+they will not. Regardless of which button is clicked, if checkbox is
+ticked document path is added to "Path List".</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Macros/Scripts run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Warning with checkbox to add path to path list is displayed on
+document load. If "Run" button clicked macros/scripts will run,
+otherwise
+they will not. Regardless of which button is clicked, if checkbox is
+ticked document path is added to "Path List".</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Warning displayed on document load. If "Run" button clicked
+macros/scripts will run, otherwise they will not.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>Always</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>Macros/Scripts run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>Always</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>Warning displayed on document load. If "Run" button clicked
+macros/scripts will run, otherwise they will not</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<p><br>
+<a href="#top">Top</a></p>
+<hr> Last Modified: Nov 19 2003
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/user-guide.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/whats-next.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/whats-next.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/whats-next.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/whats-next.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,58 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE>What's Next</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.1 Beta 1 (Solaris Sparc)">
+	<META NAME="CREATED" CONTENT="20030319;16220600">
+	<META NAME="CHANGED" CONTENT="20030319;16313000">
+</HEAD>
+<BODY LANG="en-US" DIR="LTR">
+<H1>Planned Features for the OpenOffice.org Scripting Framework</H1>
+
+<H2>Redesign of the Tools/Configure dialog</H2>
+<P>
+The current Tools/Configure dialog is not very usable. A
+<a href="http://specs.openoffice.org/scripting_framework/index.html">
+specification</a> is being completed for the complete redesign of this dialog.
+
+<H2>ScriptProviderForPython</H2>
+<P>
+Joerg Budischewski has provided UNO bindings for Python and has done some
+work on making a ScriptRuntime available for a previous version of the
+Scripting Framework. This ScriptRuntime needs to be updated to support the
+new Scripting Framework architecture so users can create OpenOffice.org
+scripts in Python.
+
+<H2>Make OpenOffice.org dialogs available to all scripting languages</H2>
+<P>
+Currently dialogs created by the OpenOffice.org Basic dialog editor
+can only be instantiated using the Basic CreateUNODialog function. In the
+next milestone it should be possible to instantiate these dialogs from other
+languages.</P>
+
+<H2>Digital Signing Support</H2>
+<P>
+The intention is to use digital signing of script parcels to give
+a higher degree of security for OpenOffice.org users of these new
+language scripts. The Scripting Framework will be enhanced to verify
+the digital signatures of scripts before they are executed.
+Appropriate configuration settings could be added so users can
+control script execution.</P>
+
+<H2>Common Packaging Format</H2>
+<P STYLE="margin-bottom: 0in">
+We will move to a common packaging format for UNO components, OpenOffice.org
+scripts, and OpenOffice.org Basic macros. 
+</P>
+
+<H2>???</H2>
+<P STYLE="margin-bottom: 0in">
+All suggestions for further features welcome on dev@framework.openoffice.org
+or in IssueZilla under category framework, subcategory scripting.
+</P>
+<HR>
+<P>Last Modified: Nov 28 2003
+</P>
+</BODY>
+</HTML>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/scriptingf1/whats-next.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/testindex.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/testindex.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/testindex.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/testindex.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,193 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<h1>OpenOffice.org Scripting Framework</h1>
+
+<p><b>Project Owners:</b> <a href="mailto:john.rice@sun.com">John Rice</a>
+, <a href="mailto:noel.power@sun.com">Noel Power</a>
+
+<p>
+<table style="width: 100%; background-color: rgb(240, 240, 240);"
+ border="0" cellpadding="2" cellspacing="0">
+  <col width="270"> <col width="6"> <col width="220"> <col
+ width="171"> <col width="117"> <col width="36"> <tbody>
+    <tr>
+      <td colspan="6"
+ style="background-color: rgb(0, 49, 90); width: 100%;">
+      <p align="center"><font color="#ffffff"><b>Documentation for the latest release</b> </font> </p>
+      </td>
+    </tr>
+    <tr>
+      <th
+ style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
+      <p align="left"><font color="#00315a"><b>Name</b> </font> </p>
+      </th>
+      <th colspan="5"
+ style="background-color: rgb(153, 204, 255); width: 70%; text-align: left;">
+      <p align="left"><font color="#00315a"><b>Description</b> </font>
+      </p>
+      </th>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p>New Features</p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+        The Scripting Framework is now installed with OpenOffice.org.
+        Basic macros can now be executed as previously or via the
+        Scripting Framework as well as the other languages supported.
+        Scripts are listed and can be assigned in the:
+        <ul>
+          <li>Tools/Configure dialog
+          <li>Basic dialog controls properties editor
+          <li>Form controls properties editor in documents
+          <li>Hyperlinks, Graphics and Objects property dialogs 
+        </ul>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p>Install</p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Just install the OpenOffice.org snapshot developer build 680_m15 from <a href="http://www.openoffice.org/dev_docs/source/680/">here</a></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td rowspan="2" style="width: 30%;">
+      <p>Script User Guides</p>
+      </td>
+      <td colspan="4" style="width: 70%;">
+      <p><a href="./scriptingf1/user-guide.html">General User Guide</a></p>
+      </td>
+    </tr>
+    <tr>
+      <td colspan="4" width="395" valign="top">
+      <p><a href="./utilities-download.html">Utility Scripts
+contributed
+by the OpenOffice.org community</a></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td rowspan="3" width="270">
+      <p>Script Developer Guides</p>
+      </td>
+      <td width="220" colspan="4">
+      <p><a href="./scriptingf1/developer-guide.html">Writing Scripts in BeanShell, JavaScript and Java</a> </p>
+      </td>
+    </tr>
+    <tr>
+      <td width="220" colspan="4" valign="top">
+      <p><a href="./scriptingf1/netbeans-devguide.html">Developing Scripts in NetBeans</a></p>
+      </td>
+    </tr>
+    <tr>
+      <td width="220" colspan="4" valign="top">
+      <p><a href="./scriptingf1/commandline-devguide.html">Developing Scripts on the command line</a></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./scriptingf1/SFArch.html">Architecture Overview</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Description of Scripting Framework architecture</p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><a href="./scriptingf1/faq.html">FAQ</a></td>
+      <td style="vertical-align: top;" colspan="5">Frequently Asked
+Questions for the OpenOffice.org Scripting Framework</td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./scriptingf1/whats-next.html">What's Next</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Planned features for the OpenOffice.org Scripting Framework</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<p>
+<table style="width: 100%; background-color: rgb(240, 240, 240);"
+ border="0" cellpadding="2" cellspacing="0">
+  <col width="270"> <col width="6"> <col width="220"> <col
+ width="171"> <col width="117"> <col width="36"> <tbody>
+    <tr>
+      <td colspan="5"
+ style="width: 100%; background-color: rgb(0, 49, 90);">
+      <p align="center"><font color="#ffffff"><b> Previous Releases</b>
+      </font> </p>
+      </td>
+    </tr>
+    <tr>
+      <th style="background-color: rgb(153, 204, 255); width: 70%;">
+      <p align="left"><font color="#00315a"><b>Version</b> </font> </p>
+      </th>
+      <th colspan="5"
+ style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
+      <p align="left"><font color="#00315a"><b>Released</b> </font> </p>
+      </th>
+    </tr>
+    <tr valign="top">
+      <td style="width: 70%;">
+      <p><a href="./release-0.3/index.html">Early Developer Release Version 0.3</a></p>
+      </td>
+      <td colspan="5" style="width: 30%;">
+      <p>June 2003</p>
+      </td>
+    <tr valign="top">
+      <td style="width: 70%;">
+      <p><a href="./release-0.2/index.html">Early Developer Release
+Version 0.2</a></p>
+      </td>
+      <td colspan="5" style="width: 30%;">
+      <p>April 2003</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 70%;">
+      <p><a href="./release-0.1/index.html">Early Developer Release
+Version 0.1</a></p>
+      </td>
+      <td colspan="5" style="width: 30%;">
+      <p>November 2002</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+</p>
+<hr>
+<table cellpadding="4" cellspacing="0" style="width: 100%;">
+  <tbody>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="mailto:dev@framework.openoffice.org">Mailing List</a></p>
+      </td>
+      <td style="width: 70%;">
+      <p>Installation, User or Developer queries on the OpenOffice.org
+Scripting Framework</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p>Issues</p>
+      </td>
+      <td style="width: 70%;">
+      <p>Issues found in the OpenOffice.org Scripting Framework should be
+logged in Issuezilla<br>
+      <b>component:</b> framework<br>
+      <b>subcomponent:</b> scripting</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<p> Last Modified: Nov 19 2003
+</p>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/testindex.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/utilities-download.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/utilities-download.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/utilities-download.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/utilities-download.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,236 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <title>Scripts contributed by the OpenOffice.org community</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<a name="top"></a>
+<h1>Utility Scripts contributed by the OpenOffice.org community</h1>
+This page contains downloads of utility scripts that have been
+contributed by the OpenOffice.org community. These scripts are intended
+to demonstrate how to write Java (or the dynamically-typed Beanshell)
+scripts for OpenOffice, with full access to both the OpenOffice.org API
+and the Java APIs. The scripts are for use with the Early Developer
+Release 0.3 of the Office Scripting Framework and all subsequent
+releases.
+<h2>Pre-requisites</h2>
+<ul>
+  <li>OpenOffice.org 1.1beta2 or above installed with the Scripting
+Framework Early Developer release 0.3. If you have not already done this
+then see the <a href="release-0.3/install-guide.html">installation guide</a>.</li>
+</ul>
+<h2>General Installation Procedure</h2>
+<ul>
+  <li>The scripts are made available for download as Zip files. To
+install the scripts, simply unzip them in either the
+&lt;OfficeInstallation&gt;/user or &lt;OfficeInstallation&gt;/share
+directories.</li>
+  <li>The scripts are then available to be bound to the key or menu of
+your choice using the Assign dialogs.<br>
+  </li>
+  <li>If the scripts require any additional pre-requisites,
+installation steps or subsequent modification this will be documented
+below.</li>
+  <li>If you wish to deploy these scripts into a document you will need
+to create a new parcel recipe and copy the sources from the zip files
+below. See the <a
+ href="http://framework.openoffice.org/scripting/scriptingf1/netbeans-devguide.html">Developer
+Guide for Netbeans</a> for more information.<br>
+  </li>
+</ul>
+<h2>Available Scripts</h2>
+<ul>
+  <li><a href="#Word_Count">Word Count&nbsp;</a> <br>
+  </li>
+  <li><a href="#Capitalisation">Capitalisation</a></li>
+  <li><a href="#Post_to_Newsgroups_">Post To Newsgroups</a></li>
+  <li><a href="#Issuezilla_Query_Writer">Scripting Framework Issuezilla
+Query -&gt; Writer</a></li>
+  <li><a href="#Issuezilla_Query_Calc">Scripting Framework Issuezilla
+Query -&gt; Calc</a></li>
+  <li><a href="#Insert_Copyright_Symbol">Insert Copyright Symbol</a></li>
+  <li><a href="#Insert_Trademark_Symbol">Insert Trademark Symbol</a></li>
+  <li><a href="#Insert_Hidden_Text">Insert Hidden Text</a></li>
+  <li><a href="#Export_To_HTML">Export To HTML</a><br>
+  </li>
+  <li><a href="#Combined_Utilities">Combined Utilities</a><br>
+  </li>
+</ul>
+<h2><a name="Word_Count"></a>Word Count</h2>
+<b>Author:</b> <a href="mailto:dfoster@openoffice.org">Duncan Foster</a><br>
+<b>Aim:</b> Provides a simple word count of the selected text.<br>
+<span style="font-weight: bold;">Language:</span> BeanShell<br>
+<b>Pre-requisites:</b> none<br>
+<b>Download:</b>&nbsp; <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/WordCount.zip">WordCount.zip</a>
+(2Kb)<br>
+<b>Installation:</b> no additional steps needed<br>
+<b>Description:</b> Uses the OpenOffice API to get the selected text,
+and then uses Java's StringTokenizer (using the default delimiters) to
+obtain a word count. Displays the result in a simple Swing dialog.<br>
+<b>Issues:</b> none<br>
+<br>
+<a href="#top">Top</a><br>
+<h2><a name="Capitalisation"></a>Capitalisation</h2>
+<b>Author:</b> <a href="mailto:dfoster@openoffice.org">Duncan Foster</a><br>
+<b>Aim:</b> Converts the selected text from upper case to first letter
+upper case, rest lower case, to lower case.<br>
+<span style="font-weight: bold;">Language:</span> BeanShell<br>
+<b>Pre-requisites:</b> none<br>
+<b>Download:</b>&nbsp; <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/Capitalise.zip">Capitalise.zip</a>
+(2Kb)<br>
+<b>Installation:</b> no additional steps needed<br>
+<b>Description:</b> Uses the OpenOffice API to get the selected text (or
+makes a selection of the current word if no text selected), and then
+uses Java to change the case. Rotates from "THIS" -&gt; "This" -&gt;
+"this" -&gt; "THIS". The script attempts to break up selected text into
+sentences using the Java StringTokenizer. The script also attempts to
+maintain the selection.<br>
+<b>Issues:</b> The script fails to maintain the selection if two
+separate areas of text are selected. For example, if the first and last
+words of the previous sentence were selected, only one (undefined) would
+remain selected after the script has been run.<br>
+<a href="#top">Top</a><br>
+<h2><a name="Post_to_Newsgroups_"></a>Post to Newsgroups </h2>
+<b>Author:</b> <a href="mailto:neilm@openoffice.org">Neil Montgomery</a> <br>
+<b>Aim:</b> Facilitates the posting of an OpenOffice document to a
+newsgroup.<br>
+<span style="font-weight: bold;">Language:</span> Java<br>
+<b>Pre-requisites:</b> none<br>
+<b>Download:</b> <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/Newsgroup.zip">Newsgroup.zip</a>
+(540Kb)<br>
+<b>Installation:</b> no additional steps needed<br>
+<b>Description:</b>&nbsp;  The script will detect if a local
+installation of either Netscape or Mozilla has been used to subscribe to
+any newsgroups. These newsgroups will be listed for the user in a combo
+box. If no newsgroups are detected the user must supply the name of the
+newgroup and server. The user may also supply the reply-to address,
+subject and message body (in the comment text field). The user can also
+specify the format in which to send the attached document (the currently
+active document). If the document hasn't already been saved with a
+title, then the default name for the attachment(s) will be
+"Attachment.sxw" and/or "Attachment.html".<br>
+<b>Issues:</b> none.<br>
+<a href="#top">Top</a><br>
+<h2><a name="Issuezilla_Query_Writer"></a>Scripting Framework
+Issuezilla Query -&gt; Writer</h2>
+<b>Author:</b> <a href="mailto:jmrice@openoffice.org">John Rice</a><br>
+<b>Aim:</b> Outputs the results of an Issuezilla query into the open
+Writer document.<br>
+<span style="font-weight: bold;">Language:</span> BeanShell<br>
+<b>Pre-requisites:</b> none<br>
+<b>Download:</b> <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/SFBugsQueryIssuezilla.zip">SFBugsQueryIssuezilla.zip</a>
+(2Kb)<br>
+<b>Installation:</b> The script sets a HTTP proxy on lines 43,44. The
+user will need to modify or remove these according to their local
+settings. The script also contains a certain amount of debug output
+which the user may want to remove.<br>
+<b>Description:</b>&nbsp;  The script uses Java to open a HTTP
+connection to the OpenOffice.org website, passing a URL for an
+Issuezilla query for Scripting Framework bugs. The script then writes
+summary information for each bug into the open Writer document.<br>
+<b>Issues:</b> none.<br>
+<a href="#top">Top</a><br>
+<h2><a name="Issuezilla_Query_Calc"></a>Scripting Framework Issuezilla
+Query -&gt; Calc</h2>
+<b>Author:</b> <a href="mailto:jmrice@openoffice.org">John Rice</a><br>
+<b>Aim:</b> Outputs the results of an Issuezilla query into the open
+Calc document.<br>
+<span style="font-weight: bold;">Language:</span> BeanShell<br>
+<b>Pre-requisites:</b> none<br>
+<b>Download:</b> <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/SFBugsQueryIssuezillaCalc.zip">SFBugsQueryIssuezillaCalc.zip</a>
+(2Kb)<br>
+<b>Installation:</b> The script sets a HTTP proxy on lines 25,26. The
+user will need to modify or remove these according to their local
+settings. <br>
+<b>Description:</b>&nbsp;  The script uses Java to open a HTTP
+connection to the OpenOffice.org website, passing a URL for an
+Issuezilla query for Scripting Framework bugs. The script then writes
+summary information for each bug into the open Calc document.<br>
+<b>Issues:</b> none.<br>
+<a href="#top">Top</a><br>
+<h2><a name="Insert_Copyright_Symbol"></a>Insert Copyright Symbol</h2>
+<span style="font-weight: bold;"> Author:</span> <a
+ href="mailto:dfoster@openoffice.org">Duncan Foster</a><br>
+<span style="font-weight: bold;"> Aim:</span> Inserts a copyright symbol
+(or replaces the current selection with a copyright symbol).<br>
+<span style="font-weight: bold;"> Language:</span> Beanshell<br>
+<span style="font-weight: bold;"> Pre-requisites:</span> none<br>
+<span style="font-weight: bold;"> Download:</span> <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/InsertC.zip">InsertC.zip</a>
+(4Kb)<br>
+<span style="font-weight: bold;"> Installation:</span> No additional
+steps needed.<br>
+<span style="font-weight: bold;"> Description:</span> Inserts a copyright
+symbol (or replaces the current selection with a copyright symbol).<br>
+<span style="font-weight: bold;"> Issues:</span> None.<br>
+<a href="#top">Top</a><br>
+<h2><a name="Insert_Trademark_Symbol"></a>Insert Trademark Symbol</h2>
+<span style="font-weight: bold;"> Author:</span> <a
+ href="mailto:dfoster@openoffice.org">Duncan Foster</a><br>
+<span style="font-weight: bold;"> Aim:</span> Inserts a trademark symbol
+(or replaces the current selection with a trademark symbol).<br>
+<span style="font-weight: bold;"> Language:</span> Beanshell<br>
+<span style="font-weight: bold;"> Pre-requisites:</span> none<br>
+<span style="font-weight: bold;"> Download:</span> <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/InsertTM.zip">InsertTM.zip</a>
+(4Kb)<br>
+<span style="font-weight: bold;"> Installation:</span> No additional
+steps needed.<br>
+<span style="font-weight: bold;"> Description:</span> Inserts a trademark
+symbol (or replaces the current selection with a trademark symbol).<br>
+<span style="font-weight: bold;"> Issues:</span> None.<br>
+<a href="#top">Top</a><br>
+<h2><a name="Insert_Hidden_Text"></a>Insert Hidden Text<br>
+</h2>
+<span style="font-weight: bold;"> Author:</span> <a
+ href="mailto:dfoster@openoffice.org">Duncan Foster</a><br>
+<span style="font-weight: bold;"> Aim:</span> Inserts a hidden text field<br>
+<span style="font-weight: bold;"> Language:</span> Beanshell<br>
+<span style="font-weight: bold;"> Pre-requisites:</span> none<br>
+<span style="font-weight: bold;"> Download:</span> <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/InsertHiddenText.zip">InsertHiddenText.zip</a>
+(4Kb)<br>
+<span style="font-weight: bold;"> Installation:</span> No additional
+steps needed.<br>
+<span style="font-weight: bold;"> Description:</span> Replaces the
+currently selected text with a hidden text field with the same contents.<br>
+<span style="font-weight: bold;"> Issues:</span> None.<br>
+<a href="#top">Top</a><br>
+<h2><a name="Export_To_HTML"></a>Export To HTML<br>
+</h2>
+<span style="font-weight: bold;"> Author:</span> <a
+ href="mailto:jmrice@openoffice.org">John Rice</a><br>
+<span style="font-weight: bold;"> Aim:</span> Saves a copy of the
+document in HTML format.<br>
+<span style="font-weight: bold;"> Language:</span> Beanshell<br>
+<span style="font-weight: bold;"> Pre-requisites: </span>none<br>
+<span style="font-weight: bold;"> Download:</span> <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/ExportToHTML.zip">ExportToHTML.zip</a>
+(4Kb)<br>
+<span style="font-weight: bold;"> Installation:</span> No additional
+steps needed.<br>
+<span style="font-weight: bold;"> Description:</span> Saves a copy of the
+document in the user's home directory in HTML format. Does not change
+the type of the current document (as happens with "Save As").<br>
+<span style="font-weight: bold;"> Issues:</span> None.<br>
+<a href="#top">Top</a><br>
+<h2><a name="Combined_Utilities"></a>Combined Utilities</h2>
+<span style="font-weight: bold;">Aim:</span> A zip file containing all
+of the scripts above.<br>
+<span style="font-weight: bold;">Download:</span> <a
+ href="http://framework.openoffice.org/scripting/UtilityScripts/all.zip">all.zip</a>
+(550Kb)<br>
+<br>
+<a href="#top">Top</a><br>
+<br>
+<hr> Last Modified: 
+Fri Jun 20 15:28:18 BST 2003
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/utilities-download.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message