Language Independent Office Scripting FrameworkProject Owners: John Rice, Noel Power There are currently two ways for users and developers to add functionality to OpenOffice.org, namely macros and UNO components. 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. 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. 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.
Last Modified: Fri Nov 29 14:14:24 GMT 2002 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

