incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r799253 [15/16] - in /websites/staging/ooo-site/trunk/content/framework: documentation/ documentation/devmanual/ documentation/filters/ documentation/filterui/ documentation/mimetypes/ documentation/others/ drafts/ proposals/ proposals/appl...
Date Fri, 25 Nov 2011 20:05:43 GMT
Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/uninstall-guide.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/uninstall-guide.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/uninstall-guide.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,170 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <title>Uninstalling the Scripting Framework</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<a name="top"></a>
+<h1>Guide for Uninstalling the Office Scripting Framework</h1>
+<!--
+<h2>Contents</h2>
+
+<ul>
+<li><p><a href="#unistall">Uninstalling the Scripting Framework</a>
+</ul>
+-->
+<h2>Uninstalling the Scripting Framework</h2>
+Currently there is no automated process for uninstalling the Scripting
+Framework, so uninstalling must be done manually (the process will be
+automated in a future release). The Scripting Framework will eventually
+be included in the standard OpenOffice.org install/uninstall process.
+<p> To remove the Scripting Framework: </p>
+<ul>
+  <li>Delete the files:
+    <ul>
+      <li>&lt;Office
+Installation&gt;/user/uno_packages/ooscriptframe.zip </li>
+      <li>&lt;Office Installation&gt;/user/uno_packages/bshruntime.zip</li>
+      <li>&lt;Office Installation&gt;/user/uno_packages/jsruntime.zip</li>
+      <li>&lt;Office Installation&gt;/user/basic/ScriptBindingLibrary/
+(delete entire directory) </li>
+      <ul>
+        <li>You may also delete the line referring to <font
+ face="Courier, monospace" size="2">library:name="ScriptBindingLibrary"</font>
+in script.xlc and dialog.xlc found in &lt;Office
+Installation&gt;/user/basic/ directory.            This will remove the
+entry for ScriptBindingLibrary in Tools-&gt;Macro</li>
+      </ul>
+      <li>&lt;Office
+Installation&gt;/share/registry/schema/org/openoffice/Office/Scripting.xcs</li>
+      <li>&lt;Office Installation&gt;/user/registry/data/org/openoffice/Office/Scripting.xcu</li>
+    </ul>
+  </li>
+  <li>Switch to the &lt;Office Installation&gt;/program directory and
+run the command: <font face="Courier, monospace" size="2">pkgchk</font>
+    <ul>
+      <li>On Windows: <font face="Courier, monospace" size="2">pkgchk.exe</font></li>
+      <li>On Solaris/Linux: <font face="Courier, monospace" size="2">./pkgchk</font></li>
+    </ul>
+  </li>
+  <li>Use the Tools/Configure dialog to remove the "Scripting Add-ons"
+entry in the Tools menu.</li>
+</ul>
+<p> If you wish to remove any scripts from your installation they are
+stored in the directories: </p>
+<ul>
+  <li>&lt;Office Installation&gt;/user/Scripts </li>
+  <li>&lt;Office Installation&gt;/share/Scripts </li>
+</ul>
+<!-- Use bak files in <office>/user/config/soffice.cfg/*xml -->
+<p> To remove any menu, key or event bindings that you have set up for
+Office scripts. </p>
+<ul>
+  <li> The original configuration can be restored by removing the files
+used by the Scripting Framework and replacing them with the files that
+were backed up during installation.</li>
+  <li> cd &lt;Office&gt;/user/config/soffice.cfg/ </li>
+  <li> Delete all files that don't end in a .bak extension. </li>
+  <li> Rename the .bak files to their original name (i.e. without the
+.bak extension). </li>
+  <ul>
+    <li>e.g. writermenubar.xml.bak to writermenubar.xml</li>
+  </ul>
+  <li> cd to META-INF </li>
+  <li> Delete manifest.xml </li>
+  <li> If it is there, rename manifest.xml.bak to manifest.xml </li>
+  <li> <b>NOTE:</b> The configuration files are only created when a
+change is made through Tools -&gt; Configure. It is possible that no
+files needed to be backed up during installation of the Scripting
+Framework. </li>
+  <li>List of config files possibly backed up in
+&lt;Office&gt;/user/config/soffice.cfg/</li>
+  <ul>
+    <li>writermenubar.xml </li>
+    <li>writerkeybinding.xml </li>
+    <li>calcmenubar.xml </li>
+    <li>calckeybinding.xml </li>
+    <li>impressmenubar.xml </li>
+    <li>impresskeybinding.xml </li>
+    <li>drawmenubar.xml </li>
+    <li>drawkeybinding.xml </li>
+    <li>META-INF/manifest.xml </li>
+  </ul>
+</ul>
+<p></p>
+<!-- Instructions superceded by file backup
+<p>
+You can use the Tools/Configure dialog to remove any menu, key or event bindings
+that you have set up for Office scripts.
+<ul>
+<li>For Menu assignments:</li>
+  <ul>
+    <li>Select &lt;menu name&gt; [] then click Delete </li>
+  </ul>
+<li>For Keyboard assignments:</li>
+  <ul>
+     <li>Select &lt;key combo&gt; [script://&lt;script name&gt;] then click Delete</li>
+  </ul>
+<li>For Event assignments:</li>
+  <ul>
+     <li>Select OpenOffice.org for application assignments or Document for document assignments</li>
+     <li>Select the script to be removed from Assigned Macro column then click Remove. </li>
+  </ul>
+</ul>
+-->
+<p> If you have installed Office Scripting support into a NetBeans
+installation you can remove it by deleting: </p>
+<ul>
+  <li>&lt;NetBeans Installation&gt;/modules/office.jar </li>
+</ul>
+<a href="#top">Top</a>
+<hr> Last Modified: 
+Fri Jun 20 15:27:54 BST 2003
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/user-guide.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/user-guide.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/release-0.3/user-guide.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,653 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=iso-8859-1">
+  <title></title>
+  <meta name="GENERATOR" content="StarOffice 6.1 Beta 1 (Linux)">
+  <meta name="CREATED" content="20030313;16153200">
+  <meta name="CHANGED" content="20030313;16505100">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<h1><a name="top"></a>User Guide for the Office Scripting Framework</h1>
+<h2>Contents</h2>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;"><a href="#prerequisites">Pre-requisites</a>
+    </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;"><a href="#bindscripts">Binding
+Office Scripts</a> </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;"><a href="#usingsf">Running the
+example Office Scripts</a></p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;"><a
+ href="#Leveraging_StarBasic_Security">Leveraging StarBasic Security</a></p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;"><a
+ href="#Different_behaviour_in_the_Scripting">Different behaviour in
+the Scripting Framework</a></p>
+  </li>
+  <li>
+    <p><a href="#Troubleshooting">Troubleshooting</a> </p>
+  </li>
+</ul>
+<h2><a name="prerequisites"></a>Pre-requisites</h2>
+<p>Before you install the Scripting Framework, be aware of the
+following: </p>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;">This is an Early Developer Release
+of the Office Scripting Framework provided for users and developers of
+OpenOffice.org to try out and provide feedback. Future releases of the
+Framework may change. </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">This release of the Scripting
+Framework runs only on <a
+ href="http://www.openoffice.org/dev_docs/source/1.1rc/index.html">
+OpenOffice.org 1.1 rc</a> and above.&nbsp;</p>
+  </li>
+  <li>
+    <p>The Scripting Framework is currently available in English only. </p>
+  </li>
+</ul>
+<h2><a name="bindscripts"></a>Binding Office Scripts</h2>
+<p>The execution of Office scripts can be bound to menu and key items
+and also to application or document events. These bindings can be
+defined via a set of Assign dialogs which can be started from the
+Tools/Scripting Add-on's menu </p>
+<p><b>Assigning scripts to Menu and Key items</b> </p>
+<p>The dialog shown below is the Assign Script to Menu dialog. This
+dialog is similar in design and function to the Assign Script to Key
+dialog and the instructions below should be seen to apply also to the
+Assign Script to Key dialog. </p>
+<p style="text-align: center;"><img src="assign-menu.gif"
+ name="Graphic1"
+ style="border: 0px solid ; width: 396px; height: 496px;" title=""
+ alt=""></p>
+<ul>
+  <li>
+    <p>Location </p>
+    <p>The location combo box will be populated with &#8220;User&#8221;,&#8221;Share&#8221;,
+&#8220;Document&#8221; or "Filesystem" the default value will be &#8220;User&#8221; which will
+display all scripts (with the selected language type) in the &#8220;User&#8221;
+area.</p>
+  </li>
+</ul>
+<ul>
+  <li>
+    <p>Language </p>
+    <p>The language combox is populated with the list of supported
+languages. The default language is set to Java.</p>
+  </li>
+</ul>
+<ul>
+  <li>
+    <p>Script ListBox </p>
+    <p>Only necessary information will be displayed, logicalname will
+always be displayed, if the &#8220;Detailed view&#8221; check box is selected the
+scripts will be displayed as follows &#8220;logicalname [functionname]&#8221;</p>
+  </li>
+  <li>Browse<br>
+    <br>
+A new feature in the 0.3 release is the ability to bind to scripts on
+the filesystem (without an associated parcel-descriptor.xml). Clicking
+[Browse] pops up a filechooser dialog enabling the user to populate the
+Script ListBox. As the Java Script Runtime (not to be confused with the
+JavaScript Script Runtime!!) does not support running scripts from the
+Filesystem, the Browse button is enabled only when the Location combo
+box is set to "Filesystem", and Language combo box is set to something
+other than "Java".<br>
+  </li>
+</ul>
+<ul>
+  <li>
+    <p>New</p>
+    <p>This button will not be selectable unless a script from the
+script ListBox and a menu name is entered in the new menu text box
+(opposite New button), clicking [New] creates a binding between two.</p>
+  </li>
+  <li>
+    <p>Delete</p>
+    <p>This button will not be selectable unless a sub menu with a
+script binding is selected, clicking [Delete] removes the binding. </p>
+  </li>
+  <li>
+    <p>OK</p>
+    <p>Clicking [OK] commits all of the changes the user has made </p>
+  </li>
+  <li>
+    <p>Cancel</p>
+    <p>Disposes the dialog without committing any changes.</p>
+  </li>
+  <li>
+    <p>Help</p>
+    <p>Will display a dialog describing how to use each of the &#8220;Assign
+Script&#8221; dialogs.</p>
+  </li>
+</ul>
+<p><b>Note: </b>Unlike StarBasic it will not be possible to setup a
+key binding that applies for the whole Office suite &#8211; key bindings can
+only be setup for an application or a document of that application type.</p>
+<p><b>Assigning scripts to events</b></p>
+<p style="text-align: center;"><img src="assign-event.gif"
+ name="Graphic2"
+ style="border: 0px solid ; width: 423px; height: 442px;" title=""
+ alt=""></p>
+<ul>
+  <li>
+    <p><a name="filesys"></a>Browse<br>
+    <br>
+A new feature in the 0.3 release is the ability to bind to scripts on
+the filesystem (without an associated parcel-descriptor.xml). Clicking
+[Browse] pops up a filechooser dialog enabling the user to populate the
+Script ListBox. As the Java Script Runtime (not to be confused with the
+JavaScript Script Runtime!!) does not support running scripts from the
+Filesystem, the Browse button is enabled only when the Location combo
+box is set to "Filesystem", and Language combo box is set to something
+other than "Java".</p>
+  </li>
+  <li>
+    <p>Event ListBox</p>
+    <p>The ListBox will be populated with the list all event types, if
+a script has already been assigned to an event the existing binding is
+displayed as follows</p>
+    <p>Event [ script URI ]</p>
+    <p>example: </p>
+    <p>Start Application<span style="text-decoration: none;"> <font
+ size="2">[script://Highlighter.BeanShell?language=BeanShell&amp;function=highlighter.bsh&amp;location=user]</font></span></p>
+  </li>
+  <li>
+    <p>Radio Buttons</p>
+    <p>By default the &#8220;Document&#8221; radio button is selected, if selected
+the event binding is for this document only. If &#8220;All Applications&#8221; is
+selected then the event binding is for all documents of all application
+types ( writer, calc etc. )</p>
+  </li>
+  <li>
+    <p>Assign</p>
+    <p>This button will not be selectable unless a script from the
+script ListBox and event from the event ListBox are highlighted
+(selected), clicking [Assign] creates a binding between two.</p>
+  </li>
+  <li>
+    <p>Delete</p>
+    <p>This button will not be selectable unless an event with a script
+binding from the event ListBox is selected, clicking [Delete] removes
+the binding. </p>
+  </li>
+  <li>
+    <p>OK</p>
+    <p>Clicking [OK] commits all of the changes the user has made </p>
+  </li>
+  <li>
+    <p>Cancel</p>
+    <p>Disposes the dialog without committing any changes.</p>
+  </li>
+  <li>
+    <p>Help</p>
+    <p>Will display a dialog describing how to use each of the &#8220;Assign
+Script&#8221; dialogs. </p>
+  </li>
+</ul>
+<p><b><a name="editdebug"></a>Other Scripting-Add'ons Menu Items</b></p>
+<p>Two other menu items are available under the Tools/Scripting
+Add-on's submenu: </p>
+<ul>
+  <li>
+    <p>Edit/Debug Scripts - This pops up a dialog in which the user can
+experiment with writing and executing JavaScript &amp; BeanShell code.
+As with the Assign dialogs, the [Browse] button allows the user to
+select scripts located on the filesystem. (and is only enabled under
+the
+same conditions as in the Assign dialogs). See <a
+ href="developer-guide.html">Writing Scripts in BeanShell and Java</a>
+for more information on using this window.<br>
+    </p>
+    <div style="text-align: center;"><img src="edit-debug.gif" title=""
+ alt="" style="width: 423px; height: 326px;"><br>
+    </div>
+    <p><br>
+    </p>
+  </li>
+  <li>
+    <p>Refresh All Scripts - This is used to refresh the script lists
+that appear in the Assign dialogs after new scripts have been deployed
+into your OpenOffice.org installation or documents. </p>
+  </li>
+</ul>
+<p><a href="#top">Top</a> </p>
+<h2><a name="usingsf"></a>Running the example Office Scripts</h2>
+<p>There are two examples scripts supplied with the Scripting
+Framework, Highlight and MemoryUsage. Highlight is an application level
+script for Writer that allows the user to search for a word or phrase.
+It will highlight all instances in red and give a count of the number
+of
+instances. </p>
+<p>The second example, MemoryUsage, is a script stored in a Calc
+spreadsheet that checks the current memory usage in the Java Virtual
+Machine and updates cells in the spreadsheet with the usage values. The
+spreadsheet also contains a graph which will update when the cell
+values
+are changed. </p>
+<p>The examples are available for both Java and BeanShell in the
+language directories created under &lt;Office
+Installation&gt;/user/Scripts by the installer. </p>
+<p><b>Running the Highlight example</b></p>
+<p>To run this example you first need to create a menu item from which
+you can execute the script. </p>
+<ul>
+  <li>
+    <p style="margin-bottom: 0in;">Start OpenOffice.org and open an
+existing Writer document or create a new one. </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Select the menu item Tools/Scripting
+Add-on's/Assign Scripts To Menu... </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">In the "Assign Scripts To Menu"
+dialog that pops up do the following: </p>
+    <ul>
+      <li>
+        <p style="margin-bottom: 0in;"><i>Select location and language</i></p>
+        <ul>
+          <li>
+            <p style="margin-bottom: 0in;">Set the location to User and
+the language to Java in the drop down lists.</p>
+          </li>
+        </ul>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><i>Select script</i></p>
+        <ul>
+          <li>
+            <p style="margin-bottom: 0in;">Select the script
+HighlightText.showForm from the list.</p>
+          </li>
+        </ul>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><i>Choose the menu to insert the
+script menu after</i></p>
+        <ul>
+          <li>
+            <p style="margin-bottom: 0in;">Select the top level menu
+and submenu under which you want to place your new menu item. </p>
+          </li>
+        </ul>
+      </li>
+      <li>
+        <p style="margin-bottom: 0in;"><i>Assign script to new menu</i></p>
+        <ul>
+          <li>
+            <p style="margin-bottom: 0in;">In the New Menu text field
+enter the label you want for your menu item (eg. Highlight) </p>
+          </li>
+          <li>
+            <p style="margin-bottom: 0in;">Click New Script Menu to
+create the new script menu item. </p>
+          </li>
+        </ul>
+      </li>
+    </ul>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Finally click on the OK button to
+save your new script menu item. </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0in;">Your new menu item will now be
+available and clicking on it will invoke the script. </p>
+  </li>
+  <li>
+    <p>You should see a Highlight Text dialog appear which you can use
+to highlight various text strings you are looking for in the document. </p>
+  </li>
+</ul>
+<p><b>Running the MemoryUsage example</b></p>
+<p>The Java version of the MemoryUsage example is already deployed
+inside an Office document, ExampleSpreadSheet.sxc. To run the Java
+example, just open: </p>
+<p>&lt;Office
+Installation&gt;/user/Scripts/java/ExampleSpreadSheet.sxc. </p>
+<p>You can then execute the MemoryUsage script by pressing <b>CTRL+Shift+M</b>
+with the ExampleSpreadSheet.sxc window focused. You should see the
+memory usage values being updated, and the graph should change to
+reflect the new values.<br>
+</p>
+<p><span style="font-weight: bold;">Running the ExportSheetsToHTML
+example</span><br>
+</p>
+<p>To run this example you first need to create or open an existing
+spreadsheet document. If you have created a new document save it (eg.
+c:\temp\mycalcdoc.sxc)<br>
+</p>
+<ul>
+  <li>Select the menu item Tools-&gt;Scripting Add-ons-&gt;Assign
+Script to Key</li>
+  <li>Select the location "User", and language "JavaScript.</li>
+  <li>Select the example script ExportSheetsToHTML.JavaScript</li>
+  <li>Select the key group CONTROL + letters, and then select the
+Shortcut Key CONTROL + H</li>
+  <li>Press the Assign button, and then the OK button.</li>
+</ul>
+This will have created a key binding to the ExportSheetsToHTML script.
+Pressing CONTROL + H will now save each sheet in HTML format in the
+same
+directory as the original document (eg. c:\temp\mycalcdoc_sheet1.html,
+c:\temp\mycalcdoc_sheet2.html, ...)<br>
+<p><a href="#top">Top</a> </p>
+<h2><a name="Leveraging_StarBasic_Security"></a>Leveraging StarBasic
+Security</h2>
+<p style="margin-bottom: 0in;">As part of the Early Developer Release
+v0.2 of the Scripting Framework, we have attempted to mimic the
+Security
+settings for StarBasic.&nbsp; The settings allow the user to control
+the
+execution of macros present in OpenOffice.org documents. Found in&nbsp;
+the&nbsp; Tools-&gt;Options dialog under&nbsp;
+OpenOffice.org-&gt;Security, these&nbsp; settings allow the user&nbsp;
+to specify the conditions under which it is permissable to execute
+document based StarBasic macros. The settings in this dialog now apply
+to both StarBasic macros and Scripting Framework scripts.<br>
+A full description of how these settings work can be found by clicking
+the "Help" button in the dialog, and then clicking "OpenOffice.org",
+and
+"Security" in the left-hand pane of the Help dialog. The possible
+scenarios associated with the security settings are summarised in the
+table below.</p>
+<table border="2" cellpadding="2" cellspacing="2">
+  <tbody>
+    <tr>
+      <th>
+      <p>"Run Macro"</p>
+      </th>
+      <th>
+      <p>"Confirm in the case of other document sources"</p>
+      </th>
+      <th>
+      <p>"Show Warning before Running"</p>
+      </th>
+      <th>
+      <p>Document path in "Path List"</p>
+      </th>
+      <th>
+      <p>Behaviour</p>
+      </th>
+    </tr>
+    <tr>
+      <td>
+      <p>Never</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>Macros never run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Macros never run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Macros run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Macros never run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Warning displayed on document load. If "Run" button clicked
+macros will run, otherwise they will not.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Warning with checkbox to add path to path list is displayed on
+document load. If "Run" button clicked macros will run, otherwise
+they will not. Regardless of which button is clicked, if checkbox is
+ticked document path is added to "Path List".</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Macros run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>Warning with checkbox to add path to path list is displayed on
+document load. If "Run" button clicked macros will run, otherwise
+they will not. Regardless of which button is clicked, if checkbox is
+ticked document path is added to "Path List".</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>According to path list</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>Warning displayed on document load. If "Run" button clicked
+macros will run, otherwise they will not.</p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>Always</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>No</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>Macros run. No warning displayed. </p>
+      </td>
+    </tr>
+    <tr>
+      <td>
+      <p>Always</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>Yes</p>
+      </td>
+      <td>
+      <p>N/A</p>
+      </td>
+      <td>
+      <p>Warning displayed on document load. If "Run" button clicked
+macros will run, otherwise they will not.</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<p><br>
+<br>
+<a href="#top">Top</a></p>
+<h2><a name="Different_behaviour_in_the_Scripting"></a>Different
+behaviour in the Scripting Framework</h2>
+<p>The Script Security has one significant difference in behaviour to
+the StarBasic security. In the Scripting Framework the security warning
+dialogs are displayed only upon the first script invocation on a
+document containing scripts, unlike StarBasic where the dialogs are
+displayed on loading a document containing macros. <br>
+If the settings are "Always", and "Show Warning Before Running", when
+loading a document containing macros the StarBasic dialog display is
+incorrect (the dialog displayed is more appropriate to the "According
+To
+Path List" setting). This has been logged as <a
+ href="http://www.openoffice.org/issues/show_bug.cgi?id=11822">Issue
+11822</a>, the fix for which is not in the OpenOffice.org 1.1 beta
+release. Under the Scripting framework the correct dialog is displayed.<br>
+<br>
+<a href="#top">Top</a></p>
+<h2><a name="Troubleshooting"></a>Troubleshooting</h2>
+<p style="margin-bottom: 0in;">See the <a href="release-notes.html">Release
+Notes</a> page. </p>
+<hr> Last Modified: 
+Tue Jul 15 16:16:07 BST 2003
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

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

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

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/beanshell.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/beanshell.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/commandline-devguide.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/commandline-devguide.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/commandline-devguide.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,229 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <title>Developing Scripts on the Command Line</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<a name="top"></a>
+<h1>Developing Scripts on the Command Line</h1>
+For users who do not wish to develop their OpenOffice.org scripts using an IDE
+there is a simple command line interface built into the OpenOffice.org Scripting
+module which can be used for the generation and deployment of OpenOffice.org
+Scripts.
+
+<h2>Contents</h2>
+<ul>
+  <li>
+    <p><a href="#prereqs">Prerequisites</a> </p>
+  </li>
+  <li>
+    <p><a href="#usage">The CommandLineTools class</a> </p>
+  </li>
+  <li>
+    <p><a href="#examples">Examples</a> </p>
+  </li>
+</ul>
+
+<h2><a name="prereqs">Prerequisites</a></h2>
+<ul>
+  <li>The Scripting module office.jar file should be included in the
+classpath. You can download this file from <a href="./office.jar">here</a>
+  </li>
+  <li>The main Scripting Framework jar file ScriptFramework.jar also needs
+to be included in the classpath. You can find it in the program/classes
+directory of your OpenOffice.org installation.
+  </li>
+  <li>The CommandLineTools class will only work if an XML parser (such
+as <a href="http://xml.apache.org/xerces2-j/index.html">Apache Xerces</a>)
+is available in the classpath.</li>
+</ul>
+<a name="usage"> </a>
+<h2><a name="usage">The CommandLineTools class</a></h2>
+<a name="usage">The CommandLineTools class takes the following options (<b>Note:</b>
+Options in angle brackets "&lt;&gt;" are required, options in square
+brackets "[]" are optional): </a>
+<blockquote> <a name="usage"><b>[-o Path to OpenOffice.org Installation] -g [Path to Parcel directory] [options]</b> </a>
+  <p> <a name="usage">Generates a Script Parcel for the given the
+parcel directory. The optional -o flag is used to specify that path
+to your OpenOffice.org installation. If it is not provided the CommandLineTools
+class will attempt to discover your OpenOffice.org installation and will print
+an error if it fails. The parcel name will be the name of the parcel
+directory plus the .sxp extension. </a></p>
+  <ul>
+    <li><a name="usage">If a parcel directory is not specified the
+current directory is used. If the parcel directory does not contain a
+directory named Contents an error message is printed. Otherwise a Script
+Parcel (.sxp) file is generated in the parcel directory containing all
+of the files under the Contents directory. The options that may be used
+with the -g option allow the user to specify how the
+parcel-descriptor.xml file for the Script Parcel is generated (see the
+Scripting Framework </a><a href="developer-guide.html">developer guide</a>
+for more information on the parcel-descriptor.xml file). The following
+options are available:
+      <p> <b>[-l language[=supported extension list]]</b> </p>
+      <p> Specifies which language attribute to use for the parcel
+element in the parcel-descriptor.xml file. The supported extension list
+is ignored if the language is Java. Otherwise all files that have one of
+the supported extensions (the list should be separated by the platform
+specific path separator, ":" on Unix, ";" on Windows) will be added as
+script entries to the parcel-descriptor.xml file. </p>
+      <p> Alternatively the user can specify a list of names at the
+command line which will be added as scripts and no search for script
+names will be performed. The following table shows the behaviour of
+CommandLineTools when the -l flag is used: </p>
+      <p>
+      <table border="1">
+        <tbody>
+          <tr>
+            <th>-l flag used? </th>
+            <th>parcel-descriptor.xml exists? </th>
+            <th>result </th>
+          </tr>
+          <tr>
+            <td align="center">no </td>
+            <td align="center">no </td>
+            <td>error message printed </td>
+          </tr>
+          <tr>
+            <td align="center">yes </td>
+            <td align="center">no </td>
+            <td>parcel-descriptor.xml generated<br>
+parcel.sxp generated </td>
+          </tr>
+          <tr>
+            <td align="center">no </td>
+            <td align="center">yes </td>
+            <td>parcel-descriptor.xml not generated<br>
+parcel.sxp generated </td>
+          </tr>
+          <tr>
+            <td align="center">yes </td>
+            <td align="center">yes </td>
+            <td>if <br>
+language is different from parcel-descriptor.xml language, error <br>
+else <br>
+parcel-descriptor.xml regenerated <br>
+parcel.sxp generated </td>
+          </tr>
+        </tbody>
+      </table>
+      </p>
+      <p> <b>[-p name=value]</b> </p>
+      <p> Specifies a name value pair to be added as a language
+dependent property in the parcel-descriptor.xml file </p>
+      <p> <b>[-v]</b> </p>
+      <p> Specifies that verbose output should be displayed. </p>
+    </li>
+  </ul>
+  <p> <b>[-o Path to OpenOffice.org Installation] -d &lt;Path to Script Parcel&gt; &lt;Target
+Directory|Document&gt;</b> </p>
+  <p> Deploys the given Script Parcel to a directory or an
+OpenOffice.org document. The optional -o flag is used to specify that path
+to your OpenOffice.org installation. If it is not provided the CommandLineTools
+class will attempt to discover your OpenOffice.org installation and will print
+an error if it fails. A directory will be created with the name of
+the Parcel and the contents of the Parcel will be put into that
+directory. </p>
+  <ul>
+    <li>If deploying to an OpenOffice.org installation the target
+directory should be the &lt;OpenOffice.org Installation&gt;/user/Scripts or
+&lt;OpenOffice.org Installation&gt;/share/Scripts directory. If the either the
+Script Parcel or the target do not exist an error message is printed.
+Otherwise the Script Parcel is deployed to the target. </li>
+  </ul>
+</blockquote>
+<p><a href="#top">Top</a> <a name="examples"> </a></p>
+<h2><a name="examples">Examples</a></h2>
+<ul>
+  <li>
+    <p><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g myparceldir -l Java </font> </a></p>
+    <p><a name="examples">Generates a myparceldir.sxp file in
+myparceldir automatically exporting all public Java methods which take
+XScriptContext as their first parameter as OpenOffice.org scripts. </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g -l BeanShell=.bsh </font> </a>
+    <p><a name="examples">Generates a script parcel file in the current
+directory automatically exporting all files that end with the .bsh
+extension as BeanShell scripts </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g myparceldir -l BeanShell MyScript.bsh </font> </a>
+    <p><a name="examples">Generates a myparceldir.sxp file in
+myparceldir and exports MyScript.bsh as an OpenOffice.org script. </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g myparceldir -l Java -p classpath=dep1.jar:dep2.jar </font> </a>
+    <p><a name="examples">Generates a myparceldir.sxp file in
+myparceldir, automatically searching for valid OpenOffice.org scripts, and
+adding the classpath property to each OpenOffice.org script. </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -g myparceldir -l Java -p classpath=dep1.jar:dep2.jar
+-p secondprop=secondvalue </font> </a>
+    <p><a name="examples">Generates a myparceldir.sxp file in
+myparceldir, automatically searching for valid OpenOffice.org scripts, and
+adding the classpath and the secondprop properties to each OpenOffice.org
+script. </a></p>
+  </li>
+  <li><a name="examples"><font face="Courier, monospace" size="2"> java
+CommandLineTools -d myparceldir.sxp /export/home/MyOffice/user/Scripts </font> </a>
+    <p><a name="examples">Deploys the myparceldir.sxp Script Parcel to
+the specified office directory.</a></p>
+  </li>
+  <li><a name="examples"> <font face="Courier, monospace" size="2">java
+CommandLineTools -g myparceldir -l JavaScript MyScript.js</font></a><br>
+    <a name="examples">Generates a myparceldir.sxp file in myparceldir
+and exports MyScript.js as an OpenOffice.org script.</a></li>
+</ul>
+<p><a href="#top">Top</a> </p>
+<hr> Last Modified: Nov 19 2003
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/developer-guide.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/developer-guide.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/developer-guide.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,346 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <title>Writing Scripts in BeanShell and Java</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<h1>Writing Scripts in BeanShell, JavaScript and Java</h1>
+<a name="top"></a>
+<h2>Contents</h2>
+<ul>
+  <li>
+    <p><a href="#bsh">Hello World in BeanShell</a> </p>
+  </li>
+  <li>
+    <p><a href="#bshinvoke">Trying out your BeanShell script</a> </p>
+  </li>
+  <li>
+    <p><a href="#js">Hello World in JavaScript</a> </p>
+  </li>
+  <li>
+    <p><a href="#jsinvoke">Trying out a JavaScript script</a> </p>
+  </li>
+  <li>
+    <p><a href="#java">Hello World in Java</a> </p>
+  </li>
+  <li>
+    <p><a href="#context">Writing OpenOffice.org Scripts and the XScriptContext
+type</a> </p>
+  </li>
+  <li>
+    <p><a href="#tips">Tips on writing OpenOffice.org scripts</a> </p>
+  </li>
+  <li>
+    <p><a href="#dtd">Parcel Descriptor DTD and sample XML</a> </p>
+  </li>
+</ul>
+<a name="bsh"></a>
+<h2>Hello World in BeanShell</h2>
+Here's a BeanShell script that inserts Hello World at the start of an
+OpenOffice.org Writer document:
+<p> </p>
+<pre>
+    import com.sun.star.frame.XModel;
+    import com.sun.star.text.*;
+    import com.sun.star.uno.UnoRuntime;
+    import drafts.com.sun.star.script.provider.XScriptContext;
+
+    model = context.getDocument(); 
+    textdoc = (XTextDocument)
+        UnoRuntime.queryInterface(XTextDocument.class, model);
+
+    oText = textdoc.getText(); 
+    oCursor = oText.createTextCursor(); 
+    oText.insertString(oCursor, "Hello World", false)
+</pre>
+<a href="#top">Top</a> <a name="bshinvoke"></a>
+<h2>Trying out your BeanShell script</h2>
+Trying out your Hello World BeanShell script is easy:
+<ul>
+  <li>Start OpenOffice.org and open a new Writer document. </li>
+  <li>Select the Tools/Configure... menu item. </li>
+  <li>Select the menu tab. In the Category section select
+      OpenOffice.org Scripts/share/Java/selector
+  <li>In the Function list select ScriptSelector.showOrganizer
+  <li>Now click the New button to create a menu item for this script. You can
+      rename the menu item by clicking on it in the Menu entries list, and
+      move it around the menu hierarchy using the arrow buttons.
+  <li>Click OK to apply your change
+  <li>Select your new menu item
+  <li>A Script dialog appears, browse to a BeanShell script
+      eg. Root/share/BeanShell/Highlight/highlighter.bsh and click Edit.
+  <li>A BeanShell Debugger window will appear. Click Clear to clear the window
+      and copy in the text of your Hello World example
+      <br><div style="text-align: center;"><img src="beanshell.gif" title=""
+           alt="" style="width: 477px; height: 319px;"><br></div>
+  </li>
+  <li>Now click on the Run button.
+  <li>You should see Hello World appear at the start of the Writer document.
+  <li>Click Close so that the highlighter.bsh script is not overwritten
+</ul>
+
+<p>
+If you are new to the OpenOffice.org API this is a great way to experiment
+with it. </p>
+<p> When you are happy with your BeanShell script, you can create a
+Script Parcel which can be deployed to OpenOffice.org installations or
+documents for use by others. This can be done <a
+ href="netbeans-devguide.html">using NetBeans</a> or <a
+ href="commandline-devguide.html">from the command line</a>. </p>
+<p>
+<a href="#top">Top</a>
+
+<a name="js">
+<h2>Hello World in JavaScript</h2>
+</a> Here's a JavaScript script that inserts Hello World at the start of
+an OpenOffice.org Writer document: </p>
+<pre>
+    importClass(Packages.com.sun.star.uno.UnoRuntime);
+    importClass(Packages.com.sun.star.text.XTextDocument);
+
+    var oModel = XSCRIPTCONTEXT.getDocument(); 
+    var oTextdoc = UnoRuntime.queryInterface(XTextDocument, oModel);
+    var oText = oTextdoc.getText(); 
+    var oCursor = oText.createTextCursor(); 
+
+    oText.insertString(oCursor, "Hello World", false);
+</pre>
+
+<p> The XSCRIPTCONTEXT variable above is a global instance of the
+XScriptContext type which is available to all JavaScript scripts
+executed by the Scripting Framework. See <a href="#context">Writing
+OpenOffice.org Scripts and the XScriptContext type</a> for the methods available
+for the XScriptContext type. </p>
+<p> <a href="#top">Top</a> </p>
+<h2> <a name="jsinvoke"> Trying out a JavaScript script in
+OpenOffice.org </a></h2>
+Once again you can use the Edit/Debug Scripts dialog to open a
+JavaScript script in an editor. The Rhino JavaScript Editor from the <a
+ href="http://mozilla.org/rhino">Mozilla Rhino project</a> can be used
+to debug and test your JavaScript scripts.
+<ul>
+  <li>Create a menu item for the Script dialog as described in the
+      BeanShell instructions above
+  <li>Open the Script dialog, navigate to
+      Root/share/JavaScript/ExportSheetsToHTML/exportsheetstohtml.hs and
+      click edit.</li>
+  <li>A Rhino Debugger window will appear. Delete the text in the window and
+      paste in the Hello World code
+      <br><div style="text-align: center;"><img src="rhino.gif" title=""
+           alt="" style="width: 640px; height: 646px;"><br> </div>
+  </li>
+  <li>To run the script select File/Run and then click on the Go button.
+</ul>
+<p> The Rhino Debugger also includes debugging functionality, so you can
+set breakpoints in your JavaScript script and step through the code as
+it is executed. </p>
+<p>
+<a href="#top">Top</a>
+
+<a name="java"></a> </p>
+<h2>Hello World in Java</h2>
+Here's the Hello World script in Java:
+<p> <font face="Courier, monospace" size="2">
+<pre>    import com.sun.star.frame.XModel;
+    import com.sun.star.text.*;
+    import com.sun.star.uno.UnoRuntime;
+    import drafts.com.sun.star.script.provider.XScriptContext;
+
+    public class MyClass {
+
+        // The script method must be public
+        // It can either be static or non-static
+
+        public void showForm(XScriptContext xSc) {
+
+            // getting the text document object
+            XModel xmodel = xSc.getDocument();
+
+            XTextDocument xtextdoc = (XTextDocument)
+                UnoRuntime.queryInterface(XTextDocument.class, xmodel);
+            XText xtext = xtextdoc.getText();
+            XTextCursor xtextcursor = xtext.createTextCursor();
+
+            xtext.insertString(xtextcursor, "Hello World", false);
+        }
+    }
+</pre>
+</font> </p>
+<p> OpenOffice.org scripts in Java need to be compiled in order to execute them.
+See the <a href="netbeans-devguide.html">Developing Scripts in NetBeans</a>
+and <a href="commandline-devguide.html">Developing Scripts on the
+command line</a> guides for instructions on how to compile and deploy
+OpenOffice.org scripts in Java. </p>
+<p> <a href="#top">Top</a> <a name="context"></a> </p>
+<h2>Writing OpenOffice.org scripts and the XScriptContext type</h2>
+The XScriptContext type is used to obtain the the document context,
+desktop and component factory from an OpenOffice.org script. Any public Java
+method which accepts XScriptContext as it's first parameter can be
+executed as an OpenOffice.org script.  For BeanShell scripts, an instance of
+XScriptContext is available in a global variable called "context" which
+can be used by the script.
+<p> The following accessor methods are available on the XScriptContext
+type: </p>
+<ul>
+  <li>Current document - access the document context against which the
+script was invoked
+    <p> <font face="Courier, monospace" size="2"> &lt;XScriptContext
+Instance&gt;.getDocument()</font> <br>
+returns <font face="Courier, monospace" size="2">::com::sun::star::frame::XModel</font> </p>
+  </li>
+  <li>OpenOffice.org Desktop - access the desktop of the running OpenOffice.org
+    <p> <font face="Courier, monospace" size="2"> &lt;XScriptContext
+Instance&gt;.getDesktop()</font> <br>
+returns <font face="Courier, monospace" size="2">
+::com::sun::star::frame::XDesktop</font> </p>
+  </li>
+  <li>Component Factory - access a ComponentContext factory to create
+other UNO components as required
+    <p> <font face="Courier, monospace" size="2"> &lt;XScriptContext
+Instance&gt;.getComponentContext()</font> <br>
+returns <font face="Courier, monospace" size="2">
+::com::sun::star::uno::XComponentContext</font> </p>
+  </li>
+</ul>
+The Java or BeanShell script must import the XScriptContext interface,
+using the following import directive: <font face="Courier, monospace"
+ size="2">
+<pre>    import drafts.com.sun.star.script.provider.XScriptContext;<br></pre>
+</font>
+<p> <a href="#top">Top</a> <a name="tips"></a> </p>
+<h2>Tips on writing OpenOffice.org scripts</h2>
+<ul>
+  <li>
+    <p><b>Performance:</b> Currently scripts are being loaded by the
+Scripting Framework each time they are run. As such it is important to
+keep the size of your scripts and any dependent jar files they are using
+reasonably small. In future releases this script loading will be
+optimised by changing the point at which the scripts are loaded by
+OpenOffice.org and using various caching schemes once they are loaded.
+However, the initial load will always be effected by the script and
+it's dependent jar/class file sizes. </p>
+  </li>
+  <li>
+    <p><b>Threading:</b> Scripts are run synchronously by the Scripting
+Framework. If you wish to perform any background task or provide some
+user interaction via a dialog for instance, then it is your
+responsibility to spawn a thread in the running script which can manage
+this process or interaction and let the script return promptly. Within
+this running thread you should follow the normal UNO component
+threading guidelines to ensure that they do not deadlock OpenOffice.org
+through inappropriate use of the UNO API. </p>
+  </li>
+</ul>
+<a href="#top">Top</a> <a name="dtd"></a>
+<h2>Parcel Descriptor DTD and sample XML</h2>
+Each Script Parcel must contain a parcel-descriptor.xml file which provides
+all the necessary metadata for the script. The DTD for the
+parcel-descriptor.xml follows:
+
+<pre>
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;!-- DTD for Parcel Meta data for use in the OpenOffice.org Scripting Framework Project --&gt;
+
+&lt;!ELEMENT description (#PCDATA)&gt;
+&lt;!ELEMENT displayname EMPTY&gt;
+&lt;!ELEMENT functionname EMPTY&gt;
+&lt;!ELEMENT prop EMPTY&gt;
+&lt;!ELEMENT languagedepprops (prop+)&gt;
+&lt;!ELEMENT script (description, displayname, functionname, languagedepprops*)&gt;
+&lt;!ELEMENT parcel (script+)&gt;
+&lt;!ATTLIST displayname
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST locale
+	lang CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST functionname
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST prop
+	name CDATA #REQUIRED
+	value CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST script
+	language CDATA #REQUIRED
+&gt;
+&lt;!ATTLIST parcel
+	language CDATA #REQUIRED
+&gt;
+</pre>
+
+<p>
+
+The following is an example of a parcel-descriptor.xml file that
+defines a script, implemented in Java. The languagedepprops element is
+used to extend the JVM's classpath.
+
+<pre>
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;!--Sample Meta Data for use with the Scripting Framework Project in OpenOffice.org --&gt;
+&lt;!DOCTYPE parcel SYSTEM "parcel.dtd"&gt;
+
+&lt;parcel language="Java"&gt;
+	&lt;script language="Java"&gt;
+		&lt;displayname value="Memory.usage"/&gt;
+		&lt;description&gt;
+			Displays the memory current memory usage
+		&lt;/description&gt;
+		&lt;functionname value="memoryUtils.memoryUsage"/&gt;
+		&lt;languagedepprops&gt;
+			&lt;prop name="classpath" value="/opt/foo.jar:/usr/java/src.jar"/&gt;
+		&lt;/languagedepprops&gt;
+	&lt;/script&gt;
+&lt;/parcel&gt;
+</pre>
+
+<a href="#top">Top</a>
+<hr> Last Modified: Nov 28 2003
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

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

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig1.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig1.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig2.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig2.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig3.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig3.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig4.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig4.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig5.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig5.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig6.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/fig6.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/index.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/index.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/index.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,237 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<h1>OpenOffice.org Scripting Framework</h1>
+
+<p><b>Project Owners:</b> <a href="mailto:john.rice@sun.com">John Rice</a>
+, <a href="mailto:noel.power@sun.com">Noel Power</a>
+
+<p>
+<table style="width: 100%; background-color: rgb(240, 240, 240);"
+ border="0" cellpadding="2" cellspacing="0">
+  <col width="270"> <col width="6"> <col width="220"> <col
+ width="171"> <col width="117"> <col width="36"> <tbody>
+    <tr>
+      <td colspan="6"
+ style="background-color: rgb(0, 49, 90); width: 100%;">
+      <p align="center"><font color="#ffffff"><b>Documentation for the latest release</b> </font> </p>
+      </td>
+    </tr>
+    <tr>
+      <th
+ style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
+      <p align="left"><font color="#00315a"><b>Name</b> </font> </p>
+      </th>
+      <th colspan="5"
+ style="background-color: rgb(153, 204, 255); width: 70%; text-align: left;">
+      <p align="left"><font color="#00315a"><b>Description</b> </font>
+      </p>
+      </th>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p>New Features</p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+        The Scripting Framework is now installed with OpenOffice.org.
+        Basic macros can now be executed as previously or via the
+        Scripting Framework as well as the other languages supported.
+        Scripts are listed and can be assigned in the:
+        <ul>
+          <li>Tools/Configure dialog
+          <li>Basic dialog controls properties editor
+          <li>Form controls properties editor in documents
+          <li>Hyperlinks, Graphics and Objects property dialogs 
+        </ul>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p>Install</p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Just install the OpenOffice.org snapshot developer build 680_m15 from <a href="http://www.openoffice.org/dev_docs/source/680/">here</a></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td rowspan="2" style="width: 30%;">
+      <p>Script User Guides</p>
+      </td>
+      <td colspan="4" style="width: 70%;">
+      <p><a href="./user-guide.html">General User Guide</a></p>
+      </td>
+    </tr>
+    <tr>
+      <td colspan="4" width="395" valign="top">
+      <p><a href="../utilities-download.html">Utility Scripts
+contributed
+by the OpenOffice.org community</a></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td rowspan="3" width="270">
+      <p>Script Developer Guides</p>
+      </td>
+      <td width="220" colspan="4">
+      <p><a href="./developer-guide.html">Writing Scripts in BeanShell, JavaScript and Java</a> </p>
+      </td>
+    </tr>
+    <tr>
+      <td width="220" colspan="4" valign="top">
+      <p><a href="./netbeans-devguide.html">Developing Scripts in NetBeans</a></p>
+      </td>
+    </tr>
+    <tr>
+      <td width="220" colspan="4" valign="top">
+      <p><a href="./commandline-devguide.html">Developing Scripts on the command line</a></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./SFArch.html">Architecture Overview</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Description of Scripting Framework architecture</p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><a href="./faq.html">FAQ</a></td>
+      <td style="vertical-align: top;" colspan="5">Frequently Asked
+Questions for the OpenOffice.org Scripting Framework</td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="./whats-next.html">What's Next</a></p>
+      </td>
+      <td colspan="5" style="width: 70%;">
+      <p>Planned features for the OpenOffice.org Scripting Framework</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<p>
+<table style="width: 100%; background-color: rgb(240, 240, 240);"
+ border="0" cellpadding="2" cellspacing="0">
+  <col width="270"> <col width="6"> <col width="220"> <col
+ width="171"> <col width="117"> <col width="36"> <tbody>
+    <tr>
+      <td colspan="5"
+ style="width: 100%; background-color: rgb(0, 49, 90);">
+      <p align="center"><font color="#ffffff"><b> Previous Releases</b>
+      </font> </p>
+      </td>
+    </tr>
+    <tr>
+      <th style="background-color: rgb(153, 204, 255); width: 70%;">
+      <p align="left"><font color="#00315a"><b>Version</b> </font> </p>
+      </th>
+      <th colspan="5"
+ style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
+      <p align="left"><font color="#00315a"><b>Released</b> </font> </p>
+      </th>
+    </tr>
+    <tr valign="top">
+      <td style="width: 70%;">
+      <p><a href="../release-0.3/index.html">Early Developer Release Version 0.3</a></p>
+      </td>
+      <td colspan="5" style="width: 30%;">
+      <p>June 2003</p>
+      </td>
+    <tr valign="top">
+      <td style="width: 70%;">
+      <p><a href="../release-0.2/index.html">Early Developer Release
+Version 0.2</a></p>
+      </td>
+      <td colspan="5" style="width: 30%;">
+      <p>April 2003</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 70%;">
+      <p><a href="../release-0.1/index.html">Early Developer Release
+Version 0.1</a></p>
+      </td>
+      <td colspan="5" style="width: 30%;">
+      <p>November 2002</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+</p>
+<hr>
+<table cellpadding="4" cellspacing="0" style="width: 100%;">
+  <tbody>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p><a href="mailto:dev@framework.openoffice.org">Mailing List</a></p>
+      </td>
+      <td style="width: 70%;">
+      <p>Installation, User or Developer queries on the OpenOffice.org
+Scripting Framework</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td style="width: 30%;">
+      <p>Issues</p>
+      </td>
+      <td style="width: 70%;">
+      <p>Issues found in the OpenOffice.org Scripting Framework should be
+logged in Issuezilla<br>
+      <b>component:</b> framework<br>
+      <b>subcomponent:</b> scripting</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<p> Last Modified: Nov 19 2003
+</p>
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/netbeans-devguide.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/netbeans-devguide.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/netbeans-devguide.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,286 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Developing Scripts in NetBeans</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<a name="top"></a>     
+
+<h1>Developing Scripts in NetBeans</h1>
+         
+This document describes how to set up NetBeans for OpenOffice.org Scripting
+and how to write a simple script using NetBeans. You can download
+the NetBeans IDE from the <a href="http://www.netbeans.org/ide/download.html">
+NetBeans download page</a>.
+
+<h2>Contents:</h2>
+
+<ul>
+<li><p><a href="#prerequisites">Pre-requisites</a>
+<li><p><a href="#recipe-create">Creating a Parcel Recipe</a>
+<li><p><a href="#recipe-actions">Actions available for Parcel Recipes</a>
+<li><p><a href="#parcel-actions">Actions available for Script Parcels</a>
+<li><p><a href="#document-actions">Actions available for OpenOffice.org Documents</a>
+<li><p><a href="#debugging">Debugging Java OpenOffice.org scripts in NetBeans</a>
+<li><p><a href="#troubleshooting">Troubleshooting</a>
+</ul>
+
+<a name="prerequisites"></a>
+<h2>Pre-requisites</h2>
+
+<ul>
+<!-- <li>You need to install the OpenOffice.org API support module for NetBeans which
+can be obtained from
+<a href="http://api.openoffice.org/common/man/IDEintegration/OfficeNetBeansIntegration.html">here</a>.
+This module must be installed in NetBeans if you wish to use the
+OpenOffice.org API in your scripts.
+-->
+
+<li>Install the <a href="./office.jar">OpenOffice.org Scripting module</a>
+To install this module, shutdown NetBeans and copy the office.jar file to
+your &lt;NetBeans installation&gt;/modules directory.
+
+<li>Create a directory somewhere on your machine in which you will develop
+your scripts.
+
+<li><b>Note:</b> The OpenOffice.org Scripting module has been tested with NetBeans 3.4
+</ul>
+
+Now start NetBeans and mount the directory you created using the
+File/Mount Filesystem menu option. You also need to mount the following
+of the jar files in the &lt;OpenOffice.org installation&gt;/program/classes directory
+in order to access the OpenOffice.org API from your scripts:
+<p>
+unoil.jar, ridl.jar, sandbox.jar, jurt.jar, juh.jar
+
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="recipe-create"></a>
+<h2>Creating a Parcel Recipe</h2>
+
+OpenOffice.org scripts are delivered in Script Parcels. Like OpenOffice.org documents they
+are zip files. Script Parcels have the .sxp extension. Script Parcels are
+generated from Parcel Recipes where all of the files that are necessary
+to create the parcel are put together. To create a new Parcel Recipe:
+
+<ul>
+<li>Right click on your mounted filesystem
+<li>Select New/Office Scripting/Parcel Recipe
+<li>In the New Wizard window that appears enter a name for your Parcel Recipe
+<li>Select a language for your Parcel Recipe from the Initial Script
+Language dropdown list.
+<li>Click the Finish button to create your Parcel Recipe
+</ul>
+                         
+This will create a new directory with the name you chose. In this directory
+you will find a Contents directory where all of your files will
+be placed. An empty stub file will have been placed in the
+Contents directory and can be used as a starting point for your script.
+
+<p>
+<b>Note:</b> To add further empty stub scripts to your Parcel Recipe, right
+click on the Contents directory and use the New/Office Scripting/Empty Script
+menu item.
+
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="recipe-actions"></a>
+<h2>Actions available for Parcel Recipe</h2>
+
+If the user right clicks on the parcel directory they should be
+able to use the following actions:
+
+<ul>
+<li><b>Compile:</b> Compiles all of the .java files in the Parcel Recipe
+
+<li><b>Build:</b> Compiles all of the .java files in the Parcel Recipe.
+It then searches for valid OpenOffice.org scripts in the language you selected
+in the Contents directory files and pops up a dialog
+which allows you to select which Java methods or BeanShell scripts
+you wish to export as OpenOffice.org scripts.
+Once you have finish making your selections, it creates a
+&lt;Parcel Recipe Name&gt;.sxp Script Parcel file in the Parcel
+Recipe directory. You can configure what files are put into the
+Script Parcel using the File Filter property. If you script includes any
+jar files that need to be in the classpath when it is executed you should
+add them to the Classpath property of your Parcel Recipe.
+
+<li><b>Configure:</b> This pops up the Configure dialog, which allows you
+to select what OpenOffice.org scripts to export. Any changes you make in
+this dialog will <b>only</b> appear in your Script Parcel after you run
+Build again.
+</ul>
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="parcel-actions"></a>
+<h2>Actions available for Script Parcels</h2>
+
+Script Parcels supports only one action:
+
+<ul>
+<li><b>Deploy:</b> This will deploy the Script Parcel to an OpenOffice.org Document
+or to an OpenOffice.org installation. If the Script Parcel already exists
+in the target, you will be asked whether you want to overwrite.
+</ul>
+
+<p>
+<b>Note:</b> If you deploy a Script Parcel to an OpenOffice.org
+installation you need to use the Tools/Scripting Add-on's/Refresh All Scripts
+menu item for the new script to appear in the Assign Script dialog.
+
+<p>
+<b>Note:</b> You can also deploy to OpenOffice.org documents within NetBeans
+using drag and drop or cut and paste.
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="document-actions"></a>
+<h2>Actions available for OpenOffice.org Documents</h2>
+
+OpenOffice.org Documents are also recognised by NetBeans. Any parcels contained
+in the document will be displayed as nodes of the OpenOffice.org document. Deleting
+one of these nodes will remove the Script Parcel from the document. You
+should ensure that the document is not open in OpenOffice.org before deleting
+any parcels it may contain.
+
+OpenOffice.org documents support the standard Delete, Cut and Copy actions and
+the following custom actions:
+
+<ul>
+<li><b>Open:</b> This will open the document in OpenOffice.org using the path
+in the Office Settings property to find the OpenOffice.org installation.
+
+<p>
+If the path to OpenOffice.org is not valid, an error dialog will be popped
+up informing the user that they need to set their Path to Office
+Installation property. This setting can be changed by bringing
+up the Tools/Options dialog and changing
+IDE Configuration/Server and External Tool Settings/Office Settings
+</ul>
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="debugging"></a>
+<h2>Debugging Java OpenOffice.org scripts in NetBeans</h2>
+
+<ul>
+<li>Follow the instructions at
+<a href="http://api.openoffice.org/common/man/IDEintegration/OfficeNetBeansIntegration.html#Debugging">
+Debugging Java components in NetBeans/Forte for Java</a>
+to set up your OpenOffice.org installation to allow debugging of the JVM.
+
+<li>Start OpenOffice.org and run one of your Java scripts. This will
+make sure the JVM is running.
+
+<li>Attach to OpenOffice.org JVM using the NetBeans Debug/Start Session/Attach...
+menu option.
+
+<li>Load a script source in NetBeans and set up breakpoints using
+Debug/New Breakpoint... menu option.
+
+<li>Run the script in OpenOffice.org.
+</ul>
+
+<p>
+<b>Note:</b> As the BeanShell scripting language does not support debugging
+it is not possible to debug BeanShell OpenOffice.org scripts from NetBeans. You
+can however use the Interactive BeanShell scripting menu item under the Tools
+menu in OpenOffice.org to test BeanShell code. Just enter any BeanShell code
+and hit the Eval button to execute it.
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="troubleshooting"></a>
+<h2>Troubleshooting</h2>
+
+<ul>
+<li><p>If you encounter problems when developing or deploying scripts in
+NetBeans, one thing you can try is to move your NetBeans settings directory
+(.netbeans on UNIX, netbeans in Windows - can be found in your home
+directory) to another name and restart NetBeans.
+
+<li><p>The Choose What to Export as Scripts dialog <b>only</b> displays
+methods which are defined within class files, it will not display
+methods in class files which are within jar files in the Parcel Recipe.
+
+<li><p>If you include package directives in the Java source files of your
+Parcel Recipe, you should ensure that the source files are in the appropriate
+directories for your package directives. This is because the
+default NetBeans compiler implementation does not use the -d switch to the
+Java compiler. As a result class files do not get placed in the appropriate
+directories and methods in these classes will not appear in the
+Choose What to Export as Scripts dialog.
+
+<p>
+There are a couple of workarounds for this problem:
+
+<p>
+<ol>
+<li>Use the <a href="commandline-devguide.html">command line tools</a>
+<li>Set the Target flag in the Tools/Options window under
+Building/Compiler Types/Internal Compilation
+</ol>
+</ul>
+
+<p>
+<a href="#top">Top</a>
+
+<hr>
+Last Modified: Nov 19 2003
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/office.jar
==============================================================================
Binary file - no diff available.

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

Added: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/rhino.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/scripting/scriptingf1/rhino.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream



Mime
View raw message