content/framework/scripting/release-0.3/index.html - openoffice-org - Git at Google

 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>
 <head>

 <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
 </head>
 <body>
 <h1>Language Independent Office Scripting Framework</h1>
 <p><b>Project Owners:</b> <a href="mailto:john.rice@sun.com">John Rice</a>,<a
  href="mailto:noel.power@sun.com">Noel Power</a> </p>
 <p>There are currently two ways for users and developers to add
 functionality to OpenOffice.org, namely macros and UNO components. </p>
 <p>Macros are a set of instructions which OpenOffice.org can interpret
 at runtime to carry out a specific set of tasks in OpenOffice.org.
 Users
 can create a macro by recording a number of tasks in OpenOffice.org,
 save this set of tasks as a macro and then bind this macro to a menu or
 keypress. The macro is run by hitting the bound menu or key. Advanced
 users can write their own StarBasic macros in an embedded StarBasic IDE
 if they wish. </p>
 <p>UNO components are compiled C++ or Java components, which a
 developer can write using the UNO API to access and manipulate
 OpenOffice.org. The component is written in an external IDE in C++ or
 Java (or any language with a supported UNO bridge). The end user needs
 to install any new component in their OpenOffice.org to make use of
 this
 new functionality. UNO component development is supported by the ODK. </p>
 <p>The Scripting Framework aims to strike a balance between these two
 approaches of customizing OpenOffice.org. The framework will allow
 scripts to be written in a variety of languages, deployed into
 OpenOffice.org installations or documents, loaded at runtime and
 executed in OpenOffice.org. The framework will allow any number of
 different scripting languages to be plugged into OpenOffice.org for
 which there is an UNO bridge. Our focus will be to support languages
 with a Java implementation, but the framework can be made to work with
 any scripting langauge with a supported UNO bridge such as the UNO
 Python bridge. In this way users and developers will be able to write
 scripts in any supported scripting language to manipulate
 OpenOffice.org. </p>
 <table style="width: 100%; background-color: rgb(240, 240, 240);"
  border="0" cellpadding="2" cellspacing="0">
   <col width="270"> <col width="6"> <col width="220"> <col
  width="171"> <col width="117"> <col width="36"> <tbody>
     <tr>
       <td colspan="6"
  style="background-color: rgb(0, 49, 90); width: 100%;">
       <p align="center"><font color="#ffffff"><b>Documentation for the
 Early Developer Release (Version 0.3)</b> </font> </p>
       </td>
     </tr>
     <tr>
       <th
  style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
       <p align="left"><font color="#00315a"><b>Name</b> </font> </p>
       </th>
       <th colspan="5"
  style="background-color: rgb(153, 204, 255); width: 70%; text-align: left;">
       <p align="left"><font color="#00315a"><b>Description</b> </font>
       </p>
       </th>
     </tr>
     <tr valign="top">
       <td style="width: 30%;">
       <p><a href="./developer-release-features.html">Features</a></p>
       </td>
       <td colspan="5" style="width: 70%;">
       <p>Features of the Early Developer Release</p>
       </td>
     </tr>
     <tr valign="top">
       <td style="width: 30%;">
       <p><a href="./SFrameworkInstall.jar">Download</a></p>
       </td>
       <td colspan="5" style="width: 70%;">
       <p>Download the Office Scripting Framework (2 MB). Refer to the
 install section for installation guidelines. <span
  style="color: rgb(255, 0, 0);">Updated to work with
 OpenOffice.org1.1rc1 and later</span><br>
       </p>
       </td>
     </tr>
     <tr valign="top">
       <td style="width: 30%;">
       <p><a href="./install-guide.html">Install</a></p>
       </td>
       <td colspan="5" style="width: 70%;">
       <p>Installation Guide for the Office Scripting Framework</p>
       </td>
     </tr>
     <tr valign="top">
       <td style="width: 30%;">
       <p><a href="./uninstall-guide.html">Uninstall</a></p>
       </td>
       <td colspan="5" style="width: 70%;">
       <p>Guide for Uninstalling the Office Scripting Framework</p>
       </td>
     </tr>
     <tr valign="top">
       <td rowspan="2" style="width: 30%;">
       <p>Script User Guides</p>
       </td>
       <td colspan="4" style="width: 70%;">
       <p><a href="./user-guide.html">General User Guide</a></p>
       </td>
     </tr>
     <tr>
       <td colspan="4" width="395" valign="top">
       <p><a href="../utilities-download.html">Utility Scripts
 contributed
 by the OpenOffice.org community</a></p>
       </td>
     </tr>
     <tr valign="top">
       <td rowspan="3" width="270">
       <p>Script Developer Guides</p>
       </td>
       <td width="220" colspan="4">
       <p><a href="./developer-guide.html">Writing Scripts in
 BeanShell, JavaScript and Java</a> </p>
       </td>
     </tr>
     <tr>
       <td width="220" colspan="4" valign="top">
       <p><a href="./netbeans-devguide.html">Developing
 Scripts in NetBeans</a> </p>
       </td>
     </tr>
     <tr>
       <td width="220" colspan="4" valign="top">
       <p><a href="./commandline-devguide.html">Developing
 Scripts on the command line</a> </p>
       </td>
     </tr>
     <tr>
       <td style="vertical-align: top;"><a href="./faq.html">FAQ</a></td>
       <td style="vertical-align: top;" colspan="5">Frequently Asked
 Questions for the Office Scripting Framework</td>
     </tr>
     <tr valign="top">
       <td style="width: 30%;">
       <p><a href="./release-notes.html">Release Notes</a></p>
       </td>
       <td colspan="5" style="width: 70%;">
       <p>Release Notes</p>
       </td>
     </tr>
     <tr valign="top">
       <td width="270">
       <p><a href="./SmokeTest.html">Test</a></p>
       </td>
       <td colspan="5" width="566">
       <p>Guidelines for testing the Framework &#8211; Description of basic
 sanity tests (smoke tests) for the framework.</p>
       </td>
     </tr>
     <tr valign="top">
       <td style="width: 30%;">
       <p><a href="./whats-next.html">What's Next</a></p>
       </td>
       <td colspan="5" style="width: 70%;">
       <p>Upcoming features in future releases of the Office Scripting
 Framework</p>
       </td>
     </tr>
   </tbody>
 </table>
 <p>
 <table style="width: 100%; background-color: rgb(240, 240, 240);"
  border="0" cellpadding="2" cellspacing="0">
   <col width="270"> <col width="6"> <col width="220"> <col
  width="171"> <col width="117"> <col width="36"> <tbody>
     <tr>
       <td colspan="5"
  style="width: 100%; background-color: rgb(0, 49, 90);">
       <p align="center"><font color="#ffffff"><b> Previous Releases</b>
       </font> </p>
       </td>
     </tr>
     <tr>
       <th style="background-color: rgb(153, 204, 255); width: 70%;">
       <p align="left"><font color="#00315a"><b>Version</b> </font> </p>
       </th>
       <th colspan="5"
  style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
       <p align="left"><font color="#00315a"><b>Released</b> </font> </p>
       </th>
     </tr>
     <tr valign="top">
       <td style="width: 70%;">
       <p><a href="../release-0.2/index.html">Early Developer Release
 Version 0.2</a></p>
       </td>
       <td colspan="5" style="width: 30%;">
       <p>April 2003</p>
       </td>
     </tr>
     <tr valign="top">
       <td style="width: 70%;">
       <p><a href="../release-0.1/index.html">Early Developer Release
 Version 0.1</a></p>
       </td>
       <td colspan="5" style="width: 30%;">
       <p>November 2002</p>
       </td>
     </tr>
   </tbody>
 </table>
 </p>
 <hr>
 <table cellpadding="4" cellspacing="0" style="width: 100%;">
   <tbody>
     <tr valign="top">
       <td style="width: 30%;">
       <p><a href="mailto:dev@framework.openoffice.org">Mailing List</a></p>
       </td>
       <td style="width: 70%;">
       <p>Installation, User or Developer queries on the Office
 Scripting Framework</p>
       </td>
     </tr>
     <tr valign="top">
       <td style="width: 30%;">
       <p>Issues</p>
       </td>
       <td style="width: 70%;">
       <p>Issues found in the Office Scripting Framework should be
 logged in Issuezilla<br>
       <b>component:</b> framework<br>
       <b>subcomponent:</b> scripting</p>
       </td>
     </tr>
   </tbody>
 </table>
 <p> Last Modified:
 Mon Sep 15 16:59:44 BST 2003
 </p>
 </body>
 </html>
	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
	<html>
	<head>

	<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
	</head>
	<body>
	<h1>Language Independent Office Scripting Framework</h1>
	<p><b>Project Owners:</b> <a href="mailto:john.rice@sun.com">John Rice</a>,<a
	href="mailto:noel.power@sun.com">Noel Power</a> </p>
	<p>There are currently two ways for users and developers to add
	functionality to OpenOffice.org, namely macros and UNO components. </p>
	<p>Macros are a set of instructions which OpenOffice.org can interpret
	at runtime to carry out a specific set of tasks in OpenOffice.org.
	Users
	can create a macro by recording a number of tasks in OpenOffice.org,
	save this set of tasks as a macro and then bind this macro to a menu or
	keypress. The macro is run by hitting the bound menu or key. Advanced
	users can write their own StarBasic macros in an embedded StarBasic IDE
	if they wish. </p>
	<p>UNO components are compiled C++ or Java components, which a
	developer can write using the UNO API to access and manipulate
	OpenOffice.org. The component is written in an external IDE in C++ or
	Java (or any language with a supported UNO bridge). The end user needs
	to install any new component in their OpenOffice.org to make use of
	this
	new functionality. UNO component development is supported by the ODK. </p>
	<p>The Scripting Framework aims to strike a balance between these two
	approaches of customizing OpenOffice.org. The framework will allow
	scripts to be written in a variety of languages, deployed into
	OpenOffice.org installations or documents, loaded at runtime and
	executed in OpenOffice.org. The framework will allow any number of
	different scripting languages to be plugged into OpenOffice.org for
	which there is an UNO bridge. Our focus will be to support languages
	with a Java implementation, but the framework can be made to work with
	any scripting langauge with a supported UNO bridge such as the UNO
	Python bridge. In this way users and developers will be able to write
	scripts in any supported scripting language to manipulate
	OpenOffice.org. </p>
	<table style="width: 100%; background-color: rgb(240, 240, 240);"
	border="0" cellpadding="2" cellspacing="0">
	<col width="270"> <col width="6"> <col width="220"> <col
	width="171"> <col width="117"> <col width="36"> <tbody>
	<tr>
	<td colspan="6"
	style="background-color: rgb(0, 49, 90); width: 100%;">
	<p align="center"><font color="#ffffff"><b>Documentation for the
	Early Developer Release (Version 0.3)</b> </font> </p>
	</td>
	</tr>
	<tr>
	<th
	style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
	<p align="left"><font color="#00315a"><b>Name</b> </font> </p>
	</th>
	<th colspan="5"
	style="background-color: rgb(153, 204, 255); width: 70%; text-align: left;">
	<p align="left"><font color="#00315a"><b>Description</b> </font>
	</p>
	</th>
	</tr>
	<tr valign="top">
	<td style="width: 30%;">
	<p><a href="./developer-release-features.html">Features</a></p>
	</td>
	<td colspan="5" style="width: 70%;">
	<p>Features of the Early Developer Release</p>
	</td>
	</tr>
	<tr valign="top">
	<td style="width: 30%;">
	<p><a href="./SFrameworkInstall.jar">Download</a></p>
	</td>
	<td colspan="5" style="width: 70%;">
	<p>Download the Office Scripting Framework (2 MB). Refer to the
	install section for installation guidelines. <span
	style="color: rgb(255, 0, 0);">Updated to work with
	OpenOffice.org1.1rc1 and later</span><br>
	</p>
	</td>
	</tr>
	<tr valign="top">
	<td style="width: 30%;">
	<p><a href="./install-guide.html">Install</a></p>
	</td>
	<td colspan="5" style="width: 70%;">
	<p>Installation Guide for the Office Scripting Framework</p>
	</td>
	</tr>
	<tr valign="top">
	<td style="width: 30%;">
	<p><a href="./uninstall-guide.html">Uninstall</a></p>
	</td>
	<td colspan="5" style="width: 70%;">
	<p>Guide for Uninstalling the Office Scripting Framework</p>
	</td>
	</tr>
	<tr valign="top">
	<td rowspan="2" style="width: 30%;">
	<p>Script User Guides</p>
	</td>
	<td colspan="4" style="width: 70%;">
	<p><a href="./user-guide.html">General User Guide</a></p>
	</td>
	</tr>
	<tr>
	<td colspan="4" width="395" valign="top">
	<p><a href="../utilities-download.html">Utility Scripts
	contributed
	by the OpenOffice.org community</a></p>
	</td>
	</tr>
	<tr valign="top">
	<td rowspan="3" width="270">
	<p>Script Developer Guides</p>
	</td>
	<td width="220" colspan="4">
	<p><a href="./developer-guide.html">Writing Scripts in
	BeanShell, JavaScript and Java</a> </p>
	</td>
	</tr>
	<tr>
	<td width="220" colspan="4" valign="top">
	<p><a href="./netbeans-devguide.html">Developing
	Scripts in NetBeans</a> </p>
	</td>
	</tr>
	<tr>
	<td width="220" colspan="4" valign="top">
	<p><a href="./commandline-devguide.html">Developing
	Scripts on the command line</a> </p>
	</td>
	</tr>
	<tr>
	<td style="vertical-align: top;"><a href="./faq.html">FAQ</a></td>
	<td style="vertical-align: top;" colspan="5">Frequently Asked
	Questions for the Office Scripting Framework</td>
	</tr>
	<tr valign="top">
	<td style="width: 30%;">
	<p><a href="./release-notes.html">Release Notes</a></p>
	</td>
	<td colspan="5" style="width: 70%;">
	<p>Release Notes</p>
	</td>
	</tr>
	<tr valign="top">
	<td width="270">
	<p><a href="./SmokeTest.html">Test</a></p>
	</td>
	<td colspan="5" width="566">
	<p>Guidelines for testing the Framework – Description of basic
	sanity tests (smoke tests) for the framework.</p>
	</td>
	</tr>
	<tr valign="top">
	<td style="width: 30%;">
	<p><a href="./whats-next.html">What's Next</a></p>
	</td>
	<td colspan="5" style="width: 70%;">
	<p>Upcoming features in future releases of the Office Scripting
	Framework</p>
	</td>
	</tr>
	</tbody>
	</table>
	<p>
	<table style="width: 100%; background-color: rgb(240, 240, 240);"
	border="0" cellpadding="2" cellspacing="0">
	<col width="270"> <col width="6"> <col width="220"> <col
	width="171"> <col width="117"> <col width="36"> <tbody>
	<tr>
	<td colspan="5"
	style="width: 100%; background-color: rgb(0, 49, 90);">
	<p align="center"><font color="#ffffff"><b> Previous Releases</b>
	</font> </p>
	</td>
	</tr>
	<tr>
	<th style="background-color: rgb(153, 204, 255); width: 70%;">
	<p align="left"><font color="#00315a"><b>Version</b> </font> </p>
	</th>
	<th colspan="5"
	style="background-color: rgb(153, 204, 255); width: 30%; text-align: left;">
	<p align="left"><font color="#00315a"><b>Released</b> </font> </p>
	</th>
	</tr>
	<tr valign="top">
	<td style="width: 70%;">
	<p><a href="../release-0.2/index.html">Early Developer Release
	Version 0.2</a></p>
	</td>
	<td colspan="5" style="width: 30%;">
	<p>April 2003</p>
	</td>
	</tr>
	<tr valign="top">
	<td style="width: 70%;">
	<p><a href="../release-0.1/index.html">Early Developer Release
	Version 0.1</a></p>
	</td>
	<td colspan="5" style="width: 30%;">
	<p>November 2002</p>
	</td>
	</tr>
	</tbody>
	</table>
	</p>
	<hr>
	<table cellpadding="4" cellspacing="0" style="width: 100%;">
	<tbody>
	<tr valign="top">
	<td style="width: 30%;">
	<p><a href="mailto:dev@framework.openoffice.org">Mailing List</a></p>
	</td>
	<td style="width: 70%;">
	<p>Installation, User or Developer queries on the Office
	Scripting Framework</p>
	</td>
	</tr>
	<tr valign="top">
	<td style="width: 30%;">
	<p>Issues</p>
	</td>
	<td style="width: 70%;">
	<p>Issues found in the Office Scripting Framework should be
	logged in Issuezilla<br>
	<b>component:</b> framework<br>
	<b>subcomponent:</b> scripting</p>
	</td>
	</tr>
	</tbody>
	</table>
	<p> Last Modified:
	Mon Sep 15 16:59:44 BST 2003
	</p>
	</body>
	</html>