incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r799253 [12/16] - in /websites/staging/ooo-site/trunk/content/framework: documentation/ documentation/devmanual/ documentation/filters/ documentation/filterui/ documentation/mimetypes/ documentation/others/ drafts/ proposals/ proposals/appl...
Date Fri, 25 Nov 2011 20:05:43 GMT
Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/build-guide.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/build-guide.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/build-guide.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,617 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=iso-8859-1">
+  <title></title>
+  <meta name="GENERATOR" content="StarOffice 6.1 Beta 1 (Solaris Sparc)">
+  <meta name="CREATED" content="20030318;15201604">
+  <meta name="CHANGED" content="20030319;14323000">
+  <style>
+	<!--
+		@page { margin-left: 1.25in; margin-right: 1.25in; margin-top: 1in; margin-bottom: 1in }
+	-->
+	</style>
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<h1><a
+ name="Building the Scripting Framework for OpenOffice.org|outline"></a>
+Building the Scripting Framework for OpenOffice.org</h1>
+<h2>Contents</h2>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;">Building Scripting Framework </p>
+    <ul>
+      <li>
+        <p style="margin-bottom: 0in;"><a href="#Pre-requisites">Pre-requisites</a>
+        </p>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><a href="#projects">Projects
+&amp; Modifications</a> </p>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><a
+ href="#Building%20the%20Scripting%20Framework%20for%20OpenOffice.org%7Coutline">Building
+        </a> </p>
+      </li>
+    </ul>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Installation </p>
+    <ul>
+      <li>
+        <p style="margin-bottom: 0in;"><a href="#autoinstaller">Building
+Automated Installer</a></p>
+      </li>
+      <li>
+        <p><a href="#install">Manual&nbsp;install</a> </p>
+      </li>
+    </ul>
+  </li>
+</ul>
+<h2><a name="Pre-requisites"></a>Pre-requisites</h2>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;">JDK1.3 or greater </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">ANT which is available from <a
+ href="http://ant.apache.org/bindownload.cgi">http://ant.apache.org/bindownload.cgi</a>
+    </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Full OO1.1rc or later solver and
+installation set </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">OO1.1beta or later OpenOffice build
+environment</p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">bsh-1.2b7.jar available from <a
+ href="http://www.beanshell.org/download.html">http://www.beanshell.org/download.html</a></p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">NetBeans IDE - this is currently
+needed for the build (unless you modify one of the makefiles. It is
+intended to develop a makefile that will detect the presence or absence
+of the NetBeans IDEand react accordingly) </p>
+    <ul>
+      <li>
+        <p><a href="http://www.netbeans.org/ide/download.html">NetBeans
+3.4</a></p>
+      </li>
+    </ul>
+  </li>
+</ul>
+<h3>Setting up build environment </h3>
+<p>If you have not configured your environment with Java and Ant,
+please re-run the configure script from the <tt>config_office</tt>
+project&nbsp; including the options <tt>--with-jdk-home=&lt;JAVA_HOME&gt;
+&nbsp;--with-ant-home=&lt;ANT_HOME&gt;</tt> and source or run the
+environment set-up script. See the <a
+ href="http://tools.openoffice.org/">Tools</a>
+project homepage for details. </p>
+<p>If configure can not find Ant, after you have sourced or run the
+environment set-up script, &nbsp;you may need to add all jarfiles
+under <tt>&lt;ANT_HOME&gt;/lib</tt> to your <tt>$CLASSPATH</tt>.</p>
+<h2><a name="projects"></a>Making Scripting Framework Services and
+Interfaces available</h2>
+<p>If you only have solvers, you will need to checkout the following
+modules on a tag that is appropriate to the release you are building
+for (eg. <tt>OO1.1beta</tt>) </p>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;"><tt>unoil</tt> </p>
+  </li>
+  <li>
+    <p><tt>offapi</tt> </p>
+  </li>
+</ul>
+<p>The Scripting Framework is work-in-progress. For this reason it is
+not included in the main OpenOffice build &amp; install set. Thus, at
+this moment it is necessary to make several patches to the sources
+&amp;
+build a separate install set for the Scripting Framework. It is
+intended that at some point in the future the Scripting Framework
+will be integrated into OpenOffice. Since we will be modifying these
+projects, it is a good idea to backup your unoil and offapi modules
+and then checkout the following with the tag <tt>SF-OO644_ED02_1</tt></p>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;"><tt>scripting</tt> </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;"><tt>unoil/drafts/com/sun/star/script/framework
+(drafts/com/sun/star/script/framework,</tt>needs to be in the <tt>unoil
+    </tt>&nbsp;module) </p>
+  </li>
+  <li>
+    <p><tt>offapi/drafts/com/sun/star/script/framework&nbsp;(drafts/com/sun/star/script/framework,</tt>needs
+to be in the <tt>offapi</tt>&nbsp;module) </p>
+  </li>
+</ul>
+<p>You will need to modify the offapi and unoil modules so that the
+services and interfaces for scripting are available. </p>
+<h3><tt>offapi</tt> module</h3>
+<ol>
+  <li>
+    <p style="margin-bottom: 0in;">Ensure that you have the
+drafts/com/sun/star/script/framework directory under the offapi module,
+if you don't, you will need to check it out from CVS with the tag <font
+ face="Cumberland">SF-OO644_ED02_1</font></p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Modify the <tt>prj/build.lst</tt>,
+you will need to add the following lines </p>
+    <ul>
+      <li>
+        <p style="margin-bottom: 0in;"><tt>oa&nbsp;offapi\drafts\com\sun\star\script\framework\runtime&nbsp;nmake&nbsp;-&nbsp;all&nbsp;oa_scriptfruntime_drafts&nbsp;NULL</tt></p>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><tt>oa&nbsp;offapi\drafts\com\sun\star\script\framework\security&nbsp;nmake&nbsp;-&nbsp;all&nbsp;oa_sfsecurity_drafts
+NULL</tt> </p>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><tt>oa&nbsp;offapi\drafts\com\sun\star\script\framework\provider&nbsp;nmake&nbsp;-&nbsp;all&nbsp;oa_sfprovider_drafts&nbsp;NULL</tt>
+        </p>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><tt>oa&nbsp;offapi\drafts\com\sun\star\script\framework\storage&nbsp;nmake&nbsp;-&nbsp;all&nbsp;oa_sfstorage_drafts&nbsp;NULL</tt>
+        </p>
+      </li>
+    </ul>
+    <p style="margin-bottom: 0in;"><b>and add</b> "<font
+ face="Cumberland">oa_scriptfruntime_draft</font><tt><font
+ face="Cumberland">s&nbsp;oa_sfsecurity_drafts&nbsp;oa_sfprovider_drafts&nbsp;oa_sfstorage_drafts</font></tt>"
+to the last line before "<tt>NULL</tt>" </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Modify the <tt>prj/d.lst</tt>, you
+will need to add the following line <br>
+    <tt>..\%__SRC%\ucr\ScriptFramework.rdb&nbsp;%_DEST%\bin%_EXT%\ScriptFramework.rdb</tt>
+    <b>after</b> the line: <br>
+    <tt>..\%__SRC%\ucr\offapi.db&nbsp;%_DEST%\bin%_EXT%\offapi.rdb</tt>
+    </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Modify the <tt>util/makefile.mk</tt>
+and add the following to UNOIDLDBFILES list </p>
+    <ul>
+      <li>
+        <p style="margin-bottom: 0in;"><tt>$(UCR)$/dcssscriptfruntime.db&nbsp;\</tt>
+        </p>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><tt>$(UCR)$/dcsssfprovider.db&nbsp;\</tt>
+        </p>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><tt>$(UCR)$/dcsssfsecurity.db&nbsp;\</tt>
+        </p>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><tt>$(UCR)$/dcsssfstorage.db</tt>
+        </p>
+      </li>
+    </ul>
+  </li>
+  <li>Modify the <tt>util/makefile.mk</tt> and add the following line
+to the target <tt>$(UCR)$/types.db</tt><br>
+    <tt>+$(REGMERGE) $(UCR)$/ScriptFramework.rdb /
+$(UCR)$/dcssscriptfruntime.db $(UCR)$/dcsssfprovider.db
+$(UCR)$/dcsssfsecurity.db $(UCR)$/dcsssfstorage.db
+    </tt> </li>
+</ol>
+<h3><tt>unoil</tt> module</h3>
+<ol>
+  <li>
+    <p style="margin-bottom: 0in;">Modify <tt>prj/build.lst</tt> </p>
+    <ul>
+      <li>
+        <p style="margin-bottom: 0in;">Add <tt>ul_scriptf_drafts</tt>
+to the last line before <tt>NULL</tt> </p>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><tt>The line should now look
+something like this <br>
+ul&nbsp;unoil\drafts\com\sun\star\script\framework&nbsp;nmake&nbsp;-&nbsp;all&nbsp;ul_scriptf_drafts&nbsp;ul_ucb&nbsp;ul_frame&nbsp;ul_ucb&nbsp;NULL</tt>
+        </p>
+      </li>
+    </ul>
+  </li>
+</ol>
+<h2>Building the Scripting Framework module </h2>
+<h3><tt>scripting</tt> module</h3>
+<ol>
+  <li>
+    <p>Modify j<font face="Cumberland">ava/build.env</font> to point to
+the point to <font face="Thorndale">beanshell </font><font
+ face="Cumberland">bsh-1.2b7.jar</font>, ( see install.dir entry in
+build.env ) </p>
+  </li>
+  <li>
+    <p>Assuming you have NetBeans installed, modify the <tt>java/build.env</tt>
+to point at the NetBeans installation (see the openide.class.path entry
+in the build.xml for more details). </p>
+  </li>
+  <li>
+    <p>Alternatively, if you do not wish to build the add-in, delete
+the following entries from the depends section of the target "all" in
+the build.xml </p>
+    <ul>
+      <li>
+        <p>No NetBeans add-in </p>
+        <ul>
+          <li>
+            <p>localoffice.jar </p>
+          </li>
+          <li>
+            <p>netbeans.jar </p>
+          </li>
+        </ul>
+      </li>
+    </ul>
+  </li>
+</ol>
+<h3>Building</h3>
+<ol>
+  <li>
+    <p>Execute <tt>build</tt> and <font face="Cumberland">deliver</font>
+in the <tt>offapi</tt> module </p>
+  </li>
+  <li>
+    <p>Execute <tt>build and <font face="Cumberland">deliver</font> </tt>in
+the <tt>unoil</tt> module </p>
+  </li>
+  <li>
+    <p>Execute <tt>build</tt> in the <tt>scripting</tt> module </p>
+  </li>
+</ol>
+<h2><a name="autoinstaller"></a>Automated Installer</h2>
+<p>In <tt>scripting/workben</tt> there is an ANT build.xml file for
+compiling the examples installer, creating the UNO package, and
+creating a Jar file for an automated install. Running <tt>dmake</tt>
+in the <tt>scripting/workben</tt> directory should result in the
+creation of the <tt>SFrameworkInstall.jar</tt> in the <tt></tt>
+directory under the output directory appriate for your platform (eg.
+wntmsci9.pro).</p>
+<h2><a name="install"></a>Manual Installation of the Scripting
+Framework</h2>
+<p>The use of the automated installer, written in Java, is
+recommended, unless you're on a platform other than Solaris/SPARC,
+Linux/x86, Windows! It is recommended that even on such a platform
+that every effort should be made to get the installer to work. If
+this isn't possible the following is the set of steps needed to
+manually install the framework. The first stage in the manual
+installation is to build the <a
+ href="http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html">UNO
+package</a> containing the libraries &amp; Jar files. </p>
+<ol>
+  <li>
+    <p>Create a two directories (<tt>$pkgsf</tt>) for scripting
+framework and (<tt>$pkgbs</tt>) from beanshell support. </p>
+  </li>
+  <li>
+    <p>Create directories called <tt>$pkgsf/&lt;PLATFORM&gt;.plt </tt>and
+    <tt><font face="Cumberland">$pkgsf/skip_registration</font></tt>
+(Where <tt>&lt;PLATFORM&gt;</tt> is like linux_x86)<br>
+NOTE: A list of supported directories is available in the source file
+desktop/source/pkgchk/pkgchk_packages.cxx, you may need to modify this,
+if your platform is not supported </p>
+  </li>
+  <li>
+    <p>Copy in the libraries from <tt>scripting/&lt;platform&gt;/lib </tt>to
+    <tt><font face="Cumberland">$pkgsf/&lt;PLATFORM&gt;.plt</font></tt>
+    </p>
+  </li>
+  <li>
+    <p>Copy in <tt>ScriptRuntimeForJava.jar</tt> from <tt>scripting/&lt;platform&gt;/class</tt>
+into the top level directory, <tt>$pkgsf</tt> </p>
+  </li>
+  <li>
+    <p>Copy in <tt>unoil.jar </tt>from <tt><font face="Cumberland">$pkgsf/unoil/&lt;platform&gt;/class</font>
+    </tt>to <font face="Cumberland">$pkgsf/</font><tt><font
+ face="Cumberland">skip_registration</font></tt> directory</p>
+  </li>
+  <li>
+    <p>Copy <font face="Cumberland">ScriptRuntimeForBeanShell.jar</font>
+from <font face="Cumberland">scripting/&lt;platform&gt;/class</font>
+to <font face="Cumberland">$pkgbs</font></p>
+  </li>
+  <li>
+    <p>Copy <font face="Cumberland">bsh-1.2b7.jar</font>, available
+from <a href="http://www.beanshell.org/download.html">http://www.beanshell.org/download.html<span
+ style="text-decoration: none;"> </span></a>to <font face="Cumberland">$pkgbs/skip_registration</font>
+directory.</p>
+  </li>
+  <li>
+    <p>Copy <font face="Cumberland">ScriptFramework.rdb</font> from <font
+ face="Cumberland">offapi/&lt;platform&gt;/ucr/ScriptFramework.rdb</font>
+to <font face="Cumberland">$pkgsf</font></p>
+  </li>
+  <li>
+    <p>Copy <font face="Cumberland">ProtocolHandler.xcu</font> from <font
+ face="Cumberland">scripting/workben/installer/</font> to <font
+ face="Cumberland">$pkgsf</font></p>
+  </li>
+  <li>
+    <p>Now, zip up all files in directory, <font face="Cumberland">$pkgsf</font>
+to ooscriptf.zip</p>
+  </li>
+  <li>
+    <p>Now, zip up all file in directory, <font face="Cumberland">$pkgbs</font>
+to bshruntime.zip</p>
+  </li>
+</ol>
+<p>The next stage is to take the UNO packages and install them in an
+OpenOffice installation. </p>
+<ol>
+  <li>
+    <p>Copy the zips file into your OpenOffice installation under the <tt>user/uno_packages</tt>
+directory&nbsp; </p>
+  </li>
+  <li>
+    <p>In the program directory, run pkgchk on each of the zip files </p>
+  </li>
+</ol>
+<p><font face="Thorndale">The next stage is to install the
+Starbasic dialogs, configuration files and example scripts.</font></p>
+<ol>
+  <ol>
+    <li>
+      <p><font face="Thorndale">Create a directory </font><font
+ face="Cumberland"><tt>ScriptBindingLibrary</tt></font><font
+ face="Thorndale, serif">, from the directory <font face="Cumberland"><tt>scripting/workben/binding</tt></font><font
+ face="Thorndale"> copy the following files to </font><font
+ face="Cumberland"><tt>ScriptBindingLibrary</tt>,</font><font
+ face="Thorndale"> </font><font face="Cumberland"><tt>dialog.xlb</tt></font>,<font
+ face="Thorndale"> </font><font face="Cumberland"><tt>HelpBinding.xdl</tt></font><font
+ face="Thorndale">, </font><font face="Cumberland"><tt>MenuBinding.xdl</tt></font>,
+      <font face="Cumberland"><tt>script.xlb</tt></font>, <font
+ face="Cumberland"><tt>EventsBinding.xdl</tt></font>, <font
+ face="Cumberland"><tt>KeyBinding.xdl</tt></font>, </font><font
+ face="Cumberland"><tt>ScriptBinding.xba</tt></font></p>
+    </li>
+    <li>
+      <p><font face="Thorndale">Copy </font><font face="Cumberland"><tt>ScriptBindingLibrary</tt></font><font
+ face="Thorndale, serif"> <font face="Thorndale">directory and its
+contents to</font> <font face="Cumberland"><tt>&lt;OpenOffice
+path&gt;/user/basic</tt></font> <font face="Thorndale">directory.</font>
+      </font> </p>
+    </li>
+    <li>
+      <p><font face="Thorndale, serif"><font face="Thorndale">Insert
+the following lines into</font> <font face="Cumberland"><tt>&lt;OpenOffice
+path&gt;/user/basic/script.xlc</tt></font> </font><font
+ face="Thorndale">( insert these lines immediately above the entry for
+the Standard library) </font> </p>
+      <ol>
+        <p><tt><font face="Cumberland">&lt;library:library
+library:name="ScriptBindingLibrary" xlink:href="file:://&lt;OpenOffice
+path&gt;user/basic/ScriptBindingLibrary/script.xlb/"
+xlink:type="simple" library:link="false"/&gt;</font></tt></p>
+      </ol>
+    </li>
+    <li>
+      <p><font face="Thorndale">Insert this following lines into </font><font
+ face="Cumberland">&lt;OpenOffice path&gt;/user/basic/dialog.xlc</font>
+( insert these lines immediately above the entry for the Standard
+library) </p>
+      <ol>
+        <p><tt><font face="Cumberland">&lt;library:library
+library:name="ScriptBindingLibrary" xlink:href="file://&lt;OpenOffice
+path&gt;/user/basic/ScriptBindingLibrary/dialog.xlb/"
+xlink:type="simple" library:link="false"/&gt;</font></tt></p>
+      </ol>
+    </li>
+    <li>
+      <p><font face="Thorndale">Create a </font><font
+ face="Thorndale, serif"><font face="Cumberland"><tt>Scripts</tt></font><font
+ face="Thorndale"> directory, create sub-directories </font><font
+ face="Cumberland"><tt>java</tt></font><font face="Thorndale"> and <tt>beanshell</tt>
+in </font><font face="Cumberland"><tt>Scripts</tt></font><font
+ face="Thorndale"> directory. </font>
+Create sub directories <tt>MemoryUsage</tt>, <tt>InteractiveBeanShell</tt>
+in the <tt>beanshell</tt> directory. Copy the contents of each of the <tt>scripting/examples/beanshell</tt>
+directories into the newly created directories.
+Create sub directories <font face="Cumberland"><tt>Highlight</tt></font><font
+ face="Thorndale">, </font><font face="Cumberland"><tt>MemoryUsage</tt></font><font
+ face="Thorndale"> and </font><font face="Cumberland"><tt>ScriptFrmwrkHelper</tt></font></font><font
+ face="Thorndale"> in the <tt>java</tt> directory. </font> Using the
+tables below populate the <tt>java</tt> directory with the appropriate
+files<font face="Thorndale"> ( make sure to rename files where
+necessary )</font></p>
+      <table width="100%" border="1" cellpadding="4" cellspacing="3">
+        <col width="97*"> <col width="159*"> <thead> <tr valign="top">
+          <th width="38%">
+          <p>Source (scripting/examples/java)</p>
+          </th>
+          <th width="62%">
+          <p>Destination file</p>
+          </th>
+        </tr>
+        </thead> <tbody>
+          <tr valign="top">
+            <td width="38%">
+            <p>HighlightTextParcel.xml</p>
+            </td>
+            <td width="62%">
+            <p>&lt;OpenOffice
+Path&gt;/user/Scripts/java/Highlight/parcel-descriptor.xml</p>
+            </td>
+          </tr>
+          <tr valign="top">
+            <td width="38%">
+            <p>HighlightUtil.java</p>
+            </td>
+            <td width="62%">
+            <p>&lt;OpenOffice
+Path&gt;/user/Scripts/java/Highlight/HighlightUtil.java</p>
+            </td>
+          </tr>
+          <tr valign="top">
+            <td width="38%">
+            <p>HighlightText.java </p>
+            </td>
+            <td width="62%">
+            <p>&lt;OpenOffice
+Path&gt;/user/Scripts/java/Highlight/HighlightText.java </p>
+            </td>
+          </tr>
+          <tr valign="top">
+            <td width="38%">
+            <p>MemoryUsage.java</p>
+            </td>
+            <td width="62%">
+            <p>&lt;OpenOffice
+Path&gt;/user/Scripts/java/MemoryUsage/MemoryUsage.java</p>
+            </td>
+          </tr>
+          <tr valign="top">
+            <td width="38%">
+            <p>MemoryUsageParcel.xml</p>
+            </td>
+            <td width="62%">
+            <p>&lt;OpenOffice
+Path&gt;/user/Scripts/java/MemoryUsage/parcel-descriptor.xml</p>
+            </td>
+          </tr>
+          <tr valign="top">
+            <td width="38%">
+            <p>ScriptFrmwrkHelper.java</p>
+            </td>
+            <td width="62%">
+            <p>&lt;OpenOffice
+Path&gt;/user/Scripts/java/ScriptFrmwrkHelper/ScriptFrmwrkHelper.java</p>
+            </td>
+          </tr>
+          <tr valign="top">
+            <td width="38%">
+            <p>ScriptFrameWkHelperParcel.xml</p>
+            </td>
+            <td width="62%">
+            <p>&lt;OpenOffice
+Path&gt;/user/Scripts/java/ScriptFrmwrkHelper/parcel-descriptor.xml</p>
+            </td>
+          </tr>
+        </tbody>
+      </table>
+    </li>
+    <li>
+      <p><font face="Thorndale">Build example and framework helper
+scripts. Create a classpath with the following jars </font><font
+ face="Cumberland"><tt>&lt;SOLVERPATH&gt;/&lt;platform&gt;/bin/unoil.jar</tt></font>,<font
+ face="Cumberland"><tt>&lt;SOLVERPATH&gt;/&lt;platform&gt;/bin/jurt.jar</tt></font>,
+      <tt><font face="Cumberland">&lt;SOLVERPATH&gt;/&lt;platform&gt;/</font><font
+ face="Cumberland">bin/jut.jar</font></tt>, <tt><font face="Cumberland">&lt;SOLVERPATH&gt;/&lt;platform&gt;/bin/java_uno.jar</font></tt>,
+      <tt><font face="Cumberland">&lt;SOLVERPATH&gt;/&lt;platform&gt;/bin/ridl.jar</font></tt>,
+      <tt><font face="Cumberland">&lt;SOLVERPATH&gt;/&lt;platform&gt;/bin/sandbox.jar</font></tt>.
+      <font face="Thorndale"> Change directory to </font><font
+ face="Cumberland"><tt>Highlight</tt></font>, <font face="Cumberland"><tt>MemoryUsage</tt></font>
+and <font face="Cumberland"><tt>ScriptFrmwrkHelper</tt></font> <font
+ face="Thorndale">in turn, building all java files in each one. Jar up
+the class files in each directory creating </font><font
+ face="Cumberland"><tt>ScriptFrmwrkHelper.jar</tt></font><font
+ face="Thorndale"> in </font><font face="Cumberland"><tt>ScriptFrmwrkHelper</tt></font>,
+      <font face="Cumberland"><tt>Highlight.jar</tt></font> in <font
+ face="Cumberland"><tt>Highlight</tt></font> and finally <font
+ face="Cumberland"><tt>MemUsage.jar</tt></font> in <font
+ face="Cumberland"><tt>MemoryUsage</tt></font>.</p>
+    </li>
+    <li>
+      <p>Copy the entire <font face="Cumberland"><tt>Scripts</tt></font>
+directory hierarchy to <font face="Cumberland"><tt>&lt;OpenOffice
+Path&gt;/user/</tt></font></p>
+    </li>
+    <li>
+      <p>Install the configuration files. Firstly backup any config
+files ( *.xml ) present in the <font face="Cumberland"><tt>&lt;OpenOffice
+Path&gt;/user/config/soconfig</tt> directory</font> ( including
+sub-directories ). Copy all files with &#8220;.xml&#8221; extention ( except <font
+ face="Cumberland"><tt>manifest.xml</tt></font> ) from <font
+ face="Cumberland"><tt>scripting/workben/bindings to &lt;OpenOffice
+Path&gt;/user/config/soconfig</tt></font>. If <font face="Cumberland"><tt>&lt;OpenOffice
+Path&gt;/user/config/soconfig/META-INF</tt></font> directory doesn't
+exist create it. Copy <font face="Cumberland"><tt>manifest.xml</tt></font>
+from directory <font face="Cumberland"><tt>scripting/workben/bindings</tt></font>
+to <font face="Cumberland"><tt>&lt;OpenOffice
+Path&gt;/user/config/soconfig/META-INF</tt></font> directory.</p>
+    </li>
+  </ol>
+</ol>
+<p>The script framework is now installed.</p>
+<table cellpadding="4" cellspacing="0">
+  <tbody>
+    <tr>
+      <td width="25%">
+      <p><a href="mailto:dev@framework.openoffice.org">Mailing List</a></p>
+      </td>
+      <td width="75%">
+      <p>Installation, User or Developer queries on the Office
+Scripting Framework</p>
+      </td>
+    </tr>
+    <tr>
+      <td width="25%">
+      <p>Issues</p>
+      </td>
+      <td width="75%">
+      <p>Issues found in the Office Scripting Framework should be
+logged in Issuezilla<br>
+      <b>component:</b> framework<br>
+      <b>subcomponent:</b> scripting</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<h2><br>
+Last revision: Wed Mar 19 17:39:14 GMT 2003
+</h2>
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/commandline-devguide.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/commandline-devguide.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/commandline-devguide.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,222 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <title>Developing Scripts on the Command Line</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<a name="top"></a>
+<h1>Developing Scripts on the Command Line</h1>
+For users who do not wish to develop their Office Scripts using an IDE
+there is a simple command line interface built into the Office Scripting
+module which can be used for the generation and deployment of Office
+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>
+<a name="prereqs"> </a>
+<h2><a name="prereqs">Prerequisites</a></h2>
+<ul>
+  <li><a name="prereqs">The Scripting module office.jar file should be
+included in the classpath. You can unpack this file from the Scripting
+Framework installer </a><a href="SFrameworkInstall.jar">SFrameworkInstall.jar</a>
+by running the following command:
+    <p> <font face="Courier, monospace" size="2"> jar xf
+SFrameworkInstall.jar ide/office.jar </font> </p>
+  </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>-g [Path to Parcel directory] [options]</b> </a>
+  <p> <a name="usage">Generates a Script Parcel for the given the
+parcel directory. 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>-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. 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;Office Installation&gt;/user/Scripts or
+&lt;Office 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 Office 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 Office 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 Office scripts, and
+adding the classpath property to each Office 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 Office scripts, and
+adding the classpath and the secondprop properties to each Office
+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 Office script.</a></li>
+</ul>
+<p><a href="#top">Top</a> </p>
+<hr> Last Modified: Tue Mar 12 11:40:28 GMT 2003
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/developer-guide.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/developer-guide.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/developer-guide.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,246 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <title>Writing Scripts in BeanShell and Java</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<h1>Writing Scripts in BeanShell 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 Office Scripts and the XScriptContext
+type</a> </p>
+  </li>
+  <li>
+    <p><a href="#tips">Tips on writing Office 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;<br>    import com.sun.star.text.*;<br>    import com.sun.star.uno.UnoRuntime;<br>    import drafts.com.sun.star.script.framework.XScriptContext;<br><br>    model = context.getDocument(); <br>    textdoc = (XTextDocument)<br>        UnoRuntime.queryInterface(XTextDocument.class, model);<br><br>    oText = textdoc.getText(); <br>    oCursor = oText.createTextCursor(); <br>    oText.insertString(oCursor, "Hello World", false)<br></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>Create a file called hello.bsh and put the above code in the
+file. </li>
+  <li>Start OpenOffice.org and open a new Writer document. </li>
+  <li>Select the Tools/Scripting Add-ons/Edit/Debug Scripts... menu
+item. </li>
+  <li>In the Edit/Debug Scripts dialog that appears select BeanShell as
+your language and FileSystem as your location. Click on the Browse...
+button. </li>
+  <li>In the file selection dialog that pops up, navigate to your
+hello.bsh file and select it. Now click OK. </li>
+  <li>A BeanShell Debugger window will appear with the contents of your
+hello.bsh script loaded. Click on the Run button.<br>
+    <div style="text-align: center;"><img src="beanshell.gif" title=""
+ alt="" style="width: 477px; height: 319px;"><br>
+    </div>
+  </li>
+  <li>You should see Hello World appear at the start of the Writer
+document. </li>
+</ul>
+<p> You can modify the code directly in the evaluation window and click
+eval again to test it. When you are finished making your changes, click
+Save to save them back to the hello.bsh file. 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);<br>importClass(Packages.com.sun.star.text.XTextDocument);<br><br>var oModel = XSCRIPTCONTEXT.getDocument(); <br>var oTextdoc = UnoRuntime.queryInterface(XTextDocument, oModel);<br>var oText = oTextdoc.getText(); <br>var oCursor = oText.createTextCursor(); <br><br>oText.insertString(oCursor, "Hello World", false);<br></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
+Office 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 file called hello.js and put the JavaScript code in the
+file. </li>
+  <li>Select the Tools/Scripting Add-ons/Edit/Debug Scripts... menu
+item. </li>
+  <li>In the Edit/Debug Scripts dialog select JavaScript as your
+language and FileSystem as your location. Click on the Browse...
+button. </li>
+  <li>In the file selection dialog that pops up, navigate to your
+hello.js file and select it. Click OK. </li>
+  <li>A Rhino Debugger window will appear with the contents of your
+hello.js script loaded. To run the script select File/Run and then
+click on the Go button.<br>
+    <div style="text-align: center;"><img src="rhino.gif" title=""
+ alt="" style="width: 640px; height: 646px;"><br>
+    </div>
+  </li>
+  <li>You can change the script and save your changes using the
+File/Save menu item. </li>
+</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;<br>    import com.sun.star.text.*;<br>    import com.sun.star.uno.UnoRuntime;<br>    import drafts.com.sun.star.script.framework.XScriptContext;<br><br>    public class MyClass {<br><br>        // The script method must be public<br>        // It can either be static or non-static<br><br>        public void showForm(XScriptContext xSc) {<br><br>            // getting the text document object<br>            XModel xmodel = xSc.getDocument();<br><br>            XTextDocument xtextdoc = (XTextDocument)<br>                UnoRuntime.queryInterface(XTextDocument.class, xmodel);<br>            XText xtext = xtextdoc.getText();<br>            XTextCursor xtextcursor = xtext.createTextCursor();<br><br>            xtext.insertString(xtextcursor, "Hello World", false);<br>        }<br>    }<br></pre>
+</font> </p>
+<p> Office 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
+Office scripts in Java. </p>
+<p> <a href="#top">Top</a> <a name="context"></a> </p>
+<h2>Writing Office scripts and the XScriptContext type</h2>
+The XScriptContext type is used to obtain the the document context,
+desktop and component factory from an Office script. Any public Java
+method which accepts XScriptContext as it's first parameter can be
+executed as an Office 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>Office Desktop - access the desktop of the running Office
+    <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.framework.XScriptContext;<br></pre>
+</font>
+<p> <a href="#top">Top</a> <a name="tips"></a> </p>
+<h2>Tips on writing Office 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 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;<br>&lt;!-- DTD for Parcel Meta data for use in the OpenOffice.org Scripting Framework Project --&gt;<br>&lt;!ELEMENT logicalname EMPTY&gt;<br>&lt;!ELEMENT description (#PCDATA)&gt;<br>&lt;!ELEMENT displayname EMPTY&gt;<br>&lt;!ELEMENT locale (displayname?, description?)&gt;<br>&lt;!ELEMENT functionname EMPTY&gt;<br>&lt;!ELEMENT prop EMPTY&gt;<br>&lt;!ELEMENT languagedepprops (prop+)&gt;<br>&lt;!ELEMENT file (prop*)&gt;<br>&lt;!ELEMENT fileset (file+)&gt;<br>&lt;!ELEMENT script (locale+, functionname, logicalname, languagedepprops*, fileset*)&gt;<br>&lt;!ELEMENT parcel (script+)&gt;<br>&lt;!ATTLIST logicalname<br>	value CDATA #REQUIRED<br>&gt;<br>&lt;!ATTLIST displayname<br>	value CDATA #REQUIRED<br>&gt;<br>&lt;!ATTLIST locale<br>	lang CDATA #REQUIRED<br>&gt;<br>&lt;!ATTLIST functionname<br>	value CDATA #REQUIRED<br>&gt;<br>&lt;!ATTLIST logicalname<br>	value CDATA #REQUIRED<br>&gt;<br>&lt;!ATTLIST prop<br>	name CDATA #REQUIRED
 <br>	value CDATA #REQUIRED<br>&gt;<br>&lt;!ATTLIST file<br>	name CDATA #REQUIRED<br>&gt;<br>&lt;!ATTLIST fileset<br>	name CDATA #IMPLIED<br>&gt;<br>&lt;!ATTLIST script<br>	language CDATA #REQUIRED<br>&gt;<br>&lt;!ATTLIST parcel<br>	language CDATA #REQUIRED<br>&gt;<br></pre>
+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;<br>&lt;!--Sample Meta Data for use with the Scripting Framework Project in OpenOffice.org --&gt;<br>&lt;!DOCTYPE parcel SYSTEM "parcel.dtd"&gt;<br>&lt;parcel language="Java"&gt;<br>	&lt;script language="Java"&gt;<br>		&lt;locale lang="english"&gt;<br>			&lt;displayname value="Memory.usage"/&gt;<br>			&lt;description&gt;<br>				Displays the memory current memory usage<br>			&lt;/description&gt;<br>		&lt;/locale&gt;<br>		&lt;functionname value="memoryUtils.memoryUsage"/&gt;<br>		&lt;logicalname value="MemoryUtils.MemUsage"/&gt;<br>		&lt;languagedepprops&gt;<br>			&lt;prop name="classpath" value="/opt/foo.jar:/usr/java/src.jar"/&gt;<br>		&lt;/languagedepprops&gt;<br>		&lt;fileset&gt;<br>			&lt;file name="mems.txt"&gt;<br>				&lt;prop name="type" value="resource"/&gt;<br>			&lt;/file&gt;<br>		&lt;/fileset&gt;<br>	&lt;/script&gt;<br>&lt;/parcel&gt;<br></pre>
+<a href="#top">Top</a>
+<hr> Last Modified: 
+Fri Jun 20 15:28:34 BST 2003
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/developer-release-features.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/developer-release-features.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/developer-release-features.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,167 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <title>Features for Early Developer Release</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<h2>New Features in Release 0.3</h2>
+<ul>
+  <li>
+    <p><span style="font-weight: bold;">JavaScript/Rhino runtime<br>
+    <br>
+    </span>This release includes a JavaScript Script runtime based on <a
+ href="http://www.mozilla.org/rhino/">Rhino</a> (used under the <a
+ href="http://www.mozilla.org/MPL/MPL-1.1.html">Mozilla Public License</a>)</p>
+  </li>
+  <li style="font-weight: bold;">Enhanced Debugging support for
+BeanShell &amp; JavaScript scripts<br>
+    <br>
+    <span style="font-weight: normal;">The Tools-&gt;Scripting Add-ons
+menu now contains a new item <a href="user-guide.html#editdebug">"Edit/Debug
+Scripts"</a>, that allows the user to edit and debug BeanShell &amp;
+JavaScript scripts.&nbsp; This required a modification to the Rhino
+class org.mozilla.javascript.tools.debugger.Main. These modifications
+are included in the Jar file, and are also available via the <a
+ href="http://framework.openoffice.org/source/browse/framework/scripting/examples/java/debugger/rhino/Main.java">source
+browser</a>.<br>
+    </span></li>
+</ul>
+<ul>
+  <li><span style="font-weight: bold;">Support for filesystem scripts<br>
+    <br>
+    </span>Users can bind to and run BeanShell &amp; Javacript scripts
+located at any point on their <a href="user-guide.html#filesys">filesystem</a>.
+These scripts do not need to have an associated parcel-descriptor.xml.<br>
+  </li>
+</ul>
+<h2>New Features in Release 0.2<br>
+</h2>
+<ul>
+  <li>
+    <p><b>Additional language support</b> </p>
+    <p> Added support for <a href="http://www.beanshell.org/home.html">BeanShell</a>,
+a loosely typed Java based scripting language supported by NetBeans.
+The Interactive BeanShell Scripting Window available from
+Tools-&gt;Scripting Add-ons allows you to experiment with Office
+scripting without needing to recompile your scripts. </p>
+    <p> This is an example of the implementation of an additional
+script
+runtime, in this case based on Java runtime (see <a
+ href="runtime-howto.html">How to write a runtime</a> for more
+information on writing runtimes). </p>
+  </li>
+  <li>
+    <p><b>Security Enhancements</b> </p>
+    <p> Script execution by the scripting framework now honors the <a
+ href="user-guide.html#Leveraging_StarBasic_Security">security</a>
+settings in Tools -&gt; Options -&gt; Security Settings. (ie. your
+existing settings for StarBasic macros). </p>
+  </li>
+  <li>
+    <p><b>Support for storage of bindings in documents</b> </p>
+    <p> With this release script bindings can now also be stored in
+documents as well as in your OpenOffice.org user directory (see the <a
+ href="release-notes.html">release notes</a> for instructions). </p>
+  </li>
+  <li>
+    <p><b>Support for Event Bindings</b> </p>
+    <p> <a href="user-guide.html#bindscripts">Assign dialogs</a> have
+been enhanced to allow bindings to events as well as to menu items and
+keys. </p>
+  </li>
+</ul>
+<p><b>Notes:</b> </p>
+<ul>
+  <li>New binding assignments can be made without requiring a restart
+of OpenOffice.org </li>
+  <li>Scripts bindings are now fully resolved at binding </li>
+  <li>Command line utilities have been added for packaging and
+deployment (see <a href="commandline-devguide.html"> Developing
+Scripts
+without an IDE</a>) </li>
+  <li>Support for jEdit IDE has been discontinued </li>
+</ul>
+<h2>Features of the Office Scripting Framework</h2>
+<h2>Scripting Framework</h2>
+Enables Office scripting in a language of your choice through support
+for different language Runtimes. The current release provides Java and
+BeanShell Runtimes. The Scripting Framework is designed to allow
+Runtimes for other languages (for which a UNO bridge exists) to be
+developed and deployed easily. Runtimes for Java based languages use
+the
+Java UNO bridge.
+<h2>Script Development and IDE support</h2>
+A NetBeans module is provided which can be used to create Office
+scripts. Scripts can be deployed to a document or to an OpenOffice.org
+installation (user or share area). By installing the ODK for
+OpenOffice.org, the user has full access to online help and code
+completion within any scripts they are writing.
+<p> Debugging of scripts is possible in NetBeans for Java scripts. For
+more information on setting up OpenOffice.org to enable debugging see <a
+ href="http://api.openoffice.org/common/man/IDEintegration/OfficeNetBeansIntegration.html#Debugging">
+Debugging Java components in NetBeans/Forte for Java</a> </p>
+<p> <b>Note:</b> The BeanShell scripting language does not support
+source level debugging it is not possible to debug Office scripts
+written in BeanShell from NetBeans. It is recommended to use the
+Interactive BeanShell Scripting Window when developing while BeanShell
+scripts. </p>
+<h2>Executing Scripts</h2>
+Scripts can be executed from key combinations, selecting menu item or
+events (document or application). Assign dialogs (written in StarBasic)
+allow the user to bind scripts available in document or OpenOffice.org
+installation to key combination, menu items or events (document or
+application). Bindings can be stored in documents or an OpenOffice.org
+installation.
+<h2>Security</h2>
+The security settings of the Scripting Framework honor the existing
+StarBasic security settings available in Tools -&gt; Options -&gt;
+Security Settings. <br>
+<hr> Last Modified: Fri Jun 20 15:27:16 BST 2003
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/edit-debug.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/edit-debug.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/faq.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/faq.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/faq.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/index.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/index.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/index.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,282 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<h1>Language Independent Office 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>
+<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
+scripts in any supported scripting language to manipulate
+OpenOffice.org. </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
+Early Developer Release (Version 0.3)</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><a href="./developer-release-features.html">Features</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Features of the Early Developer Release</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./SFrameworkInstall.jar">Download</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Download the Office Scripting Framework (2 MB). Refer to the
+install section for installation guidelines. <span
+ style="color: rgb(255, 0, 0);">Updated to work with
+OpenOffice.org1.1rc1 and later</span><br>
+      </p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./install-guide.html">Install</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Installation Guide for the Office Scripting Framework</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./uninstall-guide.html">Uninstall</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Guide for Uninstalling the Office Scripting Framework</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>
+      <td style="vertical-align: top;"><a href="./faq.html">FAQ</a></td>
+      <td style="vertical-align: top;" colspan="5">Frequently Asked
+Questions for the Office Scripting Framework</td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./release-notes.html">Release Notes</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Release Notes</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td width="270">
+      <p><a href="./SmokeTest.html">Test</a></p>
+      </td>
+      <td colspan="5" width="566">
+      <p>Guidelines for testing the Framework &#8211; Description of basic
+sanity tests (smoke tests) for the framework.</p>
+      </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>Upcoming features in future releases of the Office 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.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 Office
+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 Office 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: 
+Mon Sep 15 16:59:44 BST 2003
+</p>
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/install-guide.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/install-guide.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/install-guide.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,251 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <title>Installation and User Guide</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<a name="top"></a>
+<h1>Installation Guide for the Office Scripting Framework</h1>
+<h2>Contents</h2>
+<ul>
+  <li>
+    <p><a href="#who">Who Should Read This Document</a> </p>
+  </li>
+  <li>
+    <p><a href="#prerequisites">Pre-requisites</a> </p>
+  </li>
+  <li>
+    <p><a href="#download">Downloading the Scripting Framework</a> </p>
+  </li>
+  <li>
+    <p><a href="#install">Installing the Scripting Framework</a></p>
+  </li>
+  <li><a href="#Installing_the_Scripting_Framework_in_a_">Installing
+the Scripting Framework in a Network Installation of
+OpenOffice.org</a></li>
+</ul>
+<a name="who"></a>
+<h2>Who Should Read This Document</h2>
+This document should be read by:
+<ul>
+  <li>
+    <p>Application Developers who wish to enhance OpenOffice.org
+functionality without needing to develop UNO components or to connect
+to
+OpenOffice.org from a remote JVM </p>
+  </li>
+  <li>
+    <p>OpenOffice.org users who wish to execute Office scripts via
+menu, key and event bindings in OpenOffice.org </p>
+  </li>
+</ul>
+<a href="#top">Top</a> <a name="prerequisites"></a>
+<h2>Pre-requisites</h2>
+<ul>
+  <li>This is an Early Developer Release of the Office Scripting
+Framework provided for users and developers of OpenOffice.org to try
+out
+and provide feedback. Future releases of the Framework may change. </li>
+  <li>This release of the Scripting Framework runs on <a
+ href="http://www.openoffice.org/dev_docs/source/1.1rc/index.html"> <b>OpenOffice.org
+1.1 rc</b></a> and above. </li>
+  <li>The Scripting Framework is currently available in English only. </li>
+</ul>
+The table below shows the JDK and memory requirements for running the
+Office Scripting Framework.
+<p> </p>
+<center>
+<table colspan="4" cellpadding="5" border="1">
+  <tbody>
+    <tr>
+      <th>User</th>
+      <th>IDE</th>
+      <th>JDK required</th>
+      <th>Memory required</th>
+    </tr>
+    <tr>
+      <td>Script User</td>
+      <td>-</td>
+      <td>1.4.0_02</td>
+      <td>256MB</td>
+    </tr>
+    <tr>
+      <td>Script Developer</td>
+      <td>NetBeans 3.4</td>
+      <td>1.4.0_02</td>
+      <td>512MB</td>
+    </tr>
+  </tbody>
+</table>
+</center>
+<a href="#top">Top</a> <a name="download"></a>
+<h2>Downloading the Scripting Framework</h2>
+The Scripting Framework is available for download in the form of a Jar
+file which can be obtained from <a href="SFrameworkInstall.jar">here</a>.
+The contents of the Jar file are as follows:
+<ul>
+  <li><b>installer</b> - A platform-independent installer for the
+Scripting Framework written in Java. </li>
+  <li><b>bindingdialog</b> - A collection of StarBasic dialogs to
+enable
+the user to assign (bind) scripts to menu and key items, and to
+document
+and application events. This directory also contains the necessary XML
+files for the menu items that invoke these StarBasic dialogs. </li>
+  <li><b>examples</b> - Example scripts written in Java, JavaScript
+&amp; BeanShell.</li>
+  <li><span style="font-weight: bold;">schema</span> - Contains the
+registry schema file for the Scripting Framework data.<br>
+  </li>
+  <li><b>sframework</b></li>
+  <ul>
+    <li><b>ooscriptframe.zip</b>&nbsp; - A UNO package containing the
+core Scripting Framework libraries &amp; Jar files. This also contains
+the Java script runtime.<br>
+    </li>
+    <li><b>bshruntime.zip</b> - A UNO package containing the BeanShell
+script runtime.<br>
+    </li>
+    <li><b>jsruntime.zip</b> - A UNO package containing the JavaScript
+script runtime.<br>
+    </li>
+  </ul>
+  <li><b>ide</b> - The Jar files for NetBeans integration. </li>
+</ul>
+<!--
+<p>
+<sup>*</sup>See <a href="http://api.openoffice.org/servlets/ProjectDownloadList?action=download&amp;dlID=84">
+&sect;4.7.1</a> of the
+<a href="http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html">
+Office Developers' Guide</a> for a description of the UNO packaging system.
+<p>
+--><a
+ href="#top">Top</a> <a name="install"></a>
+<h2>Installing the Scripting Framework</h2>
+Before you begin installation, you need to ensure all Office processes
+have terminated and on Windows and Linux, that the QuickStarter has
+been
+closed. <br>
+<br>
+<span style="color: rgb(255, 0, 0);"><span style="font-weight: bold;">Note:</span>
+<span style="color: rgb(51, 0, 0);">Unlike previous releases, release
+0.3
+must be installed by the same user who installed OpenOffice.org, ie.
+the
+Administrator in the case of a network installation. This requirement
+is
+due to the fact that release 0.3 contains a schema extension to the
+OpenOffice.org registry which must be installed under </span></span><font
+ face="Courier, monospace" size="2">&lt;Office Installation&gt;/share.</font><br>
+<br>
+<b>Note:</b> Before installing an updated version of the Scripting
+Framework, the previous version should be removed. (See the <a
+ href="uninstall-guide.html">Guide for Uninstalling</a>)
+<p> To install the Scripting Framework: </p>
+<ul>
+  <li>Open a terminal (Linux/UNIX) or DOS Command Prompt (Windows) </li>
+  <li>Ensure that java is in your execution path </li>
+  <li>Run the command: <font face="Courier, monospace" size="2">java
+-jar SFrameworkInstall.jar</font> </li>
+</ul>
+<p> This will start the installer GUI, which you can use to select the
+Office installation to which you want to install the Scripting
+Framework. The framework is installed in the &lt;Office
+Installation&gt;/user/uno_packages directory of the Office installation
+you choose. If the installer detects an installation of either <a
+ href="http://www.netbeans.org/devhome/docs/releases/builds_archive/release_archive.html">
+NetBeans 3.4</a> you will be asked whether you wish to install the IDE
+Add-ins. These add-ins provide support for developing and deploying
+Office Scripts. </p>
+<p> <b>Note:</b> If you do not wish to use the GUI you can install the
+Scripting Framework and the IDE Add-in via the command line using the
+command: </p>
+<p> <font face="Courier, monospace" size="2"> java -jar
+SFrameworkInstall.jar -office &lt;Office Installation&gt; -netbeans
+&lt;NetBeans Installation&gt;</font> </p>
+<p> <b>Note:</b> The installer detects IDE installations by looking
+for
+session related files in the home directory of the user running the
+install, so in order for your IDE to be detected you will need to have
+run it at least once.<br>
+</p>
+<h2><a name="Installing_the_Scripting_Framework_in_a_"></a>Installing
+the Scripting Framework in a Network Installation of
+OpenOffice.org</h2>
+Installing the Scripting Framework into an OpenOffice.org network
+installation can only be done via the command line. the installation
+done as a two-part process.First (after installing the OpenOffice.org,
+the <font face="Courier, monospace" size="2">setup -net</font> part)
+install the components and shared scripts, macros
+etc:<br>
+<br>
+<font face="Courier, monospace" size="2"> java -jar
+SFrameworkInstall.jar -office &lt;Shared Office Installation&gt; -net<br>
+<br>
+</font>then as each user, once
+the user has installed OpenOffice.org (<font face="Courier, monospace"
+ size="2">setup</font> from the shared installation), add the menu
+bindings to the
+Scripting Framework dialogs:<br>
+<br>
+<font face="Courier, monospace" size="2"> java -jar
+SFrameworkInstall.jar -office &lt;User </font><font
+ face="Courier, monospace" size="2">Office Installation&gt; -bindings<br>
+<br>
+</font>
+This is currently not working on Linux due to a bug in the Linux release of 
+OpenOffice.org1.1rc. It 
+is expected that this will be fixed by the next release.
+<p> </p>
+<p> <b>Update:</b> The network install in current download is broken, this will be fixed as soon as possible.</p>
+<p> <a href="#top">Top</a> </p>
+<hr> Last Modified: 
+Tue Sep 16 18:48:26 BST 2003
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>



Mime
View raw message