|
OpenOffice.org Software
Development Kit (SDK) - For own solutions and products
based on OpenOffice.org and Java |
| Jürgen Schmidt Technical Lead
Software Engineering, Star Office Software Entwicklungs
GmbH |
This session describes the opportunities to extend or
control OpenOffice.org with Java or other languages
where an UNO language binding exists.
OpenOffice.org is an open source driven office
productivity formerly based on StarOffice. While it
is widely known that OpenOffice.org is multi-platform
and that it is fully compatible with the Microsoft
Office formats, few to date are aware that it offers
a complete API for developers to support the creation
of own extension or the control of OpenOffice.org
from own applications. The API based on the Universal
Network Objects (UNO) component model which allows
the integration of 100% pure Java components in
OpenOffice.org. It is also possible to control
OpenOffice.org from a Java application to use the
provided office functionality for example a report
generator or a document converter.
The session gives an introduction into the UNO
component model and it will discuss the main API
concepts (hopefully this section will be an extra
session). The capabilities of the API are
demonstrated using some examples of Java-UNO
components. The session provides an overview about
the OpenOffice.org Software Development Kit
(SDK).
The attendees will learn how to use, extend and
customize a professional office application with
Java. They learn to create highly integrated office
components in Java which are platform independent and
can be used on every platform where OpenOffice.org
and Java will be available. This is an advantage for
all who want to create extensions for their office
environment or a wider audience.
Outline
- Introduction
- OpenOffice.org
- short overview (application
areas: writer, calc, draw, impress)
- OpenOffice.org Software Development Kit (SDK)
- short overview
- (optional
- The UNO component model
- Introduction to UNO
- Concepts
- Key features
- )
- Examples
- Calc Add-in component
- Java application using a remote connection to
OpenOffice.org
- demo of a document converter
- code sample
- OfficeBean
- demo of simple examples
- code sample
(the examples may change)
|
| Biography: Jürgen Schmidt has worked
for StarOffice for over five years. He was deeply
involved in the development of the UNO component model
which is the foundation for the StarOffice API.
Currently he is technical lead for the StarOffice
Software Development Kit (SDK) which is used in
StarOffice and OpenOffice.org. |
Back
| The
new development process - How Child
Work Spaces will improve the developer experience and
the quality |
| Erwin Tenhumberg
Product Marketing Manager, Desktop Solutions Group, Sun Microsystems, Inc.
|
Beginning with the OpenOffice.org 1.1 builds a new
development process based on Child Work Spaces (CWS)
was introduced. Due to the new development process
future StarOffice releases will be based on
OpenOffice.org and actually have most of the binaries
in common. What is even more important, the usage of
CWS makes it much easier for developers to contribute
to the OpenOffice.org project. New features and patches
can be developed and tested without interfering with
other projects.
This session will outline the new development process
and explain what tools are available. In addition, the
speaker will talk about the history and illustrate what
the benefits of the new process are compared to the
past. |
| Biography:
Erwin Tenhumberg is a Product Marketing Manager in the
Desktop Solutions Group at Sun Microsystems, Inc. Within this
group he mainly focusses on the developer aspects of both
OpenOffice.org and StarOffice[tm] including the SDK.
Erwin started working for Sun as a Systems Engineer in
Langen, Germany. There he did pre-sales for
various software products including StarOffice and SunRay[tm].
Before Erwin joined Sun he worked for different companies where
he did Java consulting, software development and desktop
application administration and helpdesk.
|
Back
|
The Glow Project - an outlook for
OpenOffice.org Groupware
|
| Colm Smyth Staff Engineer with Sun
Microsystems |
|
Glow is the codename for a groupware client project being
started within the OpenOffice.org Groupware initiative.
The presentation will describe the motivation, goals,
technologies and roadmap for Glow,
and introduce the initial team who are developing
the first milestone.
|
| Biography:
Colm is a software developer with 16 years experience.
He has developed
clients, servers, middleware (object, content, data and messaging)
and some things that defy conventional classification.
He has been with Sun
for over 5 years and currently is a Technical Architect with
the StarOffice
team. Colm is an enthusiastic developer of rich clients in Java
and is Sun's lead engineer on the Glow project
within OpenOffice.org Groupware.
|
Back
|
Scripting OpenOffice.org
in your language of choice. |
| John Rice Staff Engineer with Sun
Microsystems |
The talk will describe the Scripting Framework
being developed to enable any scripting language which
has an UNO bridge to be plugged into OpenOffice.org.
Using the framework users and developers will be able
to write scripts in any supported scripting language to
automate OpenOffice.org.
Developers will learn about the overall design of the
scripting framework and how one would go about writing
their own scripting runtime to plug in their favorite
scripting language to OpenOffice.org. Details of the
Java, Beanshell and Python runtimes will be
presented. |
| Biography: John Rice is a Staff Engineer with
Sun Microsystems, working as technical lead on the
Scripting Framework project for OpenOffice.org
(http://framework.openoffice.org/scripting). John has
over 15 years industrial experience in the development
of software applications. He has worked with companies
including Hitachi, Lotus and ICL, covering
a board range of development areas including neural
network research, Lotus Notes groupware products, ICL/
Fujitsu's document management system and a number of
award winning internet based information management
tools. |
Back
|
Web-based Distributed
Localization of OpenOffice.org |
| János Noll Founder of Free Software
Foundation Hungary |
I will present two "in-house developed" web-based,
database-backed systems for distributed localization of
the OpenOffice.org messages and the help, respectively.
These systems allow involvement of a large number of
people in the localization of OpenOffice.org. This
system has been used for the Hungarian localization
(which is, sadly, far not 100% finished, as of today).
I will also present a "next generation" localization
tool, which is not implemented yet. This tool should
make localization as easy as clicking with the mouse
and entering text.
My talk will be about tools for OpenOffice.org
allowing distributed, Internet-based translation. I
will present two programs and scenarios which helped to
translatethe OpenOffice.org strings and the
OpenOffice.org help, and a plan of an interactive
program, that could make doing translations and
revisions easy and very productive.
The first program has been used to translate the
OpenOffice.org strings. The program provides a
database-backed web-based editor, where individual
strings can be searched for, translated and revised
(marked being good and appropriate) by the registered
translators. The program was written in the popular PHP
web programming language, and it is using Apache,
PostgreSQL, and is running on Linux. The translation
process also includes some scripts that bridge the gap
between the web-based translation engine and the
"standard" OpenOffice.org localization tools.
The second program has been used to translate the
OpenOffice.org help. This tool is conceptionally
similar to the first, but due to the different
structure of the material to-be-translated and the
different tools it uses (T9N toolkit), it has a
slightly different structure which makes it worth to
present this separately.
And last, there is an idea for an interactive, client
program, which can "look up" the message string on the
screen under the mouse cursor in a translation
database, and by identifying it, it can provide access
to the translation allowing to modify or revise it.
This application would radically speed up testing
(QA-ing) a localized OpenOffice.org program. |
Biography: I have been a Linux user and
programmer for 5-6 years now. In the past years, it was
an honor for me to take part in two Hungarian civil
societies, the "LME" (Association of Hungarian Linux
Users), founded in 1998, and the "FSF.hu Foundation for
Propagating and Supporting Free Software in Hungary". I
am using Linux at home and at work, which implies that
I needed a good Office product for writing documents,
presentations and so on. OpenOffice.org fullfilled my
needs, and I've been using it for two years now.
OpenOffice.org localization in Hungary has been lacking
(at least localization of the "GPL" version, as a
commercial OOo-based product is available for money),
that is why I was happy to be an organizer of the 2002
OOo-localization marathon, during which a group of 150
people localized all the approx. 21 thousand strings in
OOo in just 3 days.
In my work I do mostly web programming and system
management, and I work with opensource products
day-by-day. |
Back
|
Packaging
OpenOffice.org |
| Chris Halls The Debian project |
This talk gives an introduction to the process of
making OpenOffice.org packages. It gives an overview of
the existing techniques used to build OOo and integrate
it into the operating system. Also, I will introduce
some of the important tips, tricks, tools and resources
for packages.
The Debian team, and several other distributors, have
been providing their own packages of OpenOffice.org for
their system. The source is modified to integrate
better with the native package management, as well as
taking into account constraints put on the packages by
the rest of the system, including components with
restricted licensing such as the GPC library and the
JDK. The methods used to overcome these problems will
be covered, as well as the concepts behind the extra
features such as language packs, auto user install,
language fallbacks and managing three different
architectures. There are several tools and resources
available for packages, such as various mailing lists,
scripts, ccache & distcc, IRC, some Issuezilla
queries and web resources such as Ximian's LXR and
Tinderbox.
Targeted Audience: People interested in packaging,
porting and the installation of OOo, and those
developers who are interested in techniques to improve
the end user installation experience. |
| Biography: Chris Halls, is a software
developer, living & working in Frankfurt, Germany.
He is also a Debian Developer and part of the team that
packages OpenOffice.org for the Debian distribution, as
well contributing to the tools project. He is 29,
married and is British. |
|
