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 [13/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/index.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/index.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/index.html Fri Nov
25 20:00:55 2011
@@ -0,0 +1,323 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE>OpenOffice.org Scripting Framework</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.1 Beta 1 (Solaris Sparc)">
+	<META NAME="CREATED" CONTENT="20021216;16321100">
+	<META NAME="CHANGED" CONTENT="20021216;16360100">
+</HEAD>
+<BODY LANG="en-US" DIR="LTR">
+<H1>Language Independent Office Scripting Framework</H1>
+<P><B>Project Owners:</B> <A HREF="mailto:john.rice@sun.com">John
Rice</A>, <A HREF="mailto:noel.power@sun.com">Noel Power</A>
+</P>
+<P>There are currently two ways for users and developers to add
+functionality to OpenOffice.org, namely macros and UNO components. 
+</P>
+<P>Macros are a set of instructions which OpenOffice.org can
+interpret at runtime to carry out a specific set of tasks in
+OpenOffice.org. Users can create a macro by recording a number of
+tasks in OpenOffice.org, save this set of tasks as a macro and then
+bind this macro to a menu or keypress. The macro is run by hitting
+the bound menu or key. Advanced users can write their own StarBasic
+macros in an embedded StarBasic IDE if they wish. 
+</P>
+<P>UNO components are compiled C++ or Java components, which a
+developer can write using the UNO API to access and manipulate
+OpenOffice.org. The component is written in an external IDE in C++ or
+Java (or any language with a supported UNO bridge). The end user
+needs to install any new component in their OpenOffice.org to make
+use of this new functionality. UNO component development is supported
+by the ODK. 
+</P>
+<P>The Scripting Framework aims to strike a balance between these two
+approaches of customizing OpenOffice.org. The framework will allow
+scripts to be written in a variety of languages, deployed into
+OpenOffice.org installations or documents, loaded at runtime and
+executed in OpenOffice.org. The framework will allow any number of
+different scripting languages to be plugged into OpenOffice.org for
+which there is an UNO bridge. Our focus will be to support languages
+with a Java implementation, but the framework can be made to work
+with any scripting langauge with a supported UNO bridge such as the
+UNO Python bridge. In this way users and developers will be able to
+write scripts in any supported scripting language to manipulate
+OpenOffice.org. 
+</P>
+<TABLE WIDTH=844 BORDER=0 CELLPADDING=2 CELLSPACING=0 BGCOLOR="#f0f0f0">
+	<COL WIDTH=270>
+	<COL WIDTH=6>
+	<COL WIDTH=220>
+	<COL WIDTH=171>
+	<COL WIDTH=117>
+	<COL WIDTH=36>
+	<TR>
+		<TD COLSPAN=6 WIDTH=840 BGCOLOR="#00315a">
+			<P ALIGN=CENTER><FONT COLOR="#ffffff"><B>Documentation for the
+			Early Developer Release (Version 0.2)</B> </FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TH WIDTH=270 BGCOLOR="#99ccff">
+			<P ALIGN=CENTER><FONT COLOR="#00315a"><B>Name</B> </FONT>
+			</P>
+		</TH>
+		<TH COLSPAN=5 WIDTH=566 BGCOLOR="#99ccff">
+			<P ALIGN=CENTER><FONT COLOR="#00315a"><B>Description</B> </FONT>
+			</P>
+		</TH>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="developer-release-features.html">Features</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>Features of the Early Developer Release</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="SFrameworkInstall.jar">Download</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>Download the Office Scripting Framework (2 MB). Refer to the
+			install section for installation guidelines.</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="install-guide.html">Install</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>Installation Guide for the Office Scripting Framework</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="uninstall-guide.html">Uninstall</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>Guide for Uninstalling the Office Scripting Framework</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD ROWSPAN=3 WIDTH=270>
+			<P>Script User Guides</P>
+		</TD>
+		<TD ROWSPAN=2 WIDTH=6></TD>
+		<TD COLSPAN=2 WIDTH=395>
+			<P><A HREF="user-guide.html">General User Guide</A></P>
+		</TD>
+		<TD ROWSPAN=2 COLSPAN=2 WIDTH=157></TD>
+	</TR>
+	<TR>
+		<TD COLSPAN=2 WIDTH=395 VALIGN=TOP>
+			<P><A HREF="../examples-download.html">Examples: Scripts contributed by the
OpenOffice.org community</A></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD COLSPAN=5 WIDTH=566 VALIGN=TOP></TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD ROWSPAN=4 WIDTH=270>
+			<P>Script Developer Guides</P>
+		</TD>
+		<TD ROWSPAN=4 WIDTH=6></TD>
+		<TD WIDTH=220>
+			<P><A HREF="developer-guide.html">Writing Scripts in BeanShell and Java</A>
+						</P>
+		</TD>
+		<TD ROWSPAN=4 COLSPAN=3 WIDTH=332></TD>
+	</TR>
+	<TR>
+		<TD WIDTH=220 VALIGN=TOP>
+			<P><A HREF="javascript-devguide.html">Writing Scripts in JavaScript</A>
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=220 VALIGN=TOP>
+			<P><A HREF="netbeans-devguide.html">Developing Scripts in NetBeans</A>
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=220 VALIGN=TOP>
+			<P><A HREF="commandline-devguide.html">Developing Scripts on the command line</A>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD COLSPAN=5 WIDTH=566 VALIGN=TOP></TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="faq.html">FAQ</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>Frequently Asked Questions for the Office Scripting Framework</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="release-notes.html">Release Notes</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>Release Notes</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="whats-next.html">What's Next</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>Upcoming features in future releases of the Office Scripting
+			Framework</P>
+		</TD>
+	</TR>
+</TABLE>
+
+<P>
+<TABLE WIDTH=844 BORDER=0 CELLPADDING=2 CELLSPACING=0 BGCOLOR="#f0f0f0">
+	<COL WIDTH=270>
+	<COL WIDTH=6>
+	<COL WIDTH=220>
+	<COL WIDTH=171>
+	<COL WIDTH=117>
+	<COL WIDTH=36>
+	<TR>
+		<TD COLSPAN=6 WIDTH=840 BGCOLOR="#00315a">
+			<P ALIGN=CENTER><FONT COLOR="#ffffff"><B>
+			General Documentation</B> </FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TH WIDTH=270 BGCOLOR="#99ccff">
+			<P ALIGN=CENTER><FONT COLOR="#00315a"><B>Name</B> </FONT>
+			</P>
+		</TH>
+		<TH COLSPAN=5 WIDTH=566 BGCOLOR="#99ccff">
+			<P ALIGN=CENTER><FONT COLOR="#00315a"><B>Description</B> </FONT>
+			</P>
+		</TH>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="../release-0.2/build-guide.html">Build</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>Build guide for the Office Scripting Framework</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD ROWSPAN=5 WIDTH=270>
+			<P>Architecture/Design</P>
+		</TD>
+		<TD ROWSPAN=4 WIDTH=6></TD>
+		<TD COLSPAN=3 WIDTH=516>
+			<P>Not Yet Available 
+			</P>
+		</TD>
+		<TD ROWSPAN=4 WIDTH=36></TD>
+	</TR>
+	<TR>
+		<TD COLSPAN=3 WIDTH=516 VALIGN=TOP>
+			<P>Overview of the Framework architecture 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD COLSPAN=3 WIDTH=516 VALIGN=TOP>
+			<P>Diagrams - UML design diagrams for the Office Scripting
+			Framework 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD COLSPAN=3 WIDTH=516 VALIGN=TOP>
+			<P><a href="../EDR-IDLDocs/drafts/com/sun/star/script/framework/module-ix.html">API
documentation</a> (Updated to Version 0.2)
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD COLSPAN=3 WIDTH=516 VALIGN=TOP>
+			<P><a href="runtime-howto.html">Runtime Developer Guide</a> - Guidelines
for implementing Runtimes
+			in other languages 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD COLSPAN=5 WIDTH=566 VALIGN=TOP></TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="SmokeTest.html">Test</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>Guidelines for testing the Framework &ndash; Description of
+			basic sanity tests (smoke tests) for the framework.</P>
+		</TD>
+	</TR>
+</TABLE>
+
+<p>
+<TABLE WIDTH=844 BORDER=0 CELLPADDING=2 CELLSPACING=0 BGCOLOR="#f0f0f0">
+	<COL WIDTH=270>
+	<COL WIDTH=6>
+	<COL WIDTH=220>
+	<COL WIDTH=171>
+	<COL WIDTH=117>
+	<COL WIDTH=36>
+	<TR>
+		<TD COLSPAN=6 WIDTH=840 BGCOLOR="#00315a">
+			<P ALIGN=CENTER><FONT COLOR="#ffffff"><B>
+			Previous Releases</B> </FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TH WIDTH=270 BGCOLOR="#99ccff">
+			<P ALIGN=CENTER><FONT COLOR="#00315a"><B>Version</B> </FONT>
+			</P>
+		</TH>
+		<TH COLSPAN=5 WIDTH=566 BGCOLOR="#99ccff">
+			<P ALIGN=CENTER><FONT COLOR="#00315a"><B>Released</B> </FONT>
+			</P>
+		</TH>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=270>
+			<P><A HREF="../release-0.1/indeX.html">Early Developer Release Version 0.1</A></P>
+		</TD>
+		<TD COLSPAN=5 WIDTH=566>
+			<P>November 2002</P>
+		</TD>
+	</TR>
+</TABLE>
+<HR>
+<TABLE CELLPADDING=4 CELLSPACING=0>
+	<TR VALIGN=TOP>
+		<TD WIDTH=32%>
+			<P><A HREF="mailto:dev@framework.openoffice.org">Mailing List</A></P>
+		</TD>
+		<TD WIDTH=68%>
+			<P>Installation, User or Developer queries on the Office Scripting
+			Framework</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=32%>
+			<P>Issues</P>
+		</TD>
+		<TD WIDTH=68%>
+			<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>
+<P>Last Modified: Fri Nov 29 14:14:24 GMT 2002 
+</P>
+</BODY>
+</HTML>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/install-guide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/install-guide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/install-guide.html
(added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/install-guide.html
Fri Nov 25 20:00:55 2011
@@ -0,0 +1,160 @@
+<html>
+<head>
+<title>Installation and User Guide</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+
+<body>
+<a name="top"></a>     
+
+<h1>Installation Guide for the Office Scripting Framework</h1>
+          
+<h2>Contents</h2>
+
+<ul>
+<li><p><a href="#who">Who Should Read This Document</a>
+<li><p><a href="#prerequisites">Pre-requisites</a>
+<li><p><a href="#download">Downloading the Scripting Framework</a>
+<li><p><a href="#install">Installing the Scripting Framework</a>
+</ul>
+
+<a name="who"></a>
+
+<h2>Who Should Read This Document</h2>
+          
+This document should be read by:
+
+<ul>
+<li><p>Application Developers who wish to enhance OpenOffice.org
+functionality without needing to develop UNO components or to connect to
+OpenOffice.org from a remote JVM
+
+<li><p>OpenOffice.org users who wish to execute Office scripts
+via menu, key and event bindings in OpenOffice.org
+</ul>
+
+<a href="#top">Top</a>
+<a name="prerequisites"></a>
+
+<h2>Pre-requisites</h2>
+
+<ul>
+<li>This is an Early Developer Release of the Office Scripting Framework
+provided for users and developers of OpenOffice.org to try out and provide
+feedback. Future releases of the Framework may change.
+<li>This release of the Scripting Framework runs on
+<a href="http://www.openoffice.org/dev_docs/source/644/index.html">
+<b>OpenOffice.org 644</b></a> and above.
+<li>The Scripting Framework is currently available in English only.
+</ul>
+
+The table below shows the JDK and memory requirements for running the
+Office Scripting Framework.
+
+<p>
+<center>
+<table colspan=4 cellpadding=5 border=1>
+<tr>
+<th>User</th><th>IDE</th><th>JDK required</th><th>Memory
required</th>
+</tr>
+<tr>
+<td>Script User</td><td>-</td><td>1.3</td><td>256MB</td>
+</tr>
+<tr>
+<td>Script Developer</td><td>NetBeans 3.4</td><td>1.3</td><td>512MB</td>
+</tr>
+</table>
+</center>
+
+<a href="#top">Top</a>
+<a name="download"></a>
+
+<h2>Downloading the Scripting Framework</h2>
+
+The Scripting Framework is available for download in the form of a Jar 
+file which can be obtained from <a href="SFrameworkInstall.jar">here</a>.
+The contents of the Jar file are as follows:
+
+<ul>
+<li><b>installer</b> - A platform-independent installer for the Scripting
+Framework written in Java.
+
+<li><b>bindingdialog</b> - A collection of StarBasic dialogs
+to enable the user to assign (bind) scripts to menu and key items,
+and to document and application events. This directory also contains
+the necessary XML files for the menu items that invoke these StarBasic dialogs.
+
+<li><b>examples</b> - Example scripts written in Java and BeanShell.
+
+<li><b>sframework</b> - A UNO package <!--<sup>*</sup>-->
containing
+the Scripting Framework libraries, Jar files and types.
+
+<li><b>ide</b> - The Jar files for NetBeans integration.
+
+</ul>
+
+<!--
+<p>
+<sup>*</sup>See <a href="http://api.openoffice.org/servlets/ProjectDownloadList?action=download&amp;dlID=84">
+&sect;4.7.1</a> of the
+<a href="http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html">
+Office Developers' Guide</a> for a description of the UNO packaging system.
+<p>
+-->
+
+<a href="#top">Top</a>
+<a name="install"></a>
+
+<h2>Installing the Scripting Framework</h2>
+
+Before you begin installation, you need to ensure all Office processes 
+have terminated and on Windows and Linux, that the QuickStarter
+has been closed. <br> 
+
+<br>
+<b>Note:</b> Before installing an updated version of the Scripting Framework,
the previous version should be removed. (See the <a href="uninstall-guide.html">Guide
for Uninstalling</a>) 
+
+<p>
+To install the Scripting Framework:
+
+<ul>
+<li>Open a terminal (Linux/UNIX) or DOS Command Prompt (Windows)
+<li>Ensure that java is in your execution path
+<li>Run the command:
+<font face="Courier, monospace" size="2">java -jar SFrameworkInstall.jar</font>
+</ul>
+
+<p>
+This will start the installer GUI, which you can use to select the Office
+installation to which you want to install the Scripting Framework. The
+framework is installed in the &lt;Office Installation&gt;/user/uno_packages
+directory of the Office installation you choose.
+
+If the installer detects an installation of either
+<a href="http://www.netbeans.org/devhome/docs/releases/builds_archive/release_archive.html">
NetBeans 3.4</a>
+you will be asked whether you wish to install the IDE Add-ins.
+These add-ins provide support for developing and deploying Office Scripts.
+
+<p>
+<b>Note:</b> If you do not wish to use the GUI you can install the
+Scripting Framework and the IDE Add-in via the command line using the command:
+
+<p>
+<font face="Courier, monospace" size="2">
+java -jar SFrameworkInstall.jar -office &lt;Office Installation&gt;
+-netbeans &lt;NetBeans Installation&gt;</font>
+
+<p>
+<b>Note:</b> The installer detects IDE installations by looking for
+session related files in the home directory of the user running the install,
+so in order for your IDE to be detected you will need to have run it at
+least once.
+
+<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/install-guide.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/javascript-devguide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/javascript-devguide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/javascript-devguide.html
(added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/javascript-devguide.html
Fri Nov 25 20:00:55 2011
@@ -0,0 +1,152 @@
+<html>
+<head>
+  <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
+  <meta name="author" content="tomas o connor">
+  <title>Developing Scripts in JavaScript</title>
+</head>
+
+<body>
+<h1>Writing Office Scripts in JavaScript</h1>
+
+A prototype Script Runtime has been developed for JavaScript using the
+<a href="http://www.mozilla.org/rhino/index.html">Rhino JavaScript
+Interpreter</a> from the Mozilla project. This Runtime allows JavaScript
+scripts to be executed in OpenOffice.org. Unlike the BeanShell and Java
+Runtimes the JavaScript Runtime is still in development and is not yet
+fully functional, however it is suitable for experimenting with Office
+scripting in JavaScript.
+
+<p>
+Some known limitations of the JavaScript Runtime are:
+
+<ul>
+<li>Currently the JavaScript Runtime does support loading of Java classes that
+are deployed with the JavaScript script.
+<li>The JavaScript Runtime will not report any errors that occur during the
+execution of the script.
+<li>Currently there is no support for interactive development of
+JavaScript scripts.
+</ul>
+
+<h2>Contents</h2>
+
+<ul>
+<li><p><a href="#install">Installation</a>
+<li><p><a href="#hellow">Hello World in JavaScript</a>
+<li><p><a href="#deploy">Invoking JavaScript in OpenOffice.org</a>
+<li><p><a href="#issues">Issues</a>
+</ul>
+
+<a name="install"><h2>Installation</h2></a>
+
+<ul>
+<li>Download the <a href="jsruntime.zip">JavaScript Runtime UNO package</a>
+<li>If you have OpenOffice.org running you should close it.
+<li>Switch to the directory named program under your OpenOffice.org installation
+directory
+<li>Run the command:
+<p>
+<pre>
+pkgchk &lt;path to your downloaded jsruntime.zip&gt;
+<pre>
+</ul>
+
+<a name="hellow"><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:
+
+<pre>
+importClass(Packages.com.sun.star.uno.UnoRuntime);
+importClass(Packages.com.sun.star.text.XTextDocument);
+
+var oModel = ScriptContext.getDocument(); 
+var oTextdoc = UnoRuntime.queryInterface(XTextDocument, oModel);
+var oText = oTextdoc.getText(); 
+var oCursor = oText.createTextCursor(); 
+
+oText.insertString(oCursor, "Hello World", false);
+</pre>
+
+<p>
+The ScriptContext 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="developer-guide.html#context">Writing Office Scripts
+and the XScriptContext type</a> for the methods available for the XScriptContext type.
+
+<a name="deploy"><h2>Invoking a JavaScript script in OpenOffice.org</h2></a>
+
+You have two choices for making your Hello World script available for
+execution within OpenOffice.org:
+
+<ol>
+<li><b>Using the command line tools</b>
+
+<p>
+You can use the CommandLineTools class available with the Scripting Framework
+to generate and deploy a Script Parcel. To do this with the Hello World script:
+
+<p>
+<ul>
+<li>Create a directory called helloworld and create a file called helloworld.js
+in that directory using the code above
+
+<li>Setup the command line tools according to the instructions on the
+<a href="commandline-devguide.html">Command Line Tools</a> page
+
+<li>To generate a script parcel run the command:
+<p>
+<pre>
+java CommandLineTools -g -l Rhino=.js
+</pre>
+
+<li>To deploy the generated .sxp file:
+<p>
+<pre>
+java CommandLineTools -d &lt;path to helloworld.sxp&gt; &lt;path to your OpenOffice.org&gt;/user/Scripts
+</pre>
+</ul>
+
+<li><b>Manually deploying your script</b>
+
+<p>
+<ul>
+<li>Create a directory called &lt;path to your OpenOffice.org&gt;/user/Scripts/rhino/helloworld
+<li>Create a file helloworld.js in that directory with the Hello World code
+<li>Create a file called parcel-descriptor.xml in that directory with the following
contents:
+
+<p>
+<pre>
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+
+&lt;parcel language=&quot;Rhino&quot; xmlns:parcel=&quot;scripting.dtd&quot;&gt;
+
+    &lt;script language=&quot;Rhino&quot;&gt;
+        &lt;locale lang=&quot;en&quot;&gt;
+            &lt;displayname value=&quot;HelloWorld&quot;/&gt;
+            &lt;description&gt;Insert Hello World in a document&lt;/description&gt;
+        &lt;/locale&gt;
+        &lt;functionname value=&quot;helloworld.js&quot;/&gt;
+        &lt;logicalname value=&quot;HelloWorld.Rhino&quot;/&gt;
+    &lt;/script&gt;
+&lt;/parcel&gt;
+</pre>
+</ul>
+</ol>
+
+<p>
+Once you have the JavaScript ScriptRuntime installed and the Hello World script
+deployed restart OpenOffice.org. See the
+<a href="user-guide.html">Scripting Framework User Guide</a> for instructions
+on how to bind your script to a menu item, key binding or event. To see your
+script set the Location to User and the Language to Rhino in the Assign
+dialogs.
+
+<p>
+If you want to change your Hello World script, just edit the helloworld.js file
+in a text editor, save it and rerun the script using your menu, key or event
+binding. You don't need to restart OpenOffice.org or rebind to the script
+as the Scripting Framework reloads the script each time it runs it.
+
+</body>
+</html>

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

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

Propchange: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/jsruntime.zip
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/netbeans-devguide.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/netbeans-devguide.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/netbeans-devguide.html
(added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/netbeans-devguide.html
Fri Nov 25 20:00:55 2011
@@ -0,0 +1,244 @@
+<html>
+<head>
+<title>Developing Scripts in NetBeans</title>
+
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+
+<body>
+<a name="top"></a>     
+
+<h1>Developing Scripts in NetBeans</h1>
+         
+This document describes how to set up NetBeans for Office 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 Office Documents</a>
+<li><p><a href="#debugging">Debugging Java Office 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 Office 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
+Office API in your scripts.
+-->
+
+<li>The Office Scripting module works with NetBeans 3.4
+
+<li>You should have installed the Office Scripting module during the
+installation process for the Scripting Framework. If you have not installed
+it, see the <a href="install-guide.html">Installation Guide</a> for
+instructions on how to install.
+
+<li>On Linux, you will need to ensure that your DISPLAY environment
+variable is set to &lt;your hostname&gt;:0 in the shell from which you
+start NetBeans to work around a problem with Java GUIs in Office.
+
+<li>Create a directory somewhere on your machine in which you will develop
+your scripts.
+</ul>
+
+Now start NetBeans and mount the directory you created using the
+File/Mount Filesystem menu option. You also need to mount all of the jar
+files in the &lt;Office installation&gt;/program/classes directory in
+order to access the Office API from your scripts.
+<p>
+<a href="#top">Top</a>
+
+<p>
+<a name="recipe-create"></a>
+<h2>Creating a Parcel Recipe</h2>
+
+Office scripts are delivered in Script Parcels. Like Office 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 Office 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 Office 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 Office 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 Office Document
+or to an Office 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 Office 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 Office Documents</h2>
+
+Office Documents are also recognised by NetBeans. Any parcels contained
+in the document will be displayed as nodes of the Office 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.
+
+Office 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 Office using the path
+in the Office Settings property to find the Office installation.
+
+<p>
+If the path to Office 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 Office 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 Office installation to allow debugging of the JVM.
+
+<li>Start OpenOffice and run one of your Java scripts. This will
+make sure the JVM is running.
+
+<li>Attach to Office 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 Office.
+</ul>
+
+<p>
+<b>Note:</b> As the BeanShell scripting language does not support debugging
+it is not possible to debug BeanShell Office 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: Tue Mar 12 11:40:28 GMT 2003
+</body>
+</html>

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

Added: incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/release-notes.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/release-notes.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/release-notes.html
(added)
+++ incubator/ooo/ooo-site/trunk/content/framework/scripting/release-0.2/release-notes.html
Fri Nov 25 20:00:55 2011
@@ -0,0 +1,140 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE>Release Notes for EDR v0.2</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.0  (Solaris Sparc)">
+	<META NAME="CREATED" CONTENT="20030319;16001000">
+	<META NAME="CHANGED" CONTENT="20030320;9393200">
+</HEAD>
+<BODY LANG="en-US">
+<H1>Release Notes</H1>
+<H2>Installation</H2>
+<UL>
+	<LI><P>The installer now takes some optional command line arguments:</P>
+	<PRE STYLE="margin-bottom: 0.51cm"> java -jar SFrameworkInstall.jar [-office &lt;path_to_office_installation&gt;]
+ [-netbeans &lt;path_to_netbeans_installation&gt;]
+ [-help]</PRE>
+	<LI><P>If you are installing the framework on the windows platform (
+	for language other than english ) you may experience difficulties,
+	the installer looks for the sversion.ini file in either the user's
+	home directory or  in the &ldquo;Application  Data&rdquo;
+	sub-directory of the user's home directory. To install the framework
+	copy the sversion.ini file to the user's home directory or to the
+	&ldquo;Application Data&rdquo; sub-directory in the user's home.
+	(Note: you may need to create the sub-directory called &ldquo;Application
+	Data&rdquo;) 
+	</P>
+</UL>
+<H2>Script Binding</H2>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">It is important the only the
+	&quot;Assign Script To ...&quot; dialogs are used to create &amp;
+	delete script bindings for Scripting framework Java &amp; Beanshell
+	scripts. While these bindings also appear in the Tools-&gt;Configure
+	dialog, that dialog should <B>not </B>be used to delete these
+	bindings as the results are undefined and may lead to a loss of all
+	menu items! In a future release, both these dialogs will be
+	integrated, resolving this issue.</P>
+	<LI><P STYLE="margin-bottom: 0cm">&ldquo;Assign Script to ..&rdquo;
+	dialogs work only for the following applications, writer, calc,
+	impress, draw and presentation.</P>
+	<LI><P STYLE="margin-bottom: 0cm">The Languages displayed in the
+	&ldquo;Language&rdquo; combo-box for all &ldquo;Assign Script to
+	...&rdquo; menus is populated with &ldquo;Java&rdquo; by default and
+	then with the corrosponding languages for any associated installed
+	runtimes. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Given that Control-Shift-Digit key
+	combinations are not available to OpenOffice.org on all platforms,
+	these bindings are not supported by the Scripting framework. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">The scripting framework contains a
+	number of helper scripts for its own use. Logical names starting
+	with an underscore followed by a dollar sign and a script name, eg.
+	&quot;_$HelperScript&quot; are reserved for this purpose, and will
+	not be displayed in the assign dialogs. 
+	</P>
+	<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>
+	<LI><P STYLE="margin-bottom: 0cm">In both the Writer &amp; Calc
+	applications, the Format menu is dynamically generated. For this
+	reason the Scripting Framework does not allow the user to bind
+	scripts to entries in the Format menu in any of the applications. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">It is not possible to assign
+	scripts to menus, keys or events in Web or Formula documents (only
+	Writer, Calc, Impress &amp; Draw). 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Currently the Scripting Framework
+	does not prevent the user from duplicating menu entries, for example
+	it is possible to create a second &quot;New&quot; menu entry under
+	the &quot;File&quot; menu. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">The Comboboxes in the &quot;Assign
+	Script To ...&quot; dialogs are not read-only. Editing their
+	contents will prevent the generation of script bindings and will
+	result in a StarBasic error message being displayed. 
+	</P>
+	<LI><P>It is not possible to create top-level menus from the &quot;Assign
+	Script to Menu&quot; dialog. However, the following steps will
+	create a new top-level menu which can then be used in the &quot;Assign
+	Script To Menu&quot; dialog. Open the Tools-&gt;Configure dialog,
+	collapse the top-level menu entry preceding&nbsp; the location where
+	the new top-level menu entry is to be placed and click the &quot;New
+	Menu&quot; button. The new menu &quot;Menu&quot; will be placed
+	below the highlighted menu item. Left clicking this entry, pausing,
+	and left-clicking again (ie. not a double-click), will allow the
+	user to rename the menu. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">The user/Scripts directory should not 
+    be moved or deleted as it contains scripts (in the java/ScriptfrmwrkHelper 
+    directory) that are used by the Scripting Framework (in the creation of 
+    script bindings). While the NetBeans deploy will re-create a missing 
+    user/Scripts directory it does not restore the helper scripts.
+    </P>
+</UL>
+<H2>Script Security</H2>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">Security warning dialogs are
+	displayed upon first invocation, and not on document load as is done
+	for StarBasic. 
+	</P>
+	<LI><P>When the security setting is &quot;Always&quot;, and &quot;Show
+	Warning Before Running&quot; the Scripting Framework displays the
+	correct dialog. StarBasic displays a dialog more appropriate to
+	&quot;According To Path List&quot;, and while this issue has been
+	fixed (<A HREF="http://www.openoffice.org/issues/show_bug.cgi?id=11822">Issue
+	11822</A>) the fix is not present in OpenOffice.org 1.1 beta.</P>
+</UL>
+<H2>IDE &amp; Deployment</H2>
+<UL>
+	<LI><P>On some versions of Solaris problems have been observed in
+	NetBeans when renaming Java source files for Parcel Recipes (<A HREF="http://www.openoffice.org/issues/show_bug.cgi?id=11986">Issue
+	11986</A>). The source files can be successfully renamed by first
+	opening and closing them once, and then attempting the rename. 
+	</P>
+	<LI><P>When deleting a deployed parcel located in an Office document
+	from the NetBeans IDE ,the document should be closed first.</P>
+	<LI><P>The Interactive BeanShell Scripting window does not currently
+        report any errors that occur while evaluating a script, so your
+        BeanShell script may fail silently. See the <a href="user-guide.html">
+        User Guide</a> for an example of how to add debug statements to your
+        BeanShell script.
+	</P>
+</UL>
+<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/release-notes.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message