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 [10/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/build-guide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/build-guide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/build-guide.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/build-guide.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,285 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+  <style>
+	<!--
+		@page { margin-left: 3.18cm; margin-right: 3.18cm; margin-top: 2.54cm; margin-bottom: 2.54cm }
+	-->
+	</style>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+  <body lang="en-US">
+                      
+<h1>Building the Scripting Framework &nbsp;for &nbsp;OpenOffice.org</h1>
+                 
+<h2>Contents</h2>
+             
+<ul>
+    <li>Building Scripting Framework</li>
+    <ul>
+        <li><a href="#Pre-requisites">Pre-requisites</a></li>
+        <li><a href="#projects">Projects &amp; Modifications</a></li>
+        <li><a href="#build">Building</a></li>
+    </ul>
+    <li>Installation</li>
+    <ul>
+        <li><a href="#autoinstaller">Building Automated Installer</a><br>
+        <li><a href="#install">Manual&nbsp;install</a></li>
+    </ul>
+</ul>
+                
+<h2><a name="Pre-requisites"></a>Pre-requisites</h2>
+<p>
+<ul>
+    <li>JDK1.3 or greater</li>
+    <li>ANT which is available from <a href="http://jakarta.apache.org/builds/jakarta-ant/release">http://jakarta.apache.org/builds/jakarta-ant/release</a></li>
+    <li>Full OO643C or later solver and installation set</li>
+    <li>OO643C or later OpenOffice build environment (see: <a
+href="http://www.openoffice.org/dev_docs/source/643c/">643C Developer Release</a>)</li>
+    <li>IDE - these are 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 either of the IDEs specified below are react accordingly)</li>
+    <ul>
+        <li><a href="http://www.netbeans.org/ide/download.html">NetBeans 3.4</a></li>
+        <li><a href="http://www.jedit.org/index.php?page=download">jEdit 4.0.3</a> (plus additional modules, see the guide for developing scripts using<a href="http://framework.openoffice.org/scripting/jedit-devguide.html">jEdit</a>for details)</li>
+    </ul>
+</ul>
+</p>
+<h2><a name="projects"></a>Projects &amp; Modifications</h2>
+<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.</p>
+<p>If configure can not find Ant, after you have sourced 
+or  run   the environment set-up script, &nbsp;you may need add all jarfiles
+under  <tt>&lt;ANT_HOME&gt;/lib</tt> to your <tt>$CLASSPATH</tt>.</p>
+<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>OO643C</tt>)
+<ul>
+    <li><tt>unoil</tt></li>
+    <li><tt>offapi</tt></li>
+</ul>
+The Scripting Framework is work-in-progress. For this reason it is not included in the main OpenOffice build & install set. Thus, at this moment it is necessary to make several patches to the sources & build a separate install set for the Scripting Framework. It is intended that at some point in the future is 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-OO643C</tt><br>
+                   
+<ul>
+    <li><tt>scripting</tt></li>
+    <li><tt>unoil/drafts/com/sun/star/script (drafts/com/sun/star/script,</tt>needs to be in the <tt>unoil </tt>&nbsp;module)</li>
+    <li><tt>offapi/drafts/com/sun/star/script&nbsp;</tt><tt>(drafts/com/sun/star/script,</tt>needs to be in the <tt>offapi</tt>&nbsp;module)</li>
+</ul>
+</p>
+<p>
+<p>You will need to modify the offapi and unoil modules so that the
+services and interfaces for scripting are available.
+                   
+<h3><tt>offapi</tt> module</h3>
+<ol>
+    <li>Ensure that you have the drafts/com/sun/star/script directory 
+    under the offapi module, if you don't, you will need to check it out from
+    CVS head</li>
+    <li>Modify the <tt>prj/build.lst</tt>, you will need to add the following
+    lines
+    <ul>
+        <li><tt>oa&nbsp;offapi\drafts\com\sun\star\script\framework&nbsp;nmake&nbsp;-&nbsp;all&nbsp;oa_scriptf_drafts&nbsp;NULL</tt></li>
+        <li><tt>oa&nbsp;offapi\drafts\com\sun\star\script\framework\provider&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;nmake&nbsp;&nbsp;-&nbsp;all&nbsp;oa_sfprovider_drafts&nbsp;NULL</tt></li>
+        <li><tt>oa&nbsp;offapi\drafts\com\sun\star\script\framework\storage&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nmake&nbsp;&nbsp; -&nbsp;&nbsp; all oa_sfstorage_drafts NULL</tt></li>
+    </ul>
+    <b>and add</b> "<tt>oa_sfprovider_drafts oa_sfstorage_drafts oa_scriptf_drafts</tt>" to the last line before "<tt>NULL</tt>"</li>
+    <li>Modify the util/makefile.mk and add the following to UNOIDLDBFILES list</li>
+    <ul>
+        <li><tt>$(UCR)$/dcssscriptframework.db&nbsp;\</tt></li>
+        <li><tt>$(UCR)$/dcsssfprovider.db&nbsp;\</tt></li>
+        <li><tt>$(UCR)$/dcsssfstorage.db</tt></li>
+    </ul>
+</ol>
+                           
+<h3><tt>unoil</tt> module</h3>
+<ol>
+    <li>Ensure that you have the drafts/com/sun/star/script directory 
+    under the unoil module, if you don't, you will need to check it out from 
+    CVS head</li>
+    <li>Modify the <tt>makefile.mk</tt> in the top level directory of the module<br>
+    Change the line <tt>RDB &nbsp;= &nbsp;$(SOLARBINDIR)/offapi.rdb</tt> to <tt>RDB = $(PRJ)$/..$/offapi$/$(INPATH)$/ucr$/offapi.db</tt></li>
+    <li>Modify <tt>prj/build.lst</tt></li>
+    <ul>
+        <li>Add the following line<br>
+        <tt>ul&nbsp; unoil\drafts\com\sun\star\script\framework&nbsp;nmake&nbsp;-&nbsp;all ul_scriptf_drafts ul_ucb ul_frame NULL</tt></li>
+        <li>Add <tt>ul_scriptf_drafts</tt>to the last line before <tt>NULL</tt></li>
+    </ul>
+</ol>
+               
+<h3><tt>scripting</tt> module</h3>
+<ol>
+    <li>Remove the comments from the lines in <tt>source/cppumaker.mk</tt></li>
+    <ul>
+        <li><tt>UNOUCRDEP=$(PRJ)/../offapi/$(INPATH)/ucr/offapi.db $(SOLARBINDIR)$/udkapi.rdb $(SOLARBINDIR)$/offapi.rdb</tt></li>
+        <li><tt>UNOUCRRDB=$(PRJ)/../offapi/$(INPATH)/ucr/offapi.db $(SOLARBINDIR)$/udkapi.rdb $(SOLARBINDIR)$/offapi.rdb</tt></li>
+    </ul>
+    <li>Comment out the lines in <tt>source/cppumaker.mk</tt></li>
+    <ul>
+        <li><tt>UNOUCRDEP=$(SOLARBINDIR)$/udkapi.rdb</tt></li>
+        <li><tt>UNOUCRRDB=$(SOLARBINDIR)$/udkapi.rdb</tt></li>
+    </ul>
+    <li>Remove the comment from the following line in <tt>java/build.xml</tt></li>
+    <ul>
+        <li><tt>&lt;!-- &lt;pathelement location="${prj}/../unoil/${inpath}/class/unoil.jar"/&gt; --&gt;</tt></li>
+    </ul>
+    <li>Comment out the line in <tt>java/build.xml</tt></li>
+    <ul>
+        <li><tt>&lt;pathelement location="${solar.jar}/unoil.jar"/&gt;</tt></li>
+    </ul>
+    <li>Assuming you have both NetBeans &amp; jEdit installed, modify the <tt>java/build.env</tt> to point at the NetBeans &amp; jEdit installations (see the openide.class.path &amp; jedit.class.path entries in the build.xml
+ for more details).&nbsp;</li>
+    <li><b>Alternatively,</b> if you do not wish to build the add-ins, delete the following entries from the depends section of the target "all" in the build.xml</li>
+    <ul>
+        <li>No NetBeans add-in</li>
+        <ul>
+             <li>localoffice.jar</li>
+             <li>netbeans.jar</li>
+        </ul>
+        <li>No jEdit add-in</li>
+        <ul>
+             <li>localoffice.jar</li>
+             <li>jedit.jar</li>
+        </ul>
+        <ul>
+             <li>netbeans.jar</li>
+             <li>localoffice.jar</li>
+             <li>jedit.jar</li>
+            <li>idesupport.jar<br>
+        </ul>
+    </ul>
+</ol>
+                   
+<h2><a name="build"></a>Building</h2>
+               
+<ol>
+    <li>Execute <tt>build</tt> in the <tt>offapi</tt> module</li>
+    <li>Execute <tt>build </tt>in the <tt>unoil</tt> module</li>
+    <li>Execute <tt>build</tt> in the <tt>scripting</tt> module</li>
+</ol>
+               
+          
+<h2><a name="autoinstaller"></a>Automated Installer</h2>
+   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. However, this expects that there exist output 
+ directories in the three projects mentioned previously
+ for each of the three main platforms (Solaris/SPARC. Linux/x86, Windows). 
+ For a build on a single platform, modifications to the following targets 
+ will need to be made
+<ul>
+     <li><b>buildunopackage</b></li>
+  <ul>
+       <li>Modify the copy of the <tt>offapi.db</tt>, replacing <tt>unxsols3</tt> 
+ with the appropriate platform.</li>
+       <li>Modify the copy of the <tt>unoil.jar</tt>, replacing <tt>unxsols3</tt> 
+ with the appropriate platform.</li>
+       <li>Remove the mkdir &amp; copy of the <tt>.plt</tt> directories other than 
+that  on which you are working.</li>
+  </ul>
+     <li><b>packagesingletons</b> - remove the <tt>mkdir</tt> &amp; <tt>copy</tt> of the <tt>regsingleton</tt> 
+ tool for platforms other than that on which you are working.</li>
+     
+</ul>
+   Once these changes have been made, running <tt>dmake</tt> in the <tt>scripting/workben</tt> 
+ directory should result in the creation of the <tt>SFrameworkInstall.jar</tt>.<br>
+   <br>
+
+<h2><a name="install"></a>Manual Installation of the Scripting Framework</h2>
+The use of the automated installer, written in Java, is recommended, unless you're on a platform other than Solaris/SPARC, Linux/x86, Windows!
+ 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 & Jar files.
+<ol>
+          <li>Create a separate directory (<tt>$pkg</tt>)</li>
+          <li>In this directory, create directories called <tt>$pkg/&lt;PLATFORM&gt;.plt
+        </tt>and <tt>$pkg/skip_registration</tt> (Where <tt>&lt;PLATFORM&gt;</tt>
+   is like  linux_x86)<br>
+         <b>NOTE</b>: 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</li>
+          <li>Copy in the libraries from <tt>scripting/&lt;platform&gt;/lib
+     </tt>to        <tt>$pkg/&lt;PLATFORM&gt;.plt</tt></li>
+              <li>Copy in <tt>ScriptRuntimeForJava.jar</tt> from <tt>scripting/&lt;platform&gt;/class</tt>
+    into the top level directory,&nbsp;<tt>$pkg</tt></li>
+        <li>Copy in <tt>unoil.jar </tt>from <tt>$pkg/unoil/&lt;platform&gt;/class
+       </tt>&nbsp;to      <tt>skip_registration</tt> directory<br>
+          </li>
+          <li>Merge the following registries from <tt>offapi/&lt;platform&gt;/ucr 
+       </tt>into one registry called <tt>ooscript.rdb</tt> under the top level 
+  directory,&nbsp;<tt>$pkg</tt></li>
+                           
+  <ul>
+           <li><tt>dcssscriptframework.db</tt></li>
+           <li><tt>dcsssfprovider.db</tt></li>
+           <li><tt>dcsssfstorage.db</tt></li>
+                           
+  </ul>
+         <li>Now, zip up all files in this directory,&nbsp;<i>$pkg</i></li>
+               
+</ol>
+The next stage is to take the UNO package and install it in an OpenOffice installation. 
+             
+<ol>
+         <li>Copy the zip file into your OpenOffice installation under the
+ <tt>user/uno_packages</tt>   directory&nbsp;<font color="#ff0000"></font></li>
+         <li>In the program directory, run pkgchk on the zip file</li>
+      <li>Copy from the solver<tt> ($SRC_ROOT)/solver/643/&lt;platform&gt;/bin/regsingleton</tt>
+  to your OpenOffice installation under the program directory<br>
+      </li>
+         <li>Execute the following</li>
+                           
+  <ul>
+           <li><tt>./regsingleton &lt;OpenOffice Path&gt;/user/uno_packages/cache/services.rdb 
+   drafts.com.sun.star.script.framework.storage.theScriptStorageManager=drafts.com.sun.star.script.framework.storage.ScriptStorageManager</tt></li>
+           <li><tt>./regsingleton &lt;OpenOffice Path&gt;/user/uno_packages/cache/services.rdb
+    drafts.com.sun.star.script.framework.theScriptRuntimeForJava=drafts.com.sun.star.script.framework.ScriptRuntimeForJava</tt></li>
+                           
+  </ul>
+         <li>Modify the the <tt>ProtocolHandler.xcu</tt> file under<tt> &lt;OpenOffice 
+   Path&gt;/share/registry/data/org/openoffice/Office/</tt>, add the following 
+   lines:<br>
+                           
+  <tt>
+           &lt;node oor:name="com.sun.star.comp.ScriptProtocolHandler"
+ oor:op="replace"&gt;<br>
+       &nbsp;&nbsp;&nbsp;&nbsp;&lt;prop oor:name="Protocols"&gt;<br>
+       &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;value&gt;script:*&lt;/value&gt;<br>
+   &nbsp;&nbsp;&nbsp;&nbsp;&lt;/prop&gt;<br>
+   &lt;/node&gt;<br>
+  </tt>
+       Under the <tt>HandlerSet</tt> Tag</li>
+                           
+             
+</ol>
+       Unzip <tt>HighlightTextParcel.sxp</tt> from <tt>scripting/examples/java 
+ </tt>into   <tt>&lt;OpenOffice Path&gt;/user</tt>, this should create a directory 
+ under   <tt>user </tt>&nbsp;called <tt>Scripts/java/HighlightText</tt><br>
+       <br>
+       Now, run OpenOffice and under the <tt>Tools-&gt;Configure</tt> menu
+add   a  new menu which is bound to the macro <tt>Standard.Main</tt>, then
+shut down   OpenOffice and modify the file <tt>&lt;OpenOffice&gt;/user/config/soffice.cfg/writermenubar.cfg</tt> 
+   and change <tt>macro://Standard.main()</tt> to <tt>script://HighlightText.showForm. 
+   </tt>Start OpenOffice again and select the menu item you have added, this 
+  should bring up a Java dialog box call <tt>HighlightText</tt><br>
+   </tt>
+<hr width="100%" size="2">         <table colspan="2" cellpadding="4" cellspacing="0">
+<tr>
+<td width=25%><a href="mailto:dev@framework.openoffice.org">
+Mailing List</a></td>
+<td width=75%>Installation, User or Developer queries on the Office
+Scripting Framework</td>
+</tr>
+<tr>
+<td width=25%>Issues</td>
+<td width=75%>Issues found in the Office Scripting Framework should be
+logged in Issuezilla<br>
+<b>component:</b> framework<br>
+<b>subcomponent:</b> scripting</td>
+</tr>
+</table>
+ <br>
+ 
+Last revision: Fri Nov 29 11:40:28 GMT 2002<br>
+</body>
+</html>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/index.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/index.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/index.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,287 @@
+<!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>Maintainers:</b>
+<a href="mailto:ab@openoffice.org">Andreas Bregas</a><a href="mailto:dfoster@openoffice.org"></a>
+
+</p>
+<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>Features</p>
+
+      </td>
+
+      <td colspan="5" style="width: 70%;">
+        The Scripting Framework allows OpenOffice.org users to write and
+        run macros in multiple languages including OpenOffice.org Basic,
+        Python, Java, BeanShell and JavaScript. These macros can then be
+        assigned to menus, toolbars, keyboard shortcuts, events and embedded
+        objects.
+        
+      <p><a href="http://specs.openoffice.org/scripting_framework/index.html">Specifications for the Scripting Framework UI</a>
+      </p>
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td style="width: 30%;">
+      
+      <p>Install</p>
+
+      </td>
+
+      <td colspan="5" style="width: 70%;">
+      
+      <p>Install the <a href="http://download.openoffice.org/680/index.html">latest OpenOffice.org 2.0 build</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>See Developer Guide chapter attached to <a href="http://www.openoffice.org/issues/show_bug.cgi?id=29495">issue 29495</a>, (<a href="http://framework.openoffice.org/scripting/ScriptingFrameworkChapter.pdf">PDF</a>)
+      </p>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td colspan="4" valign="top" width="395">
+      
+      <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 colspan="4" width="220">
+      
+      <p>See Developer Guide chapter attached to <a href="http://www.openoffice.org/issues/show_bug.cgi?id=29495">issue 29495</a>, (<a href="http://framework.openoffice.org/scripting/ScriptingFrameworkChapter.pdf">PDF</a>)
+      </p>
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td colspan="4" valign="top" width="220">
+      
+      <p><a href="http://framework.openoffice.org/scripting/netbeans-debugging.html">Debugging Scripts in NetBeans</a></p>
+
+      </td>
+
+    </tr>
+
+  
+  </tbody>
+</table>
+
+</p>
+<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>
+    <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 style="width: 100%;" cellpadding="4" cellspacing="0">
+
+  <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 28 2006
+</p>
+
+</body>
+</html>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/netbeans-debugging.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/netbeans-debugging.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/netbeans-debugging.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/netbeans-debugging.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,37 @@
+<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>Debugging Java OpenOffice.org macros in NetBeans</h1>
+         
+This document describes how to set up NetBeans for debugging Java macros
+in OpenOffice.org.
+
+<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>
+
+<hr>
+Last Modified: Jan 13 2005
+</body>
+</html>

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

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

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/SmokeTest.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/SmokeTest.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/SmokeTest.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/SmokeTest.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,1115 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE>Smoke Test</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.1 Beta 1 (Solaris Sparc)">
+	<META NAME="AUTHOR" CONTENT="Robert.Kinsella@Sun.COM">
+	<META NAME="CREATED" CONTENT="20010103;10350500">
+	<META NAME="CHANGED" CONTENT="20021216;15453300">
+</HEAD>
+<BODY LANG="en-US" TEXT="#000000" LINK="#ff0000" VLINK="#551a8b" BGCOLOR="#ffffff" DIR="LTR">
+<P STYLE="margin-bottom: 0cm">&nbsp; 
+</P>
+<TABLE COLS=1 WIDTH=100% CELLPADDING=2 CELLSPACING=2>
+	<TR>
+		<TD>
+			<P>&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD>
+			<P ALIGN=CENTER><FONT SIZE=6><B>Smoke Tests for OpenOffice.org
+			Scripting FrameWork</B></FONT></P>
+		</TD>
+	</TR>
+</TABLE>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm">&nbsp;</P>
+<CENTER>
+	<TABLE WIDTH=80% BORDER=1 CELLPADDING=2 CELLSPACING=3>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#README">README</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P>Outline the order by which the installs of various components
+				must occur.</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#install_01">Install_01</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P><FONT SIZE=3>Test the SFrameworkInstall.jar file will not
+				install if placed in the incorrect directory.</FONT></P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#install_02">Install_02</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P><FONT SIZE=3>Test the SFrameworkInstall.jar&nbsp; will sense
+				directory names longer than 8 characters.&nbsp;</FONT></P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#install_03">Install_03</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P><FONT SIZE=3>Test the SFrameworkInstall.jar&nbsp; will sense
+				directory names which contain a space character.&nbsp;</FONT></P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#install_04">Install_04</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P>Test the SFrameworkInstall.jar file when deployed will present
+				to the user options to allow a script to be bound to an event.&nbsp;
+				<BR>Also test&nbsp; that scripting framework jar files are
+				successfully deployed to NetBeans and Jedit.&nbsp;</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%></TD>
+			<TD WIDTH=89%></TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#bindings_01">Bindings_01</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P><FONT SIZE=3>Test that the user can assign a deployed script
+				to a key.&nbsp;</FONT></P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#bindings_02">Bindings_02</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P><FONT SIZE=3>Test that the user can&nbsp; remove an assigned
+				key.&nbsp;</FONT></P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#bindings_03">Bindings_03</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P><FONT SIZE=3>Test that the user can assign a deployed script
+				to the File menu item.&nbsp;</FONT></P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#bindings_04">Bindings_04</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P><FONT SIZE=3>Test that the user can delete an assigned File
+				menu item.&nbsp;</FONT></P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#bindings_05">Bindings_05</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P>Test that the user can execute a&nbsp; script stored in a
+				document with a binding stored in the same document.</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD>
+				<P><A HREF="#bindings_06">Bindings_06</A></P>
+			</TD>
+			<TD>
+				<P>Test that the user can store a binding within a document for a
+				script already stored in that document.</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TD></TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#jedit_01">jEdit_01</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P>Compile and deploy a java script to the application user area
+				using jedit.</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD>
+				<P><A HREF="#jedit_02">jedit_02</A></P>
+			</TD>
+			<TD>
+				<P>Verify that Refresh User Scripts (Java) functions correctly
+				for scripts deployed from jEdit.</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD>
+				<P><A HREF="#jedit_03">jedit_03</A></P>
+			</TD>
+			<TD>
+				<P>Verify that user can deploy a script to a document using jEdit</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD>
+				<P><A HREF="#jedit_04">jedit_04</A></P>
+			</TD>
+			<TD>
+				<P>Verify that user can delete a script deployed to a document
+				using jEdit.</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD WIDTH=11%>
+				<P><A HREF="#netbeans_01">NetBeans_01</A></P>
+			</TD>
+			<TD WIDTH=89%>
+				<P>Compile and deploy a java script to the application user area
+				using NetBeans.</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD>
+				<P><A HREF="#netbeans_02">NetBeans_02</A></P>
+			</TD>
+			<TD>
+				<P>Compile and deploy a java script to a document&nbsp; using
+				NetBeans.</P>
+			</TD>
+		</TR>
+		<TR>
+			<TD>
+				<P><A HREF="#netbeans_03">NetBeans_03</A></P>
+			</TD>
+			<TD>
+				<P>Delete a script&nbsp; deployed to a document&nbsp; using
+				NetBeans.</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<HR>
+<HR>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="README"></A>Test
+Case: README</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Outline
+the order by which the installs of various components must occur.</FONT>
+<BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000"><B>Prerequisites</B>:-</FONT>
+<BR><FONT COLOR="#000000">Download NetBeans 3.4&nbsp; from
+http://www.netbeans.org.</FONT> <BR><FONT COLOR="#000000">Download
+Jedit&nbsp; 4.0.3&nbsp; from http://www.jedit.org</FONT> <BR><FONT COLOR="#000000">Download
+Scripting Framework from http://framework.openoffice.org/scripting/</FONT>
+<BR><FONT COLOR="#000000">Download OpenOffice.org 643C or later from
+http://www.openoffice.org</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">General
+Description:</FONT></B> <BR><FONT COLOR="#000000">It is important
+that the following steps be executed in order and before and other
+test cases.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">1. Install
+NetBeans</FONT> <BR><FONT COLOR="#000000">2. Install jedit, install
+the jar version by executing&nbsp; 'java -Djava.compiler=none -jar
+filename.jar'</FONT> <BR><FONT COLOR="#000000">3.&nbsp; Start jedit,
+cd to the install directory and select jedit. exit jedit.</FONT> <BR><FONT COLOR="#000000">4.&nbsp;
+Start NetBeans, cd to the install-dir/bin and execute runide.sh for
+unix systems,</FONT> <BR><FONT COLOR="#000000">select runidew.exe for
+windows. exit NetBeans.</FONT> <BR><FONT COLOR="#000000">5.&nbsp;
+Install OpenOffice.org.</FONT> <BR><FONT COLOR="#000000">6.&nbsp;
+Copy&nbsp; the SFrameworkInstall.jar file to the
+OpenOffice.org-install-dir/program directory.</FONT> 
+</P>
+<HR>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="install_01"></A>
+Test Case: install_01</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Test
+the SFrameworkInstall.jar file will not install if placed in the
+incorrect directory.</FONT> <BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Requirements</FONT></B>
+<BR><FONT COLOR="#000000"><A HREF="#README">README </A>is performed
+before running this test case.</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR><FONT COLOR="#000000">1. Copy the SFrameworkInstall.jar file to
+the &lt;office-installation&gt;&nbsp; directory.</FONT> <BR><FONT COLOR="#000000">2.
+Ensure OpenOffice is not running, also ensure the quickstarters for
+windows and Linux are not running.</FONT> <BR><FONT COLOR="#000000">3.
+Execute java -jar SFrameworkInstall.jar</FONT> <BR><FONT COLOR="#000000">4.
+The installer should launch and advise the user that the installer
+must be run from the program directory</FONT> <BR><FONT COLOR="#000000">of
+a valid Office installation.</FONT> <BR><FONT COLOR="#000000">5.
+Select Cancel, the installer closes.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Expected
+Result:</FONT></B> <BR><FONT COLOR="#000000">All operations should
+complete successfully.</FONT> 
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="install_02"></A>
+Test Case: install_02</H1>
+<H2 STYLE="text-decoration: none">Test Area: Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Test
+the SFrameworkInstall.jar&nbsp; will sense directory names longer
+than 8 characters.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Requirements</FONT></B>
+<BR><FONT COLOR="#000000"><A HREF="#README">README</A>is performed
+before running this test case.</FONT> <BR><FONT COLOR="#000000">OpenOffice.org
+installation path directory has a name which is nine characters or
+more.</FONT> <BR><FONT COLOR="#000000">Jedit installation path
+directory has a name which is nine characters or more.</FONT>
+<BR><FONT COLOR="#000000">NetBeans installation path directory has a
+name which is nine characters or more.</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR><FONT COLOR="#000000">1. Copy the SFrameworkInstall.jar file to
+the &lt;office-installation&gt;/program&nbsp; directory.</FONT> <BR><FONT COLOR="#000000">2.
+Ensure OpenOffice is not running, also ensure the quickstarters for
+windows and Linux are not running.</FONT> <BR><FONT COLOR="#000000">3.
+Execute java -jar SFrameworkInstall.jar</FONT> <BR><FONT COLOR="#000000">4.
+On the Scripting Framework Installer welcome screen click next.</FONT>
+<BR><FONT COLOR="#000000">5. Select Install, in the dialog select
+Next.</FONT> <BR><FONT COLOR="#000000">6. When Installation has
+completed, select Finish, the next dialog should prompt you that the
+installer has</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
+found a Jedit installation and a NetBeans installation, select Next.</FONT>
+<BR><FONT COLOR="#000000">8. Select the IDE's for update, i.e.
+NetBeans and Jedit, select Next, Select Install, Select Finish</FONT>
+</P>
+<P><FONT COLOR="#000000">9. Manully check the jedit install,
+directory &lt;jedit-install&gt;/jars for the following files:-</FONT>
+<BR><B><FONT COLOR="#000000">OfficeScripting.jar</FONT></B>
+<BR><FONT COLOR="#000000">i<B>desupport.jar</B></FONT> <BR><FONT COLOR="#000000">10.
+Manually check the NetBeans install directory
+&lt;netbeans-install&gt;/modules for the following file:-</FONT>
+<BR><B><FONT COLOR="#000000">office.jar</FONT></B> 
+</P>
+<P><FONT COLOR="#000000">11. Start OpenOffice.org, select Tools,
+there should be an entry - Assign Script (java) to and an entry
+Refresh User Scripts.</FONT> <BR><FONT COLOR="#000000">12. Select
+Tools, Assign Script(java) , Menu. An assign Script(java) dialog
+should be launched.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Expected
+Result:</FONT></B> <BR><FONT COLOR="#000000">All operations should
+complete successfully.</FONT> 
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="install_03"></A>
+Test Case: install_03</H1>
+<H2 STYLE="text-decoration: none">Test Area: Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Test
+the SFrameworkInstall.jar&nbsp; will sense directory names which
+contain a space character.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Requirements</FONT></B>
+<BR><FONT COLOR="#000000"><A HREF="#README">README </A>is performed
+before running this test case.</FONT> <BR><FONT COLOR="#000000">OpenOffice.org
+installation path directory has a name which&nbsp; contains a space
+character.</FONT> <BR><FONT COLOR="#000000">Jedit installation path
+directory has a name which contains a space character.</FONT>
+<BR><FONT COLOR="#000000">NetBeans installation path directory has a
+name which contains a space character.</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR><FONT COLOR="#000000">1. Copy the SFrameworkInstall.jar file to
+the &lt;office-installation&gt;/program&nbsp; directory.</FONT> <BR><FONT COLOR="#000000">2.
+Ensure OpenOffice is not running, also ensure the quickstarters for
+windows and Linux are not running.</FONT> <BR><FONT COLOR="#000000">3.
+Execute java -jar SFrameworkInstall.jar</FONT> <BR><FONT COLOR="#000000">4.
+On the Scripting Framework Installer welcome screen click next.</FONT>
+<BR><FONT COLOR="#000000">5. Select Install, in the dialog select
+Next.</FONT> <BR><FONT COLOR="#000000">6. When Installation has
+completed, select Finish, the next dialog should prompt you that the
+installer has</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
+found a Jedit installation and a NetBeans installation, select Next.</FONT>
+<BR><FONT COLOR="#000000">8. Select the IDE's for update, i.e.
+NetBeans and Jedit, select Next, Select Install, Select Finish</FONT>
+</P>
+<P><FONT COLOR="#000000">9. Manully check the jedit install,
+directory &lt;jedit-install&gt;/jars for the following files:-</FONT>
+<BR><B><FONT COLOR="#000000">OfficeScripting.jar</FONT></B>
+<BR><FONT COLOR="#000000">i<B>desupport.jar</B></FONT> <BR><FONT COLOR="#000000">10.
+Manually check the NetBeans install directory
+&lt;netbeans-install&gt;/modules for the following file:-</FONT>
+<BR><B><FONT COLOR="#000000">office.jar</FONT></B> 
+</P>
+<P><FONT COLOR="#000000">11. Start OpenOffice.org, select Tools,
+there should be an entry - Assign Script (java) to and an entry
+Refresh User Scripts.</FONT> <BR><FONT COLOR="#000000">12. Select
+Tools, Assign Script(java) , Menu An assign Script(java) dialog
+should be launched.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Expected
+Result:</FONT></B> <BR><FONT COLOR="#000000">All operations should
+complete successfully.</FONT> 
+</P>
+<HR>
+<HR>
+<P><BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="install_04"></A>
+Test Case: install_04</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Test
+the SFrameworkInstall.jar file when deployed will present to the user
+options to allow a script to be bound to an event.</FONT> <BR><FONT COLOR="#000000">Also
+test&nbsp; that scripting framework jar files are successfully
+deployed to NetBeans and Jedit.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Requirements</FONT></B>
+<BR><FONT COLOR="#000000"><A HREF="#README">README </A>is performed
+before running this test case.</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR><FONT COLOR="#000000">1. Copy the SFrameworkInstall.jar file to
+the &lt;office-installation&gt;/program&nbsp; directory.</FONT> <BR><FONT COLOR="#000000">2.
+Ensure OpenOffice is not running, also ensure the quickstarters for
+windows and Linux are not running.</FONT> <BR><FONT COLOR="#000000">3.
+Execute java -jar SFrameworkInstall.jar</FONT> <BR><FONT COLOR="#000000">4.
+On the Scripting Framework Installer welcome screen click next, the
+welcome screen should state the version of SFramework.jar.</FONT> <BR><FONT COLOR="#000000">5.
+Select Install, in the dialog select Next.</FONT> <BR><FONT COLOR="#000000">6.
+When Installation has completed, select Finish, the next dialog
+should prompt you that the installer has</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
+found a Jedit installation and a NetBeans installation, select Next.</FONT>
+<BR><FONT COLOR="#000000">8. Select the IDE's for update, i.e.
+NetBeans and Jedit, select Next, Select Install, Select Finish</FONT>
+</P>
+<P><FONT COLOR="#000000">9. Manully check the jedit install,
+directory &lt;jedit-install&gt;/jars for the following files:-</FONT>
+<BR><B><FONT COLOR="#000000">OfficeScripting.jar</FONT></B>
+<BR><FONT COLOR="#000000">i<B>desupport.jar</B></FONT> <BR><FONT COLOR="#000000">10.
+Manually check the NetBeans install directory
+&lt;netbeans-install&gt;/modules for the following file:-</FONT>
+<BR><B><FONT COLOR="#000000">office.jar</FONT></B> <BR><FONT COLOR="#000000">11.
+Manually check that the SFrameworkInstall.log file was writter to the
+program directory.</FONT> <BR><FONT COLOR="#000000">12. Start
+OpenOffice.org, select Tools, there should be an entry - Assign
+Script (java) to and an entry Refresh User Scripts.</FONT> <BR><FONT COLOR="#000000">13.
+Select Tools, Assign Script(java) , Menu An assign Script(java)
+dialog should be launched.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Expected
+Result:</FONT></B> <BR><FONT COLOR="#000000">All operations should
+complete successfully.</FONT> 
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="bindings_01"></A>
+Test Case: bindings_01</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Test
+that the user can assign a deployed script to an key.</FONT> <BR>&nbsp;
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">Prerequisites:-</FONT>
+<BR><FONT COLOR="#000000"><A HREF="#install_04">install_04 </A>is
+executed before running this test case.</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR><FONT COLOR="#000000">1.&nbsp; Start OpenOffice.org writer
+document.</FONT> <BR><FONT COLOR="#000000">2. Select Tools -Assign
+Script(java) To, Key.</FONT> <BR><FONT COLOR="#000000">3. In the
+popup dialog,</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
+in the select script function select a script e.g.
+HighlightText.showForm</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+Select&nbsp; Key Group SHIFT + CONTROL +F keys.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+Select ShortcutKey SHIFT + CONTROL + F3.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+Select New Script Key.</FONT> <BR><FONT COLOR="#000000">4. The Key
+should now be assigned to HighlightText.showForm. Select OK.</FONT>
+<BR><FONT COLOR="#000000">5. Select OK when prompted that you need to
+restart OpenOffice.org</FONT> <BR><FONT COLOR="#000000">6. Exit and
+restart OpenOffice.org, opening a writer document.</FONT> <BR><FONT COLOR="#000000">7.
+Select Shift - Control - F3. The Highlight Text box dialog should be
+displayed.</FONT> <BR><FONT COLOR="#000000">8. Select Tools - Assign
+Script(java) To, Key, SHIFT-CONTROL-F3 should be listed as assigned
+to HighlightText.showForm. Close the Assign Script (Java) to Key
+dialog</FONT> <BR><FONT COLOR="#000000">9. Select Tools - Configure,
+select the Keyboard option, ensure that writer is selected in the top
+right corner.</FONT> <BR><FONT COLOR="#000000">In the shortcut keys
+scroll to Ctrl+Shift+F3, this should show that it is assigned to
+[script://HighlightText.showForm].</FONT> <BR><FONT COLOR="#000000">10.
+Close the Configuration dialog.</FONT> <BR>&nbsp; <BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Expected
+Result:</FONT></B> <BR><FONT COLOR="#000000">All operations should
+complete successfully.</FONT> 
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="bindings_02"></A>
+Test Case: bindings_02</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Test
+that the user can&nbsp; remove an assigned key.</FONT> <BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">Prerequisites:-</FONT>
+<BR><FONT COLOR="#000000"><A HREF="#bindings_01">bindings_01 </A>is
+executed before running this test case.</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR><FONT COLOR="#000000">1.&nbsp; Start OpenOffice.org writer
+document.</FONT> <BR><FONT COLOR="#000000">2. Select Tools -Assign
+Script(java) To, Key.</FONT> <BR><FONT COLOR="#000000">3. In the
+popup dialog,</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+Select&nbsp; Key Group SHIFT + CONTROL +F keys.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+Select ShortcutKey SHIFT + CONTROL + F3.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+Select&nbsp; Delete Script Key.</FONT> <BR><FONT COLOR="#000000">4.
+The Key should not be assigned to anything. Select OK.</FONT> <BR><FONT COLOR="#000000">5.
+Select OK when prompted that you need to restart OpenOffice.org</FONT>
+<BR><FONT COLOR="#000000">6. Exit and restart OpenOffice.org, opening
+a writer document.</FONT> <BR><FONT COLOR="#000000">7. Select Shift -
+Control - F3. The Highlight Text box dialog should be not&nbsp;
+displayed.</FONT> <BR><FONT COLOR="#000000">8. Select Tools - Assign
+Script(java) To, Key, SHIFT-CONTROL-F3 should not be listed as
+assigned to anything. Close the Assign Script (Java) to Key dialog</FONT>
+<BR><FONT COLOR="#000000">9. Select Tools - Configure, select the
+Keyboard option, ensure that writer is selected in the top right
+corner.</FONT> <BR><FONT COLOR="#000000">In the shortcut keys scroll
+to Ctrl+Shift+F3, this should show that it is not assigned to
+anything</FONT> <BR><FONT COLOR="#000000">10. Close the Configuration
+dialog.</FONT> <BR>&nbsp; <BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Expected
+Result:</FONT></B> <BR><FONT COLOR="#000000">All operations should
+complete successfully.</FONT> 
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="bindings_03"></A>
+Test Case: bindings_03</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Test
+that the user can assign a deployed script to the File menu item.</FONT>
+<BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">Prerequisites:-</FONT>
+<BR><FONT COLOR="#000000"><A HREF="#install_04">install_04 </A>is
+executed before running this test case</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR><FONT COLOR="#000000">1.&nbsp; Start OpenOffice.org&nbsp; writer
+document.</FONT> <BR><FONT COLOR="#000000">2. Select Tools, Assign
+Script(java) To, Menu.</FONT> <BR><FONT COLOR="#000000">3. In the
+popup dialog,</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
+in the select script function select a script e.g.
+HighlightText.showForm</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+Select File in the Top Level menu drop down list.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+In the New Menu, enter a menu item name e.g. menuhighlight.</FONT>
+<BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp; Select New Script Menu,
+select ok.</FONT> <BR><FONT COLOR="#000000">4. Select OK when
+prompted to restart OpenOffice.org. Exit and restart OpenOffice.org
+writer document.</FONT> <BR><FONT COLOR="#000000">5. Select File,
+menuhighlight - a highlight text box should appear.</FONT> <BR>&nbsp;
+<BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Expected
+Result:</FONT></B> <BR><FONT COLOR="#000000">All operations should
+complete successfully.</FONT> 
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="bindings_04"></A>
+Test Case: bindings_04</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Test
+that the user can delete an assigned File menu item.</FONT> <BR>&nbsp;
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">Prerequisites:-</FONT>
+<BR><FONT COLOR="#000000"><A HREF="#bindings_03">bindings_03</A>&nbsp;
+is&nbsp; executed before running this test case</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR><FONT COLOR="#000000">1.&nbsp; Start OpenOffice.org writer
+document.</FONT> <BR><FONT COLOR="#000000">2. Select Tools, Assign
+Script(java) To, Menu.</FONT> <BR><FONT COLOR="#000000">3. In the
+popup dialog,</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
+Select File in the Top Level menu drop down list.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+In the Sub Menu, select menuhighlight [ HighlightText.ShowForm]</FONT>
+<BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp; Select Delete Script
+Menu. Select OK.</FONT> <BR><FONT COLOR="#000000">4. Select OK when
+prompted to restart OpenOffice.org. Exit and restart OpenOffice.org
+writer document.</FONT> <BR><FONT COLOR="#000000">5. Select File,
+there should now be no menu option menuhighlight.</FONT> <BR>&nbsp;
+<BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Expected
+Result:</FONT></B> <BR><FONT COLOR="#000000">All operations should
+complete successfully.</FONT> 
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER><A NAME="bindings_05"></A>Test Case: bindings_05</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Test
+that the user can execute a&nbsp; script stored in a document with a
+binding stored in the same document.</FONT> <BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">Prerequisites:-</FONT>
+<BR><FONT COLOR="#000000">&nbsp;<A HREF="#install_04">install_04 </A>is
+executed before running this test case.</FONT> 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR><FONT COLOR="#000000">1.&nbsp; Start OpenOffice.org.</FONT> <BR><FONT COLOR="#000000">2.
+Select File - Open, navigate to
+&lt;OpenOffice.org-install-dir&gt;/user/Scripts/java/MemoryUsage.</FONT>
+<BR><FONT COLOR="#000000">3. Open file ExampleSpreadSheet.sxc, a
+spreadsheet document with a pie chart should be opened</FONT> <BR><FONT COLOR="#000000">4.
+Press ctrl-shift-m, the user is warned that they are about to execute
+a sctipt.</FONT> <BR><FONT COLOR="#000000">Do you want to execute
+this script.</FONT> <BR><FONT COLOR="#000000">5. Select Yes.</FONT>
+<BR><FONT COLOR="#000000">6. The chart updates with JVM memory usage
+statistics.</FONT> <BR><FONT COLOR="#000000">7. Repeat steps 4-6
+again.</FONT> <BR>&nbsp; <BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Expected
+Result:</FONT></B> 
+</P>
+<P><FONT SIZE=3>All operations should complete successfully.</FONT></P>
+<HR>
+<HR>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="bindings_06"></A>
+Test Case:&nbsp;bindings_06</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B>Test Aim</B> <BR>Test that the user can store a binding within
+a document for a script already stored in that document. <BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm">Prerequisites:- <BR><A HREF="#jedit_03">jedit_03</A>
+is executed before running this test case. <BR>Note The functionality
+for this test case is not available yet. 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B>Description:</B> <BR>&nbsp; <BR>&nbsp;
+</P>
+<P STYLE="margin-bottom: 0cm"><B>Expected Result:</B> <BR>All
+operations should complete successfully. 
+</P>
+<HR>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="jedit_01"></A>
+Test Case: jedit_01</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P STYLE="margin-bottom: 0cm"><B>Test Aim</B></P>
+<P><FONT COLOR="#000000">Compile and deploy a java script to the
+application user area using jedit.</FONT> 
+</P>
+<P><FONT COLOR="#000000">Prequisites:-</FONT> <BR><FONT COLOR="#000000"><A HREF="#install_04">install_04
+</A>is executed before running this test case.</FONT> <BR><A HREF="jedit-devguide.html#prerequisites">JEdit
+prerequisites</A></P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+</P>
+<OL START=2>
+	<P><FONT COLOR="#000000">1. Start Jedit.</FONT> <BR><FONT COLOR="#000000">Click
+	on the Office Scripting button on the right of the frame.</FONT> 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">Right click on
+	all parcels.</FONT> 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">Select New</FONT>
+	<BR><FONT COLOR="#000000">Enter the name of the new parcel e.g.
+	HelloJedit.</FONT> <BR><FONT COLOR="#000000">Select a directory
+	where you want the parcel to be built .</FONT> 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">2. In the left
+	hand frame the HelloJedit script is opened you need to add the
+	following lines to the top of the script</FONT> <BR><FONT COLOR="#000000">immediately
+	after the first import statement</FONT> 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">import
+	com.sun.star.uno.UnoRuntime;</FONT> <BR><FONT COLOR="#000000">import
+	com.sun.star.frame.XModel;</FONT> <BR><FONT COLOR="#000000">import
+	com.sun.star.text.*;</FONT> <BR>&nbsp; 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">3. Add the
+	following lines to&nbsp; the public method doMethod in the
+	HelloJedit class.</FONT> 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">XModel model =
+	xSc.getDocument();</FONT> <BR><FONT COLOR="#000000">&nbsp;XTextDocument
+	textdoc = (XTextDocument)</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	UnoRuntime.queryInterface(XTextDocument.class, model);</FONT>
+	<BR><FONT COLOR="#000000">&nbsp;XText oText = textdoc.getText();</FONT>
+	<BR><FONT COLOR="#000000">&nbsp;XTextCursor oCursor =
+	oText.createTextCursor();</FONT> <BR><FONT COLOR="#000000">&nbsp;oText.insertString(oCursor,
+	&quot;Hello jEdit&quot;, false);</FONT> <BR>&nbsp; <BR>&nbsp; 
+	</P>
+	<P><FONT COLOR="#000000">4. Right click on&nbsp; 'HelloJedit' and
+	select ScriptCompile.</FONT> <BR><FONT COLOR="#000000">After
+	complation has successfully completed, right click on 'HelloJedit'
+	and select Build Parcel SXP.</FONT> 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">In the scripting
+	framework dialog that appears select the method HelloJedit.doMethod
+	in the right frame</FONT> 
+	</P>
+	<P STYLE="margin-bottom: 0cm">and select Add.</P>
+	<P STYLE="margin-bottom: 0cm">Select Finish.</P>
+	<P><BR>&nbsp; 
+	</P>
+	<P><FONT COLOR="#000000">5. Right click on the HelloJedit.sxp parcel
+	and select Deploy to OpenOffice.org.</FONT> 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">Check that the
+	scripts have been deployed to
+	&lt;office_installation&gt;/user/Scripts/java.</FONT> <BR>&nbsp; 
+	</P>
+	<P><FONT COLOR="#000000">6. Assign an event&nbsp; to execute the
+	script.</FONT> <BR><FONT COLOR="#000000">- Start OpenOffice.org&nbsp;
+	writer document.</FONT> <BR><FONT COLOR="#000000">- Select Tools,
+	Assign Script(java) To, Menu.</FONT> <BR><FONT COLOR="#000000">- In
+	the popup dialog,</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
+	in the select script function select a script e.g.
+	HelloJedit.doMethod</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+	Select File in the Top Level menu drop down list.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+	In the New Menu, enter a menu item name e.g. HelloJedit.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+	Select New Script Menu, select ok.</FONT> <BR><FONT COLOR="#000000">-
+	Select OK when prompted to restart OpenOffice.org. Exit and restart
+	OpenOffice.org writer document.</FONT> <BR><FONT COLOR="#000000">-
+	Select File, HelloJedit - Hello jEdit should be inserted into the
+	document.</FONT> <BR>&nbsp; 
+	</P>
+	<P><B>Expected Result:</B></P>
+</OL>
+<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+All operations should complete successfully.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P><BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER><A NAME="jedit_02"></A>Test Case:&nbsp;jedit_02</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P STYLE="margin-bottom: 0cm"><B>Test Aim</B> <BR>Verify that Refresh
+User Scripts (Java) functions correctly for scripts deployed from
+jEdit. 
+</P>
+<P STYLE="margin-bottom: 0cm">&nbsp; <BR>Prequisites:- <BR><A HREF="#install_04">install_04</A>is
+executed before running this test case.</P>
+<P STYLE="margin-bottom: 0cm">OpenOffice.org is running a writer
+document. <BR>Ensure hellojedit2 is not already listed under Assign
+Script (Java) to Key or Menu. 
+</P>
+<HR>
+<P STYLE="text-decoration: none"><B>Description:</B> <BR>&nbsp; <BR>&nbsp;
+</P>
+<OL START=2>
+	<P STYLE="margin-bottom: 0cm">1. Click on the Office Scripting
+	button on the right of the frame. 
+	</P>
+	<P STYLE="margin-bottom: 0cm">Right click on all parcels.</P>
+	<P STYLE="margin-bottom: 0cm">Select New <BR>Enter the name of the
+	new parcel e.g. HelloJedit2. <BR>Select a directory where you want
+	the parcel to be built . 
+	</P>
+	<P STYLE="margin-bottom: 0cm">2. In the left hand frame the
+	HelloJedit2 script is opened you need to add the following lines to
+	the top of the script <BR>immediately after the first import
+	statement 
+	</P>
+	<P STYLE="margin-bottom: 0cm">import com.sun.star.uno.UnoRuntime;
+	<BR>import com.sun.star.frame.XModel; <BR>import
+	com.sun.star.text.*; <BR>&nbsp; 
+	</P>
+	<P STYLE="margin-bottom: 0cm">3. <FONT COLOR="#000000">Add the
+	following lines to&nbsp; the public method doMethod in the
+	</FONT>HelloJedit2 class. 
+	</P>
+	<P STYLE="margin-bottom: 0cm">XModel model = xSc.getDocument();
+	<BR>&nbsp;XTextDocument textdoc = (XTextDocument) <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	UnoRuntime.queryInterface(XTextDocument.class, model); <BR>&nbsp;XText
+	oText = textdoc.getText(); <BR>&nbsp;XTextCursor oCursor =
+	oText.createTextCursor(); <BR>&nbsp;oText.insertString(oCursor,
+	&quot;Hello jEdit2 &quot;, false); <BR>&nbsp;</P>
+	<P STYLE="margin-bottom: 0cm">&nbsp; <BR>4. Select, File - Save.
+	<BR>Right click on&nbsp; 'HelloJedit2' and select ScriptCompile.
+	<BR>After complation has successfully completed, right click on
+	'HelloJedit2' and select Build Parcel SXP.</P>
+	<P STYLE="margin-bottom: 0cm">In the scripting framework dialog that
+	appears select the method HelloJedit2.doMethod in the right frame</P>
+	<P STYLE="margin-bottom: 0cm">and select Add.</P>
+	<P STYLE="margin-bottom: 0cm">&nbsp; <BR>5. Right click on the
+	HelloJedit2.sxp parcel and select Deploy to OpenOffice.org.</P>
+	<P STYLE="margin-bottom: 0cm">&nbsp; <BR>6. In OpenOffice.org select
+	Tools, Assign Script (Java) To - Key. <BR>HelloJedit2 should not be
+	listed&nbsp; in the Select script function box. <BR>Close the Assign
+	Script (Java) To Key dialog box 
+	</P>
+	<P STYLE="margin-bottom: 0cm">7. Select Tools, Refresh User Scripts
+	(java). <BR>Select Tools, Assign Script (Java) To - Key.
+	<BR>HelloJedit2 should now be listed&nbsp; in the Select script
+	function box. 
+	</P>
+	<P STYLE="margin-bottom: 0cm">8. Select HelloJedit2.doMethod in the
+	Select script function box. <BR>Select the shotcut key group Shift +
+	Control + F keys. <BR>Select the Shortcut Key Shift + Control + F10.
+	<BR>Select, New Script Key, Select OK. <BR>Select OK when prompted
+	to restart OpenOffice.org. Exit and restart OpenOffice.org writer
+	document. <BR>Select Shift+ Control + F10, Hello jEdit2 should be
+	inserted into the document.</P>
+	<P><B>Expected Result:</B></P>
+</OL>
+<P STYLE="margin-bottom: 0cm">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+All operations should complete successfully. 
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER><A NAME="jedit_03"></A>Test Case:&nbsp;jedit_03</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P STYLE="margin-bottom: 0cm"><B>Test Aim</B> <BR>Verify that user
+can deploy a script to a document using jEdit. 
+</P>
+<P STYLE="margin-bottom: 0cm">&nbsp; <BR>Prequisites:- <BR><A HREF="#jedit_01">jedit_01</A>
+is executed before running this test case. <BR>Delete directory
+&lt;office-install&gt;/user/Scripts/java/HelloJedit. <BR>OpenOffice.org
+is not running. <BR>A previously created OpenOffice.org writer
+document, e.g. TestBindjE.sxw</P>
+<HR>
+<P>1. Start Jedit <BR>Click on the HelloJedit.java file listed under
+All Parcels, HelloJedit. <BR>Change the text in the HelloJedit.java
+file from <FONT COLOR="#000000">&quot;Hello jEdit&quot;&nbsp; to
+&quot;Hello jEdit 3---&quot;.</FONT> <BR><FONT COLOR="#000000">Select
+File Save.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">2. Right click on
+hellojedit and select Script Compile.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm">After complation has successfully
+completed, right click on 'HelloJedit' and select Build Parcel SXP.</P>
+<P STYLE="margin-bottom: 0cm">Select Finish. 
+</P>
+<P STYLE="margin-bottom: 0cm">3. <FONT COLOR="#000000">Right click on
+the HelloJedit.sxp parcel and select Deploy to Document.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">4. Check that the
+script has been successfully deployed to the document by running
+unzip -l&nbsp; </FONT>TestBindjE.sxw<FONT COLOR="#000000">. (Unix) or
+pkunzip -v&nbsp; </FONT>TestBindjE.sxw <FONT COLOR="#000000">(Windows).
+You should see the script saved in the document.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm">5. Launch OpenOffice.org, note the
+previously assigned bindings as setup in jedit_01 still apply to the
+TestBindjE.sxw document. Open the TestBindjE.sxw document. 
+</P>
+<P STYLE="margin-bottom: 0cm">6. Select File <FONT COLOR="#000000">HelloJedit
+- &quot;Hello jEdit&nbsp; 3--- &quot;should be inserted into the
+document.</FONT> <BR>&nbsp;</P>
+<HR>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER><A NAME="jedit_04"></A>Test Case:&nbsp;jedit_04</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P STYLE="margin-bottom: 0cm"><B>Test Aim</B> <BR>Verify that user
+can delete a script deployed to a document using jEdit. 
+</P>
+<P STYLE="margin-bottom: 0cm">&nbsp; <BR>Prequisites:- <BR><A HREF="#jedit_03">jedit_03</A>
+is executed before running this test case. <BR>Close the test
+document TestBindjE.sxw in OpenOffice.org before executing test. 
+</P>
+<HR>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+</P>
+<P STYLE="margin-bottom: 0cm">1. Start Jedit, right click on All
+Parcels and select Open. 
+</P>
+<P STYLE="margin-bottom: 0cm">2. Browse to the document
+TestBindjE.sxw and open it. 
+</P>
+<P STYLE="margin-bottom: 0cm">3. Expand the document TestBindjE.sxw.
+Right click on the PARCEL_FILE and select Remove Parcel. 
+</P>
+<P STYLE="margin-bottom: 0cm">4. <FONT COLOR="#000000">Check that the
+script has been successfully remove from the document by running
+unzip -l&nbsp; </FONT>TestBindjE.sxw<FONT COLOR="#000000">. (Unix) or
+pkunzip -v&nbsp; </FONT>TestBindjE.sxw <FONT COLOR="#000000">(Windows).
+You should see that the script has been removed from the document.</FONT>
+<BR>&nbsp;</P>
+<HR>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="netbeans_01"></A>
+Test Case: netbeans_01</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Compile
+and deploy a java script to the application user area using NetBeans.</FONT>
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Prerequisits</FONT></B>
+<BR><FONT COLOR="#000000"><A HREF="#install_04">install_04 </A>is
+executed before running this test case.</FONT> <BR><A HREF="netbeans-devguide.html#prerequisites">Netbeans
+prerequisites</A></P>
+<HR>
+<P STYLE="text-decoration: none"><B><FONT COLOR="#000000">Description:</FONT></B>
+<BR>&nbsp; 
+</P>
+<OL START=2>
+	<P><FONT COLOR="#000000">1. Create an examples directory e.g.
+	HelloNetBeans.#</FONT> <BR><FONT COLOR="#000000">Start NetBeans.</FONT>
+		</P>
+	<P><FONT COLOR="#000000">2. Mount the examples directories</FONT>
+	<BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	Select the File-&gt;Mount Filesystem menu item</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	In the Choose Filesystem Type window select Local Directory and
+	click Next</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	Mount the examples directory you created i.e. HelloNetBeans.</FONT>
+	<BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	Select Finish.</FONT> 
+	</P>
+	<P><FONT COLOR="#000000">3.&nbsp;&nbsp; Create a new script parcel</FONT>
+	<BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	Right click on your mounted examples directory.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	Select New-&gt;Office Scripting-&gt;Parcel Recipe</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	In the New Wizard window that appears, enter the name you wish to
+	call your new parcel e.g HelloNetBeans.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	Select Finish.</FONT> 
+	</P>
+	<P><FONT COLOR="#000000">4.&nbsp; Click on the Contents-Empty file</FONT>
+	<BR><FONT COLOR="#000000">-Change the name of 'public class Empty'
+	to 'public class HelloNetBeans'</FONT> <BR><FONT COLOR="#000000">-Remove
+	the package declaration 'package HelloNetBeans.Contents;' at the top
+	of the file</FONT> <BR><FONT COLOR="#000000">-Add the following
+	lines to the top of the script immediately after the first import
+	statement</FONT> 
+	</P>
+	<P><FONT COLOR="#000000">import com.sun.star.uno.UnoRuntime;</FONT>
+	<BR><FONT COLOR="#000000">import com.sun.star.frame.XModel;</FONT>
+	<BR><FONT COLOR="#000000">import com.sun.star.text.*;</FONT> <BR>&nbsp;
+		</P>
+	<P><FONT COLOR="#000000">5. Add the following lines to&nbsp; the
+	public method doMethod in the </FONT>HelloNetBeans class. 
+	</P>
+	<P><FONT COLOR="#000000">XModel model = xSc.getDocument();</FONT>
+	<BR><FONT COLOR="#000000">&nbsp;XTextDocument textdoc =
+	(XTextDocument)</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+	UnoRuntime.queryInterface(XTextDocument.class, model);</FONT>
+	<BR><FONT COLOR="#000000">&nbsp;XText oText = textdoc.getText();</FONT>
+	<BR><FONT COLOR="#000000">&nbsp;XTextCursor oCursor =
+	oText.createTextCursor();</FONT> <BR><FONT COLOR="#000000">&nbsp;oText.insertString(oCursor,
+	&quot;Hello NetBeans&quot;, false);</FONT> 
+	</P>
+	<P><FONT COLOR="#000000">6. Right click on the HelloNetBeans in the
+	right frame and select save.</FONT> 
+	</P>
+	<P><FONT COLOR="#000000">7.&nbsp;&nbsp; Right click on&nbsp; the
+	HelloNetBeans directory and select compile. You should note that</FONT>
+	<BR><FONT COLOR="#000000">the compile completes successfully from
+	the lower right hand frame (output window) of NetBeans.</FONT> 
+	</P>
+	<P><FONT COLOR="#000000">8. Right click on the HelloNetBeans&nbsp;
+	directory and select build,</FONT> <BR><FONT COLOR="#000000">In the
+	dialog which appears select the HelloNetBeans.doMethod and add to
+	scripts , select OK.</FONT> <BR><FONT COLOR="#000000">A
+	HelloNetBeans parcel file should be built.</FONT> 
+	</P>
+	<P><FONT COLOR="#000000">9. Right click on the Hello NetBeans parcel
+	file and select Deploy to OpenOffice.org.</FONT> 
+	</P>
+	<P><FONT COLOR="#000000">10. Check that the files have been
+	successfully deployed to &lt;office-install&gt;/user/Scripts/java.</FONT>
+		</P>
+	<P><FONT COLOR="#000000">11. Assign an event&nbsp; to execute the
+	script.</FONT> <BR><FONT COLOR="#000000">- Start OpenOffice.org&nbsp;
+	writer document.</FONT> <BR><FONT COLOR="#000000">- Select Tools,
+	Assign Script(java) To, Menu.</FONT> <BR><FONT COLOR="#000000">- In
+	the popup dialog,</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
+	in the select script function select a script e.g.
+	HelloNetBeans.doMethod</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+	Select File in the Top Level menu drop down list.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+	In the New Menu, enter a menu item name e.g. HelloNetBeans.</FONT>
+	<BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp; Select New Script Menu,
+	select ok.</FONT> <BR><FONT COLOR="#000000">- Select OK when
+	prompted to restart OpenOffice.org. Exit and restart OpenOffice.org
+	writer document.</FONT> <BR><FONT COLOR="#000000">- Select File,
+	HelloNetBeans - Hello NetBeans should be inserted into the document.</FONT></P>
+</OL>
+<P><B><FONT COLOR="#000000">Expected Result:</FONT></B> <BR>&nbsp; 
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">All operations
+should complete successfully.</FONT> 
+</P>
+<HR>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="netbeans_02"></A>
+Test Case: netbeans_02</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Compile
+and deploy a java script to a document&nbsp; using NetBeans.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Prerequisites</FONT></B>
+<BR><FONT COLOR="#000000"><A HREF="#netbeans_01">netbeans_01</A> is
+executed before running this test case.</FONT> <BR>Delete directory
+&lt;office-install&gt;/user/Scripts/java/HelloNetBeans. <BR>A
+previously created OpenOffice.org writer document, e.g.
+TestBindNB.sxw 
+</P>
+<HR>
+<P><BR>&nbsp; 
+</P>
+<P>1. Start NetBeans <BR><FONT COLOR="#000000">&nbsp;Right click on
+the HelloNetBeans in the right frame and select the previously opened
+HelloNetBeans.java file.</FONT> <BR><FONT COLOR="#000000">Change the
+&quot;Hello NetBeans&quot; line to &quot;Hello NetBeans 2 ----&quot;</FONT>
+<BR><FONT COLOR="#000000">Select File Save.</FONT> 
+</P>
+<P><FONT COLOR="#000000">2.&nbsp;&nbsp; Right click on&nbsp; the
+HelloNetBeans directory and select compile. You should note that</FONT>
+<BR><FONT COLOR="#000000">the compile completes successfully from the
+lower right hand frame (output window) of NetBeans.</FONT> 
+</P>
+<P><FONT COLOR="#000000">3. Right click on the HelloNetBeans&nbsp;
+directory and select build,</FONT> <BR><FONT COLOR="#000000">In the
+dialog which appears select the HelloNetBeans.doMethod and add to
+scripts , select OK.</FONT> <BR><FONT COLOR="#000000">A HelloNetBeans
+parcel file should be built.</FONT> 
+</P>
+<P><FONT COLOR="#000000">4. Right click on the Hello NetBeans parcel
+file and select Deploy to Office Document, select the previously
+saved</FONT> <BR><FONT COLOR="#000000">test document i.e.
+</FONT>TestBindNB.sxw<FONT COLOR="#000000">.</FONT> 
+</P>
+<P><FONT COLOR="#000000">5. Check that the script has been
+successfully deployed to the document by running unzip -l&nbsp;
+</FONT>TestBindNB.sxw<FONT COLOR="#000000">. (Unix) or pkunzip -v&nbsp;
+</FONT>TestBindNB.sxw <FONT COLOR="#000000">(Windows). You should see
+the script saved in the document.</FONT> 
+</P>
+<P><FONT COLOR="#000000">6. Assign an event&nbsp; to execute the
+script.</FONT> <BR><FONT COLOR="#000000">- Start OpenOffice.org&nbsp;
+writer document.</FONT> <BR><FONT COLOR="#000000">- Select Tools,
+Assign Script(java) To, Menu.</FONT> <BR><FONT COLOR="#000000">- In
+the popup dialog,</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
+in the select script function select a script e.g.
+HelloNetBeans.doMethod</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+Select File in the Top Level menu drop down list.</FONT> <BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;
+In the New Menu, enter a menu item name e.g. HelloNetBeans.</FONT>
+<BR><FONT COLOR="#000000">&nbsp;&nbsp;&nbsp; Select New Script Menu,
+select ok.</FONT> <BR><FONT COLOR="#000000">- Select OK when prompted
+to restart OpenOffice.org. Exit and restart OpenOffice.org writer
+document.</FONT> <BR><FONT COLOR="#000000">- Select File,
+HelloNetBeans - Hello NetBeans should be inserted into the document.</FONT>
+<BR>&nbsp; 
+</P>
+<HR>
+<HR>
+<P><BR>&nbsp; <BR>&nbsp; 
+</P>
+<H1 ALIGN=CENTER STYLE="text-decoration: none"><A NAME="netbeans_03"></A>
+Test Case: netbeans_03</H1>
+<H2 STYLE="text-decoration: none">Test Area: Solaris&nbsp; - Linux -
+Windows</H2>
+<P><B><FONT COLOR="#000000">Test Aim</FONT></B> <BR><FONT COLOR="#000000">Delete
+a script&nbsp; deployed to a document&nbsp; using NetBeans.</FONT> 
+</P>
+<P STYLE="margin-bottom: 0cm"><B><FONT COLOR="#000000">Prerequisits</FONT></B>
+<BR><FONT COLOR="#000000"><A HREF="#netbeans_02">netbeans_02</A> is
+executed before running this test case.</FONT> 
+</P>
+<HR>
+<P>1. Start NetBeans. <BR>Mount the file system where&nbsp;<FONT COLOR="#000000">
+</FONT>TestBindNB.sxw<FONT COLOR="#000000">. is stored.</FONT> 
+</P>
+<P><FONT COLOR="#000000">2. Expand the file TestBindNB.sxw file .
+Right click on the PARCEL_FILE and select Delete.</FONT> 
+</P>
+<P><FONT COLOR="#000000">3. The Script saved in the office document
+TestBindNB.sxw should now be deleted.</FONT> 
+</P>
+<P><FONT COLOR="#000000">4. Check that it is deleted by running unzip
+-l </FONT>TestBindNB.sxw<FONT COLOR="#000000">. (Unix) or pkunzip -v
+</FONT>TestBindNB.sxw <FONT COLOR="#000000">(Windows). You should see
+that&nbsp; the previously saved&nbsp; script in the document is now
+gone.</FONT> 
+</P>
+<HR>
+<HR>
+<P><BR>&nbsp; 
+</P>
+</BODY>
+</HTML>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/developer-guide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/developer-guide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/developer-guide.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/developer-guide.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,267 @@
+<html>
+<head>
+<title>General Developer Guidelines</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+
+<body>
+
+<h1>General Developer Guidelines</h1>
+         
+<h2>Writing Office scripts and the XScriptContext type</h2>
+
+All Java script methods must pass in XScriptContext as their first
+parameter. The developer can then use accessor functions on the scripting
+context to get at the document context, desktop and component factory
+as follows:
+
+<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>
+
+<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>
+
+<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>
+</ul>
+
+The 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;
+</pre>
+</font>
+
+Example usage in a Java script method to access a Writer document and
+insert some text:
+
+<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.framework.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>
+
+<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.
+
+<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.
+</ul>
+
+<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;
+&lt;!-- DTD for Parcel Meta data for use in the OpenOffice.org Scripting Framework Project --&gt;
+&lt;!ELEMENT logicalname EMPTY&gt;
+&lt;!ELEMENT description (#PCDATA)&gt;
+&lt;!ELEMENT displayname EMPTY&gt;
+&lt;!ELEMENT locale (displayname?, description?)&gt;
+&lt;!ELEMENT functionname EMPTY&gt;
+&lt;!ELEMENT prop EMPTY&gt;
+&lt;!ELEMENT languagedepprops (prop+)&gt;
+&lt;!ELEMENT file (prop*)&gt;
+&lt;!ELEMENT fileset (file+)&gt;
+&lt;!ELEMENT script (locale+, functionname, logicalname, languagedepprops*, fileset*)&gt;
+&lt;!ELEMENT parcel (script+)&gt;
+&lt;!ATTLIST logicalname
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST displayname
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST locale
+	lang CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST functionname
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST logicalname
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST prop
+	name CDATA #REQUIRED
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST file
+	name CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST fileset
+	name CDATA #IMPLIED
+&gt;
+&lt;!ATTLIST script
+	language CDATA #REQUIRED
+&gt;
+</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;
+&lt;!--Sample Meta Data for use with the Scripting Framework Project in OpenOffice.org --&gt;
+&lt;!DOCTYPE parcel SYSTEM "parcel.dtd"&gt;
+&lt;parcel&gt;
+	&lt;script language="java"&gt;
+		&lt;locale lang="english"&gt;
+			&lt;displayname value="Memory.usage"/&gt;
+			&lt;description&gt;
+				Displays the memory current memory usage
+			&lt;/description&gt;
+		&lt;/locale&gt;
+		&lt;functionname value="memoryUtils.memoryUsage"/&gt;
+		&lt;logicalname value="MemoryUtils.MemUsage"/&gt;
+		&lt;languagedepprops&gt;
+			&lt;prop name="classpath" value="/opt/foo.jar:/usr/java/src.jar"/&gt;
+		&lt;/languagedepprops&gt;
+		&lt;fileset&gt;
+			&lt;file name="mems.txt"&gt;
+				&lt;prop name="type" value="resource"/&gt;
+			&lt;/file&gt;
+		&lt;/fileset&gt;
+	&lt;/script&gt;
+&lt;/parcel&gt;
+</pre>
+
+
+<a name="bindscripts"></a>
+<h2>How to Bind Scripts</h2>
+
+<a name="menubind"></a>
+<b>Binding scripts to Menu items</b>
+<ul>
+<li>Start OpenOffice.org and open an existing document or create
+a new one.
+
+<li>Select the menu item Tools/Assign Scripts (Java) To/Menu...
+
+<li>In the &quot;Assign Scripts (Java) To Menu&quot; dialog that pops up
+do the following:
+
+<ul>
+<li><i>Select script function</i>
+  <ul><li>Select the script function that you require from the list.
+  </ul>
+
+<li><i>Choose the menu to insert the script menu after</i>
+  <ul><li>Select the top level menu and submenu under which you want
+          to place your new menu item.
+  </ul>
+
+<li><i>Assign script to new menu</i>
+  <ul><li>In the New Menu text field enter the label you want for your
+          menu item
+      <li>Click New Script Menu to create the new script menu item.
+  </ul>
+</ul>
+
+<li>Finally click on the OK button to save your new script menu item.
+
+<li>Restart OpenOffice.org and open a document
+
+<li>Your new menu item will now be available and clicking on it will
+invoke the Java script.
+</ul>
+
+
+<a name="keybind"></a>
+<b>Binding scripts to Shortcut Keys</b>
+<ul>
+<li>Start OpenOffice.org and open an existing document or create
+a new one.
+
+<li>Select the menu item Tools/Assign Scripts (Java) To/Key...
+
+<li>In the &quot;Assign Scripts (Java) To Key&quot; dialog that pops up
+do the following:
+
+<ul>
+<li><i>Select script function</i>
+  <ul><li>Select the script function that you require from the list.
+  </ul>
+
+<li><i>Choose the Shortcut key to bind the script to</i>
+  <ul><li>Select one of the Key Groups (e.g. SHIFT + CONTROL + digits)
+      <li>Select a key from the Shortcut Keys.
+  </ul>
+
+<li><i>Assign script to shortcut key:</i>
+  <ul<li>Click New Script Key to create the new script Shortcut key.
+  </ul>
+</ul>
+
+<li>Finally click on the OK button to save your new script shortcut key.
+
+<li>Restart OpenOffice.org and open a document
+
+<li>Pressing your new script shortcut key will invoke the Java script.
+</ul>
+
+<b>Note:</b> Menu items and Shortcut keys are not updated on the fly, hence the
+          need to restart, this will be addressed in a future release.
+
+<hr>
+Last Modified: 
+Wed Jan 15 16:25:01 GMT 2003
+</body>
+</html>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/developer-release-features.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/developer-release-features.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/developer-release-features.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/developer-release-features.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,75 @@
+<html>
+<head>
+<title>Features for Early Developer Release</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+
+<body>
+<h1>Features for Early Developer Release of the
+Office Scripting Framework (Version 0.1)</h1>
+
+<h2>Framework</h2>
+
+Supports the loading of different language Runtimes to allow the
+invocation of scripts written in a specific language. These scripts can
+be deployed within the OpenOffice.org installation (user or share area)
+or in a document. The current release provides a Java Runtime.
+
+<p>
+<b>Note:</b> IDE add-ins will only allow deployment of Java
+scripts to the user area of an Office installation or to a document.
+
+<h2>Language Runtime</h2>
+
+The Java Runtime will dynamically load a Java script and any
+supporting classes it requires, invoke the script and provide the script
+with access to the current OpenOffice.org document which it can manipulate
+using the Java UNO API.
+
+<h2>IDE Add-ins</h2>
+
+Integration modules for NetBeans and JEdit. The user can create a new Java
+script parcel which contains one or more Java classes. They can export any
+public methods from these classes as scripts, during deployment, as long
+as the method takes a Scripting Context as its first parameter. Using
+this Scripting Context object within these methods, they can access the
+current OpenOffice.org document and use the Java UNO API to manipulate it.
+
+<p>
+By installing the ODK for OpenOffice.org, the user has full access to
+online help and code completion within any scripts written in Java they
+are writing.
+
+<p>
+The IDE fully supports debugging Java applications and as a result it is
+possible to interactively debug your OpenOffice.org scripts written in
+Java. Just set a breakpoint, bind to the running JVM in OpenOffice.org,
+invoke the script in this OpenOffice.org and step through the code in the
+IDE. 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>
+
+<h2>Binding</h2>
+
+Ability to assign scripts written in Java to menu and key bindings
+from OpenOffice.org Tools/Assign Script menu (invokes a custom Assign
+dialog written in StarBasic)
+
+<p>
+<b>Note:</b> Bindings are stored in the application configuration settings
+from the Assign dialog . The cannot be stored directly in a document.
+
+<h2>Security</h2>
+
+Security in the Early Developer Release will be provided in the form of a
+nag dialog which will be popped up every time a user attempts to run a
+script from within a document. The nag dialog is not displayed when
+invoking application scripts deployed to the user or share area.
+
+<hr>
+Last Modified: Fri Nov 29 14:19:53 GMT 2002
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.1/developer-release-features.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message