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

 <!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>
 <P>The Early Developer release (Version 0.1) of the Office Scripting
 Framework will work with <A HREF="http://www.openoffice.org/dev_docs/source/643c/index.html">OpenOffice.org
 643C</A>
 </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.1)</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 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=5 WIDTH=270>
 			<P>Script Developer Guides</P>
 		</TD>
 		<TD ROWSPAN=4 WIDTH=6></TD>
 		<TD WIDTH=220>
 			<P><A HREF="developer-guide.html">General Developer Guidelines</A>
 						</P>
 		</TD>
 		<TD ROWSPAN=4 COLSPAN=3 WIDTH=332></TD>
 	</TR>
 	<TR>
 		<TD WIDTH=220 VALIGN=TOP>
 			<P><A HREF="netbeans-devguide.html">Developer Guide for NetBeans</A>
 						</P>
 		</TD>
 	</TR>
 	<TR>
 		<TD WIDTH=220 VALIGN=TOP>
 			<P><A HREF="jedit-devguide.html">Developer Guide for jEdit</A>
 			</P>
 		</TD>
 	</TR>
 	<TR>
 		<TD WIDTH=220 VALIGN=TOP>
 			<P>Developing Scripts without an IDE
 			</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="issues-list.html">Issues</A></P>
 		</TD>
 		<TD COLSPAN=5 WIDTH=566>
 			<P>Known Issues list for the Early Developer Release</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>
 <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>
	<!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>
	<P>The Early Developer release (Version 0.1) of the Office Scripting
	Framework will work with <A HREF="http://www.openoffice.org/dev_docs/source/643c/index.html">OpenOffice.org
	643C</A>
	</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.1)</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 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=5 WIDTH=270>
	<P>Script Developer Guides</P>
	</TD>
	<TD ROWSPAN=4 WIDTH=6></TD>
	<TD WIDTH=220>
	<P><A HREF="developer-guide.html">General Developer Guidelines</A>
	</P>
	</TD>
	<TD ROWSPAN=4 COLSPAN=3 WIDTH=332></TD>
	</TR>
	<TR>
	<TD WIDTH=220 VALIGN=TOP>
	<P><A HREF="netbeans-devguide.html">Developer Guide for NetBeans</A>
	</P>
	</TD>
	</TR>
	<TR>
	<TD WIDTH=220 VALIGN=TOP>
	<P><A HREF="jedit-devguide.html">Developer Guide for jEdit</A>
	</P>
	</TD>
	</TR>
	<TR>
	<TD WIDTH=220 VALIGN=TOP>
	<P>Developing Scripts without an IDE
	</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="issues-list.html">Issues</A></P>
	</TD>
	<TD COLSPAN=5 WIDTH=566>
	<P>Known Issues list for the Early Developer Release</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>
	<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>