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 [12/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/release-0.2/SmokeTest.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/SmokeTest.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/SmokeTest.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/SmokeTest.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,928 @@
+<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head>
+            
+  <meta http-equiv="Content-Type"
+ content="text/html; charset=iso-8859-1">
+            
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=iso-8859-1">
+            
+  <meta name="GENERATOR"
+ content="Mozilla/4.79C-CCK-MCD  [en] (X11; U; SunOS 5.8 sun4u) [Netscape]">
+            
+  <meta name="AUTHOR" content="Robert.Kinsella@Sun.COM">
+            
+  <meta name="CREATED" content="20010103;10350500">
+            
+  <meta name="CHANGED" content="20021008;17390600">
+  <title>Smoke Test</title>
+                   
+  <style>
+	<!--
+		TD P { color: #000000 }
+		H1 { color: #3333dd }
+		P { color: #000000 }
+		H2 { color: #3333dd }
+		A:link { color: #ff0000 }
+		A:visited { color: #551a8b }
+	-->
+	</style> 
+      
+  <style>
+	<!--
+		H1 { color: #3333dd }
+		P { color: #000000 }
+		H2 { color: #3333dd }
+		A:link { color: #ff0000 }
+		A:visited { color: #551a8b }
+	-->
+	</style>
+      
+  <style>
+	<!--
+		H1 { color: #3333dd }
+		P { color: #000000 }
+		H2 { color: #3333dd }
+		A:link { color: #ff0000 }
+		A:visited { color: #551a8b }
+	-->
+	</style>
+</head>
+  <body text="#000000" bgcolor="#ffffff" link="#ff0000" vlink="#551a8b"
+ lang="en-US">
+   &nbsp;   
+<table cols="1" width="100%" nosave="">
+   <tbody>
+      <tr nosave="">
+   <td nosave="">&nbsp;</td>
+   </tr>
+    <tr nosave="">
+   <td nosave="">               
+      <center><b><font color="#000000"><font size="+3">Smoke Tests for OpenOffice.org 
+ Scripting FrameWork</font></font></b></center>
+   </td>
+   </tr>
+         
+  </tbody>  
+</table>
+      
+<center>  
+<table border="1" cellspacing="3" cellpadding="2" width="80%">
+   <caption>&nbsp;</caption>  <tbody>
+      <tr>
+   <td width="11%"><font size="+0"><a href="#README">README</a></font></td>
+    <td width="89%">Outline the order by which the installs of various components 
+ must occur.</td>
+   </tr>
+    <tr>
+   <td width="11%"><font size="+0"><a href="#install_01">Install_01</a></font></td>
+    <td width="89%"><font size="+0">Test the SFrameworkInstall.jar file when 
+ deployed will present to the user options to allow a script to be bound to
+an event.&nbsp;</font> <br>
+        <font size="+0">Also test&nbsp; that scripting framework office.jar
+ file is successfully deployed to NetBeans.&nbsp;</font><br>
+        </td>
+   </tr>
+    <tr>
+   <td width="11%"><font size="+0"><a href="#install_02">Install_02</a></font></td>
+    <td width="89%"><font size="+0">Test the SFrameworkInstall.jar&nbsp;
+will  sense directory names longer than 8 characters.&nbsp;</font></td>
+   </tr>
+    <tr>
+   <td width="11%"><font size="+0"><a href="#install_03">Install_03</a></font></td>
+    <td width="89%"><font size="+0">Test the SFrameworkInstall.jar&nbsp;
+will  sense directory names which contain a space character.&nbsp;</font></td>
+   </tr>
+      <tr>
+   <td width="11%"><br>
+        </td>
+    <td width="89%"><br>
+        </td>
+   </tr>
+    <tr>
+   <td width="11%"><font size="+0"><a href="#bindings_01">Bindings_01</a></font></td>
+    <td width="89%"><font size="+0">Test that the user can assign a deployed 
+ script to a key.&nbsp;</font></td>
+   </tr>
+    <tr>
+   <td width="11%"><font size="+0"><a href="#bindings_02">Bindings_02</a></font></td>
+    <td width="89%"><font size="+0">Test that the user can&nbsp; remove an
+ assigned key.&nbsp;</font></td>
+   </tr>
+    <tr>
+   <td width="11%"><font size="+0"><a href="#bindings_03">Bindings_03</a></font></td>
+    <td width="89%"><font size="+0">Test that the user can assign a deployed 
+ script to the File menu item.&nbsp;</font></td>
+   </tr>
+    <tr>
+   <td width="11%"><font size="+0"><a href="#bindings_04">Bindings_04</a></font></td>
+    <td width="89%"><font size="+0">Test that the user can delete an assigned 
+ File menu item.&nbsp;</font></td>
+   </tr>
+    <tr>
+   <td width="11%"><font size="+0"><a href="#bindings_05">Bindings_05</a></font></td>
+    <td width="89%"><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></td>
+   </tr>
+      <tr>
+   <td><br>
+        </td>
+    <td><br>
+        </td>
+   </tr>
+            <tr>
+   <td width="11%"><font size="+0"><a href="#netbeans_01">NetBeans_01</a></font></td>
+    <td width="89%"><font color="#000000">Compile and deploy a java script 
+to the application user area using NetBeans.</font></td>
+   </tr>
+    <tr>
+   <td><a href="#netbeans_02">NetBeans_02</a></td>
+    <td><font color="#000000">Compile and deploy a java script to a document&nbsp; 
+ using NetBeans.</font></td>
+   </tr>
+    <tr>
+   <td><a href="#netbeans_03">NetBeans_03</a></td>
+    <td><font color="#000000">Delete a script&nbsp; deployed to a document&nbsp; 
+ using NetBeans.</font></td>
+   </tr>
+      <tr>
+        <td valign="top"><a href="#netbeans_04">NetBeans_04</a><br>
+        </td>
+        <td valign="top">Generate and deploy a script using the command line
+ interface<br>
+        </td>
+      </tr>
+         
+  </tbody>  
+</table>
+  </center>
+      
+<center>   
+<h1 style="text-decoration: none;">    
+<hr width="100%">   
+<hr width="100%"></h1>
+  </center>
+      
+<center>   
+<h1 style="text-decoration: none;"> <a name="README"></a><font
+ color="#000000">Test Case: README</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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 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 Scripting Framework from http://framework.openoffice.org/scripting/</font> 
+ <br>
+  <font color="#000000">Download OpenOffice.org 1.1Beta or later from http://www.openoffice.org</font> 
+ <br>
+   </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><font color="#000000">1. Install NetBeans</font> <br>
+  <font color="#000000">2.&nbsp; Start NetBeans, cd to the install-dir/bin 
+and execute runide.sh for unix systems,</font> <br>
+  <font color="#000000">select runide.exe for windows. exit NetBeans.</font> 
+ <br>
+  <font color="#000000">3.&nbsp; Install OpenOffice.org.</font> <br>
+  <font color="#000000">4.&nbsp; Copy&nbsp; the SFrameworkInstall.jar file
+ to the users home directory.</font> <br>
+   </p>
+   
+<hr>   
+<hr>   
+<h1 style="text-decoration: none;" align="center">  </h1>
+ 
+<h1 style="text-decoration: none;"> <a name="install_01"></a><small><font
+ color="#000000">Test Case: install_01</font></small></h1>
+       
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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 office.jar 
+ files is successfully deployed to NetBeans.</font>    
+<p style="margin-bottom: 0cm;"><b><font color="#000000">Requirements</font></b> 
+ <br>
+  <font color="#000000"><a
+ href="file:///home/rk99157/Apachetest/OpenOffice/assertions/scripting/SmokeTest0.2.html#README">README 
+ </a>is performed before running this test case.</font> <br>
+   </p>
+   
+<hr>    
+<p><b><font color="#000000">Description:</font></b> <br>
+  <font color="#000000">1. Copy the SFrameworkInstall.jar file to the user's
+ home&nbsp; directory.</font> <br>
+  <font color="#000000">2. Ensure OpenOffice.org 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 NetBeans installation,
+ select Next.</font> <br>
+  <font color="#000000">8. Select the IDE's for update, i.e. NetBeans, select
+ Next, Select Install, Select Finish<br>
+   9. 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">10. Manually check that the SFrameworkInstall.log 
+file was writter to the users home directory.</font> <br>
+  <font color="#000000">11. Start OpenOffice.org, select Tools, there should
+ be an entry - Scripting Add On's</font><br>
+  <font color="#000000">12. Select Tools, Scripting Add On's, Interactive 
+Beanshell Scripting, &nbsp;An interactive beanshell editor window 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>
+   
+<p> </p>
+   
+<center></center>
+  <br>
+     
+<hr width="100%"> <br>
+  &nbsp; <br>
+  &nbsp;   
+<center>   
+<h1 style="text-decoration: none;"> <a name="install_02"></a><font
+ color="#000000">Test Case: install_02</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Windows</font></h2>
+   <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 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">NetBeans installation path directory has a name which
+ is nine characters or more.</font> <br>
+   </p>
+   
+<hr>    
+<p><b><font color="#000000">Description:</font></b> <br>
+  <font color="#000000">1. Copy the SFrameworkInstall.jar file to the user's
+ home directory.</font> <br>
+  <font color="#000000">2. Ensure OpenOffice.org 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; a NetBeans installation, select
+ Next.</font> <br>
+  <font color="#000000">8. Select the IDE's for update, i.e. NetBeans, select
+ Next, Select Install, Select Finish.<br>
+  9. 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">10. Start OpenOffice.org, select Tools,&nbsp;</font><font
+ color="#000000"> there should be an entry - Scripting Add On's</font><br>
+  <font color="#000000">11. Select Tools, Scripting Add On's, Interactive 
+Beanshell Scripting, &nbsp;An interactive beanshell editor window should be
+launched.</font>   <font color="#000000"></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> <br>
+  &nbsp; <br>
+  &nbsp;   
+<center>   
+<h1 style="text-decoration: none;"> <a name="install_03"></a><font
+ color="#000000">Test Case: install_03</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Windows</font></h2>
+   <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 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">NetBeans installation path directory has a name which
+ contains a space character.</font> <br>
+   </p>
+   
+<hr>    
+<p><b><font color="#000000">Description:</font></b> <br>
+  <font color="#000000">1. Copy the SFrameworkInstall.jar file to the user's
+ home&nbsp; directory.</font> <br>
+  <font color="#000000">2. Ensure OpenOffice.org 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; a NetBeans installation, select
+ Next.</font> <br>
+  <font color="#000000">8. Select the IDE's for update, i.e. NetBeans, select
+ Next, Select Install, Select Finish<br>
+  9. 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">10. Start OpenOffice.org, select Tools,&nbsp;</font><font
+ color="#000000"> there should be an entry - Scripting Add On's</font><br>
+  <font color="#000000">11. Select Tools, Scripting Add On's Interactive
+Beanshell  Scripting, &nbsp;An interactive beanshell editor window should
+be launched.</font>   <font color="#000000"></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> 
+ <br>
+   </p>
+   
+<hr>   
+<hr> <br>
+  &nbsp;&nbsp;  
+<center></center>
+  <br>
+  &nbsp; <br>
+  &nbsp;   
+<center>   
+<h1 style="text-decoration: none;"> <a name="bindings_01"></a><font
+ color="#000000">Test Case: bindings_01</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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 style="margin-bottom: 0cm;"><font color="#000000">Prerequisites:-</font> 
+ <br>
+  <font color="#000000"><a href="#install_01">install_01 </a>is executed
+before  running this test case.</font> <br>
+   </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 - Script Add On's, Assign Script
+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 <br>
+  &nbsp; &nbsp; Location- User<br>
+  &nbsp; &nbsp; Language- Java<br>
+  &nbsp; &nbsp; Script -&nbsp; 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; SelectAssign Key.</font> <br>
+  <font color="#000000">4. The Key should now be assigned to HighlightText.showForm. 
+ Select OK.</font> <br>
+  <font color="#000000">5. </font><font color="#000000">Select Shift - Control
+ - F3. The Highlight Text box dialog should be displayed.</font> <br>
+  <font color="#000000">6. Select Tools - </font><font color="#000000">Script
+ Add On's -&nbsp; Assign Script to Key.</font><font color="#000000"> <br>
+  SHIFT-CONTROL-F3 should be listed as assigned to HighlightText.showForm. 
+Close the Assign Script 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> 
+ <br>
+   </p>
+  <br>
+     
+<hr> <br>
+  &nbsp; <br>
+  &nbsp;   
+<center>   
+<h1 style="text-decoration: none;"> <a name="bindings_02"></a><font
+ color="#000000">Test Case: bindings_02</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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 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> <br>
+   </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 - </font><font color="#000000">Script
+ Add On's - Assign Script 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">6. Select Shift - Control - F3. The Highlight Text
+ box dialog should be not&nbsp; displayed.</font> <br>
+  <font color="#000000">7. Select Tools -</font><font color="#000000">Script
+ Add On's - Assign Script to Key</font><font color="#000000"> , <br>
+  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">8. 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">9. 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> 
+ <br>
+   </p>
+   
+<hr>  <br>
+  &nbsp; <br>
+  &nbsp;   
+<center>   
+<h1 style="text-decoration: none;"> <a name="bindings_03"></a><font
+ color="#000000">Test Case: bindings_03</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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 style="margin-bottom: 0cm;"><font color="#000000">Prerequisites:-</font> 
+ <br>
+  <font color="#000000"><a href="#install_01">install_01 </a>is executed
+before  running this test case</font> <br>
+   </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, Scripting Add On's, Assign Script
+ to Menu.</font><br>
+  <font color="#000000">3. In the popup dialog,</font> select<br>
+  &nbsp; &nbsp; Location - User<br>
+  &nbsp; &nbsp; Language - Java<br>
+  &nbsp; &nbsp; Script - <font color="#000000"> HighlightText.showForm</font><br>
+  <font color="#000000">&nbsp; &nbsp; Select File in the Top Level menu drop
+ down list.</font> <br>
+  <font color="#000000">&nbsp;&nbsp;&nbsp; In the New Menu dialog box , enter
+ a menu item name e.g. menuhighlight.</font> <br>
+  <font color="#000000">&nbsp;&nbsp;&nbsp; Select New, select ok.</font>
+<font color="#000000"><br>
+  4. 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> 
+ <br>
+   </p>
+   
+<hr>  <br>
+  &nbsp; <br>
+  &nbsp;   
+<center>   
+<h1 style="text-decoration: none;"> <a name="bindings_04"></a><font
+ color="#000000">Test Case: bindings_04</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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 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> <br>
+   </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. </font><font color="#000000">Select Tools, Scripting
+ Add On's, Assign Script to Menu.</font><br>
+  <font color="#000000">3. In the popup dialog,</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 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 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> 
+ <br>
+   </p>
+   
+<hr>  <br>
+  &nbsp; <br>
+  &nbsp;   
+<center>   
+<h1> <a name="bindings_05"></a><font color="#000000">Test Case: bindings_05</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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 style="margin-bottom: 0cm;"><font color="#000000">Prerequisites:-</font> 
+ <br>
+  <font color="#000000">&nbsp;<a href="#install_01">install_01 </a>is executed
+ before running this test case.</font> <br>
+   </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>
+   
+<div style="margin-bottom: 0cm;"><font color="#000000"><font size="+0">All 
+ operations should complete successfully.</font></font></div>
+      
+<center>   
+<h1 style="text-decoration: none;">    
+<hr width="100%">  
+<hr width="100%"></h1>
+  </center>
+   
+<center>  
+<h1 style="text-decoration: none;"><br>
+   </h1>
+  <br>
+  <br>
+  </center>
+     
+<center>   
+<h1 style="text-decoration: none;"> <a name="netbeans_01"></a><font
+ color="#000000">Test Case: netbeans_01</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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><b><font color="#000000">Prerequisits</font></b> <br>
+  <font color="#000000"><a href="#install_01">install_01 </a>is executed
+before  running this test case.</font> <br>
+  <a
+ href="http://framework.openoffice.org/scripting/release-0.2/netbeans-devguide.html#prerequisites">http://framework.openoffice.org/scripting/release-0.2/netbeans-devguide.html#prerequisites</a><br>
+   </p>
+   
+<hr>    
+<p style="text-decoration: none;"><b><font color="#000000">Description:</font></b> 
+ <br>
+  &nbsp; </p>
+   
+<ol start="2">
+    <font color="#000000">1. Create an examples directory e.g. HelloNetBeans.#</font> 
+   <br>
+    <font color="#000000">Start NetBeans.</font>       
+  <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, "Hello NetBeans", 
+ 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, user.</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, </font><font color="#000000">Scripting
+ Add On's, Assign Script to Menu.</font><br>
+    <font color="#000000">- In the popup dialog,</font> select<br>
+  &nbsp; &nbsp;Location - user<br>
+  &nbsp; &nbsp;Language - Java<br>
+  &nbsp; &nbsp;Script HelloNetBeans.doMethod<br>
+    <font color="#000000">&nbsp;&nbsp; Select File in the Top Level menu
+drop  down list.</font> <br>
+    <font color="#000000">&nbsp; In the New Menu, enter a menu item name
+e.g.  HelloNetBeans.</font> <br>
+    <font color="#000000">&nbsp; Select New, select ok.</font> <br>
+    <font color="#000000">- Select File, HelloNetBeans - Hello NetBeans should
+ be inserted into the document.</font></p>
+   
+</ol>
+   <b><font color="#000000">Expected Result:</font></b> <br>
+  &nbsp;   
+<p><font color="#000000">All operations should complete successfully.</font> 
+ <br>
+   </p>
+     
+<hr> <br>
+  &nbsp; <br>
+  &nbsp;   
+<center>   
+<h1 style="text-decoration: none;"> <a name="netbeans_02"></a><font
+ color="#000000">Test Case: netbeans_02</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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><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 
+<br>
+   </p>
+   
+<hr> <br>
+  &nbsp;   
+<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 "Hello NetBeans" line to "Hello NetBeans 
+ 2 ----"</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> 
+<font color="#000000">test document i.e. </font>TestBindNB.sxw<font
+ color="#000000">. A warning dialog should warn the user that the douemnt
+ should not already be opened in OpenOffice.org. If the document is opened,
+ close it and select ok.</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">- Open the TestBindNB.sxw test document.</font> <br>
+  <font color="#000000">- Select Tools,&nbsp;</font><font
+ color="#000000">Scripting  Add On's, Assign Script to Menu.</font> <br>
+  <font color="#000000">- In the popup dialog,</font> select<br>
+  <font color="#000000">&nbsp; &nbsp;Location - Document,<br>
+  &nbsp; &nbsp;Language - Java,<br>
+  &nbsp; &nbsp;Script-&nbsp; HelloNetBeans.doMethod</font> <br>
+  <font color="#000000">&nbsp;&nbsp; Select File in the Top Level menu drop
+ down list.</font> <br>
+  <font color="#000000">&nbsp;&nbsp; In the New Menu, enter a menu item name
+ e.g. HelloNetBeans.</font> <br>
+  <font color="#000000">&nbsp;&nbsp; Select New, select ok.</font> <br>
+  &nbsp; <br>
+  <font color="#000000">- Select File, HelloNetBeans - Hello NetBeans 2 ---- 
+ should be inserted into the document.</font> <br>
+  &nbsp; </p>
+   
+<p> </p>
+   
+<hr> <br>
+  &nbsp; <br>
+  &nbsp;   
+<center>   
+<h1 style="text-decoration: none;"> <a name="netbeans_03"></a><font
+ color="#000000">Test Case: netbeans_03</font></h1>
+  </center>
+      
+<h2 style="text-decoration: none;"> <font color="#000000">Test Area: Solaris&nbsp;
+ - Linux - Windows</font></h2>
+   <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><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> <br>
+   </p>
+   
+<hr>   
+<p>1. Start NetBeans. <br>
+  Mount the file system where&nbsp;<font color="#000000"> </font>TestBindNB.sxw<font
+ color="#000000">. is stored. If TestBindNB.sxw is opened in OpenOffice.org,
+ close it.</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>
+   
+<p> </p>
+     
+<hr> <br>
+   
+<div align="center">&nbsp;   <b><big></big></b>   
+<h1 style="text-decoration: none;">&nbsp; <a name="netbeans_04"></a><font
+ color="#000000"><b><big><big><big>Test Case : netbeans_04</big></big></big></b></font><br>
+  </h1>
+ </div>
+  <br>
+  <br>
+  <b>Test Aim</b><br>
+  Generate and deploy a script using the command line interface.<br>
+  <br>
+  <b>Prerequisits</b><br>
+  <a href="#netbeans_03">netbeans_03</a> is executed before running this
+test  case.<br>
+<a
+ href="http://framework.openoffice.org/scripting/release-0.2/commandline-devguide.html#prereqs">http://framework.openoffice.org/scripting/release-0.2/commandline-devguide.html#prereqs</a><br>
+  Set the users CLASSPATH to include <br>
+  &lt;netbeans-install-dir&gt;/modules.jar<br>
+  all jar files &lt;office-install-dir&gt;/program/classes/&nbsp; directory.<br>
+  all jar files in the xerces installation path directory.<br>
+  <br>
+  1. Create a new examples directory, e.g. examplesCLI. Create a Contents 
+directory in examplesCLI.<br>
+  2. Copy the <font color="#000000">HelloNetBeans.java </font>and <font
+ color="#000000">HelloNetBeans.class path from the examples directory (HelloNetBeans)
+ previously </font>generated in netbeans_02 to the newly created Contents 
+directory in examplesCLI.<br>
+  3. Enter the command 'java CommandLineTools -g &nbsp;examplesCLI -l Java'.<br>
+  You should be prompted that a examplesCLI.sxp file has been generated.<br>
+  4. Enter the command 'java CommandLineTools -d &lt;absolute path&gt;/examplesCLI.sxp
+ &lt;office-install-dir/share/Scripts.<br>
+  5. Start OpenOffice.org, Select Tools, Scripting Add On's, Assign Script
+ to Menu.<br>
+  Select,<br>
+  Location - Share<br>
+  Language - Java<br>
+  Script - HelloNetBeans.doMethod<br>
+  <br>
+  Create a binding to the File menu, and execute it. HelloNetBeans 2 ---- 
+should be entered in the text document.<br>
+  <br>
+  <br>
+  <br>
+ <br>
+</body>
+</html>

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

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

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/assign-event.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

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

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/assign-menu.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/build-guide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/build-guide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/build-guide.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/build-guide.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,472 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.1 Beta 1 (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 LANG="en-US" DIR="LTR">
+<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><P STYLE="margin-bottom: 0in"><A HREF="#projects">Projects &amp;
+		Modifications</A> 
+		</P>
+		<LI><P STYLE="margin-bottom: 0in"><A HREF="#Building the Scripting Framework for OpenOffice.org|outline">Building
+		</A>
+		</P>
+	</UL>
+	<LI><P STYLE="margin-bottom: 0in">Installation 
+	</P>
+	<UL>
+		<LI><P STYLE="margin-bottom: 0in"><A HREF="#autoinstaller">Building
+		Automated Installer</A></P>
+		<LI><P><A HREF="#install">Manual&nbsp;install</A> 
+		</P>
+	</UL>
+</UL>
+<H2><A NAME="Pre-requisites"></A>Pre-requisites</H2>
+<UL>
+	<LI><P STYLE="margin-bottom: 0in">JDK1.3 or greater 
+	</P>
+	<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><P STYLE="margin-bottom: 0in">Full OO1.1beta or later solver and
+	installation set 
+	</P>
+	<LI><P STYLE="margin-bottom: 0in">OO1.1beta or later OpenOffice
+	build environment</P>
+	<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><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>
+	</UL>
+</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><P><TT>offapi</TT> 
+	</P>
+</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><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><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>
+</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><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><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><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><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>
+	</UL>
+	<P STYLE="margin-bottom: 0in"><B>and add</B>
+	&quot;<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>&quot;
+	to the last line before &quot;<TT>NULL</TT>&quot; 
+	</P>
+	<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><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><P STYLE="margin-bottom: 0in"><TT>$(UCR)$/dcsssfprovider.db&nbsp;\</TT>
+				</P>
+		<LI><P STYLE="margin-bottom: 0in"><TT>$(UCR)$/dcsssfsecurity.db&nbsp;\</TT>
+				</P>
+		<LI><P STYLE="margin-bottom: 0in"><TT>$(UCR)$/dcsssfstorage.db</TT>
+				</P>
+	</UL>
+    <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><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>
+	</UL>
+</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><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><P>Alternatively, if you do not wish to build the add-in, delete
+	the following entries from the depends section of the target &quot;all&quot;
+	in the build.xml 
+	</P>
+	<UL>
+		<LI><P>No NetBeans add-in 
+		</P>
+		<UL>
+			<LI><P>localoffice.jar 
+			</P>
+			<LI><P>netbeans.jar 
+			</P>
+		</UL>
+	</UL>
+</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><P>Execute <TT>build and <FONT FACE="Cumberland">deliver</FONT>
+	</TT>in the <TT>unoil</TT> module 
+	</P>
+	<LI><P>Execute <TT>build</TT> in the <TT>scripting</TT> module 
+	</P>
+</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><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><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><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><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><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><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><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><P>Copy <FONT FACE="Cumberland">ProtocolHandler.xcu</FONT> from
+	<FONT FACE="Cumberland">scripting/workben/installer/</FONT>
+	to <FONT FACE="Cumberland">$pkgsf</FONT></P>
+	<LI><P>Now, zip up all files in directory, <FONT FACE="Cumberland">$pkgsf</FONT>
+	to ooscriptf.zip</P>
+	<LI><P>Now, zip up all file in directory, <FONT FACE="Cumberland">$pkgbs</FONT>
+	to bshruntime.zip</P>
+</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><P>In the program directory, run pkgchk on each of the zip files 
+	</P>
+</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><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><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=&quot;ScriptBindingLibrary&quot;
+			xlink:href=&quot;file:://&lt;OpenOffice
+			path&gt;user/basic/ScriptBindingLibrary/script.xlb/&quot;
+			xlink:type=&quot;simple&quot; library:link=&quot;false&quot;/&gt;</FONT></TT></P>
+		</OL>
+		<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=&quot;ScriptBindingLibrary&quot;
+			xlink:href=&quot;file://&lt;OpenOffice
+			path&gt;/user/basic/ScriptBindingLibrary/dialog.xlb/&quot;
+			xlink:type=&quot;simple&quot; library:link=&quot;false&quot;/&gt;</FONT></TT></P>
+		</OL>
+		<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></TT></TT><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 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><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><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><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 &ldquo;.xml&rdquo; 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>
+	</OL>
+</OL>
+<P>The script framework is now installed.</P>
+<TABLE CELLPADDING=4 CELLSPACING=0>
+	<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>
+</TABLE>
+<H2><BR>Last revision: 
+Wed Mar 19 17:39:14 GMT 2003
+</H2>
+</BODY>
+</HTML>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/commandline-devguide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/commandline-devguide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/commandline-devguide.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/commandline-devguide.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,212 @@
+<html>
+<head>
+<title>Developing Scripts on the Command Line</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+
+<body>
+<a name="top"></a>     
+
+<h1>Developing Scripts on the Command Line</h1>
+         
+For users who do not wish to develop their 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>
+<li><p><a href="#usage">The CommandLineTools class</a>
+<li><p><a href="#examples">Examples</a>
+</ul>
+
+<a name="prereqs">
+<h2>Prerequisites</h2>
+
+<ul>
+<li>The Scripting module office.jar file should be included in the
+classpath. You can unpack this file from the Scripting Framework installer
+<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>
+
+<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.
+</ul>
+
+<a name="usage">
+<h2>The CommandLineTools class</h2>
+
+The CommandLineTools class takes the following options (<b>Note: </b>
+Options in angle brackets &quot;<>&quot; are required, options in
+square brackets &quot;[]&quot; are optional):
+
+<blockquote>
+
+<b>-g [Path to Parcel directory] [options]</b>
+
+<p>
+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.
+
+<ul>
+<li>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 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>
+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,
+&quot;:&quot; on Unix, &quot;;&quot; on Windows) will be added as script
+entries to the parcel-descriptor.xml file.
+
+<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>
+
+<table border=1>
+<tr>
+<th>-l flag used?
+<th>parcel-descriptor.xml exists?
+<th>result
+</tr>
+<tr>
+<td align=center>no
+<td align=center>no
+<td>error message printed
+</tr>
+<tr>
+<td align=center>yes
+<td align=center>no
+<td>parcel-descriptor.xml generated<br>parcel.sxp generated
+</tr>
+<tr>
+<td align=center>no
+<td align=center>yes
+<td>parcel-descriptor.xml not generated<br>parcel.sxp generated
+</tr>
+<tr>
+<td align=center>yes
+<td align=center>yes
+<td>if
+<br>language is different from parcel-descriptor.xml language, error
+<br>else
+<br>parcel-descriptor.xml regenerated
+<br>parcel.sxp generated
+</tr>
+</table>
+
+<p>
+<b>[-p name=value]</b>
+
+<p>
+Specifies a name value pair to be added as a language dependent property in
+the parcel-descriptor.xml file
+
+<p>
+<b>[-v]</b>
+
+<p>
+Specifies that verbose output should be displayed.
+</ul>
+
+<p>
+<b>-d &lt;Path to Script Parcel&gt; &lt;Target Directory|Document&gt;</b>
+
+<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.
+
+<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.
+</ul>
+</blockquote>
+<p><a href="#top">Top</a>
+
+<a name="examples">
+<h2>Examples</h2>
+
+<ul>
+
+<li><p><font face="Courier, monospace" size="2">
+java CommandLineTools -g myparceldir -l Java
+</font>
+
+<p>Generates a myparceldir.sxp file in myparceldir automatically exporting
+all public Java methods which take XScriptContext as their first parameter as
+Office scripts.
+
+<p><li><font face="Courier, monospace" size="2">
+java CommandLineTools -g -l BeanShell=.bsh
+</font>
+
+<p>Generates a script parcel file in the current directory
+automatically exporting all files that end with the .bsh extension as
+BeanShell scripts
+
+<p><li><font face="Courier, monospace" size="2">
+java CommandLineTools -g myparceldir -l BeanShell MyScript.bsh
+</font>
+
+<p>Generates a myparceldir.sxp file in myparceldir and exports MyScript.bsh
+as an Office script.
+
+<p><li><font face="Courier, monospace" size="2">
+java CommandLineTools -g myparceldir -l Java -p classpath=dep1.jar:dep2.jar
+</font>
+
+<p>Generates a myparceldir.sxp file in myparceldir, automatically
+searching for valid Office scripts, and adding the classpath property to
+each Office script.
+
+<p><li><font face="Courier, monospace" size="2">
+java CommandLineTools -g myparceldir -l Java -p classpath=dep1.jar:dep2.jar -p secondprop=secondvalue
+</font>
+
+<p>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.
+
+<p><li><font face="Courier, monospace" size="2">
+java CommandLineTools -d myparceldir.sxp /export/home/MyOffice/user/Scripts
+</font>
+
+<p>Deploys the myparceldir.sxp Script Parcel to the specified office directory.
+</ul>
+
+<p><a href="#top">Top</a>
+<hr>
+Last Modified: Tue Mar 12 11:40:28 GMT 2003
+</body>
+</html>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/developer-guide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/developer-guide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/developer-guide.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/developer-guide.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,294 @@
+<html>
+<head>
+<title>Writing Scripts in BeanShell and Java</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+
+<body>
+
+<h1>Writing Scripts in BeanShell and Java</h1>
+         
+<a name="top"></a>
+<h2>Contents</h2>
+
+<ul>
+<li><p><a href="#bsh">Hello World in BeanShell</a>
+<li><p><a href="#bshinvoke">Trying out your BeanShell script</a>
+<li><p><a href="#java">Hello World in Java</a>
+<li><p><a href="#context">Writing Office Scripts and the XScriptContext type</a>
+<li><p><a href="#tips">Tips on writing Office scripts</a>
+<li><p><a href="#dtd">Parcel Descriptor DTD and sample XML</a>
+</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>
+<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;
+
+    model = context.getDocument(); 
+    textdoc = (XTextDocument)
+        UnoRuntime.queryInterface(XTextDocument.class, model);
+
+    oText = textdoc.getText(); 
+    oCursor = oText.createTextCursor(); 
+    oText.insertString(oCursor, "Hello World", false)
+</pre>
+<a href="#top">Top</a>
+
+<a name="bshinvoke"></a>
+<h2>Trying out your BeanShell script</h2>
+
+Trying out your Hello World BeanShell script is easy:
+
+<ul>
+<li>Start OpenOffice.org and open a new Writer document.
+<li>Select the Tools/Scripting Add-on's/Interactive BeanShell Scripting...
+menu item.
+<li>Paste your Hello World code from above into the window that pops up and
+click on the eval button.
+<li>You should see Hello World appear at the start of the Writer document.
+</ul>
+
+<p>
+You can modify the code directly in the evaluation window and click eval again to test it. If you are new to the OpenOffice.org API this is a great way to experiment with it.
+
+<p>
+<b>Note:</b> The Interactive BeanShell window does not report when an error occurs while evaluating your code, so it may fail silently. The best way to trace the execution of your code is to write debug statements into your document from your script, for example:
+
+<pre>
+model = context.getDocument();
+textdoc = (XTextDocument)UnoRuntime.queryInterface(XTextDocument.class, model);
+oText = textdoc.getText();
+oCursor = oText.createTextCursor();
+
+oText.insertString(oCursor, "DEBUG: start", false);
+
+// do something with the API
+
+oText.insertString(oCursor, "DEBUG: did something", false);
+</pre>
+
+<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>
+<a href="#top">Top</a>
+
+<a name="java"></a>
+<h2>Hello World in Java</h2>
+
+Here's the Hello World script in Java:
+
+<p>
+<font face="Courier, monospace" size="2">     
+<pre>
+    import com.sun.star.frame.XModel;
+    import com.sun.star.text.*;
+    import com.sun.star.uno.UnoRuntime;
+    import drafts.com.sun.star.script.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>
+
+<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>
+<a href="#top">Top</a>
+
+<a name="context"></a>
+<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 &quot;context&quot; which can be
+used by the script.
+
+<p>
+The following accessor methods are available on the XScriptContext type:
+
+<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 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;
+</pre>
+</font>
+
+<p>
+<a href="#top">Top</a>
+
+<a name="tips"></a>
+<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>
+
+<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;
+&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;
+&lt;!ATTLIST parcel
+	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 language="Java"&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 href="#top">Top</a>
+
+<hr>
+Last Modified: Tue Mar 12 11:40:28 GMT 2003
+</body>
+</html>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/developer-release-features.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/developer-release-features.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/developer-release-features.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/developer-release-features.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,109 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <title>Features for Early Developer Release</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+ 
+<h1>New Features in this Release</h1>
+
+<ul>
+<li><p><b>Additional language support</b>
+
+<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>
+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).
+
+<li><p><b>Security Enhancements</b>
+
+<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).
+
+<li><p><b>Support for storage of bindings in documents</b>
+
+<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).
+
+<li><p><b>Support for Event Bindings</b>
+
+<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.
+</ul>
+
+<p><b>Notes:</b>
+
+<ul>
+<li>New binding assignments can be made without requiring a restart of
+OpenOffice.org
+<li>Scripts bindings are now fully resolved at binding
+<li>Command line utilities have been added for packaging and deployment
+(see <a href="commandline-devguide.html">
+Developing Scripts without an IDE</a>)
+<li>Support for jEdit IDE has been discontinued
+</ul>
+
+<h1>Features of the Office Scripting Framework</h1>
+  
+<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>
+<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.
+
+<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: Tue Mar 12 11:40:28 GMT 2003
+
+</body>
+</html>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/faq.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/faq.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/faq.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/faq.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,91 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+	<TITLE>FAQ</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="CREATED" CONTENT="20021203;15313500">
+	<META NAME="CHANGED" CONTENT="20030318;19405289">
+</HEAD>
+<BODY LANG="en-US">
+<H1><A NAME="top"></A>Frequently Asked Questions for the Office
+Scripting Framework</H1>
+<H2>Questions</H2>
+<OL>
+	<P STYLE="margin-bottom: 0cm"></P>
+	<LI><P STYLE="margin-bottom: 0cm"><A HREF="#3">I have removed the
+	examples provided with the Script Framework installation and
+	installed my own but the script in ExampleSpreadSheet.sxc still
+	works. Why?</A> 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm"><A HREF="#4">How can I store menu
+	or key bindings for scripting in a document?</A> 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm"><A HREF="#5">Why is there a delay
+	in starting the first script?</A> 
+	</P>
+	<LI><P><A HREF="#6">Why do I have to use one dialog to work with
+	StarBasic macros [Tools/ Configure] and another to work with my new
+	Java scripts [Assign Script...]?</A> 
+	</P>
+</OL>
+<H2>Answers</H2>
+<OL>
+	<LI><P><A NAME="3"></A>I have removed the examples provided with the
+	Script Framework installation and installed my own but the script in
+	ExampleSpreadSheet.sxc still works. Why? 
+	</P>
+	<P>Both the script and the Key bindings are contained in the
+	document itself, at the moment the [Assign Script] dialog does not
+	display scripts or bindings stored in documents. 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><A HREF="#top">Top</A> 
+	</P>
+	<LI><P><A NAME="4"></A>How can I store a script, menu or key
+	bindings for scripting in a document? 
+	</P>
+</OL>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm"><FONT COLOR="#000000">In order to
+	save a script event binding to a menu item or key into a document
+	there are two steps which must be followed. Firstly, set up the
+	binding in the usual way using the &quot;Assign Script To ...&quot;
+	dialog. Then open the Tools-&gt;Configure dialog, and select the
+	&quot;Menu&quot; tab. Click the &quot;Save&quot; button, select the
+	document into which you wish to save the binding, and click &quot;Save&quot;.&nbsp;
+	You will be prompted with a dialog that says &quot;The file already
+	exists. Overwrite?&quot;. It is OK to click &quot;Yes&quot; as this
+	will simply write the bindings into the file. Saving a binding to an
+	event into a document can be done by clicking the &quot;Document&quot;
+	radio button in the &quot;Assign Script to Event&quot; dialog.</FONT></P>
+</UL>
+<OL START=0>
+	<P STYLE="margin-bottom: 0cm"><A HREF="#top">Top</A> 
+	</P>
+	<LI><P><A NAME="5"></A>Why is there a delay in starting the first
+	script? 
+	</P>
+	<P>The delay is caused by the startup of the inprocess JVM by
+	OpenOffice. 
+	</P>
+	<P STYLE="margin-bottom: 0cm"><A HREF="#top">Top</A> 
+	</P>
+	<LI><P><A NAME="6"></A>Why do I have to use one dialog to work with
+	StarBasic macros [Tools/ Configure] and another to work with my new
+	Java scripts [Assign Script...]? 
+	</P>
+	<P>The StarBasic macros are completely separate from and do not use
+	the Scripting Framework. As such they use their own configuration
+	and settings dialogs. In the future the Scripting Framework and
+	StarBasic dialogs will be integrated so users have one consistnet
+	way of working with macros/ scripts, regardless of which language
+	they have been written it. 
+	</P>
+	<P><A HREF="#top">Top</A> 
+	</P>
+</OL>
+<HR>
+<P>Last Modified: Tue Mar 12 11:40:28 GMT 2003 
+</P>
+</BODY>
+</HTML>

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



Mime
View raw message