blob: 7ec1186369de6e3f7d507cd9c0a748ded635f462 [file] [log] [blame]
<html><head>
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
</head>
<body>
<STYLE>
<!--
-->
</STYLE>
<H1>Glossary</H1>
<TABLE BORDER=0 CELLPADDING=5 CELLSPACING=0>
<THEAD>
<TR VALIGN=TOP>
<TH>
Term
</TH>
<TH>
Definition
</TH>
</TR>
</THEAD>
<TBODY>
<TR VALIGN=TOP>
<TD>
API
</TD>
<TD>
Application Programming Interface.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
AWT
</TD>
<TD>
Abstract Window Toolkit.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
CDF
</TD>
<TD>
Channel Definition Format.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
CHAOS
</TD>
<TD>
Common Hierarchical Access
Object System. This is now known as UCB (Universal Content
Broker).
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
compatible modification
</TD>
<TD>
A modification where the modified files are compatible in a
binary sense. The updated files do not require complete recompilation.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
CVS
</TD>
<TD>
Concurrent Version System, the source control system that
the OpenOffice.org project uses.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
CVS module
</TD>
<TD>
<I>See</I> module.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
DDE
</TD>
<TD>
Dynamic Data Exchange
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
dependency
</TD>
<TD>
When a module must be built before another module is built,
a dependency exists between the two modules. For example, the
<CODE>offmgr</CODE> module must be built before
the <CODE>sw</CODE> module, so <CODE>sw</CODE>
<EM>depends</EM> on <CODE>offmgr</CODE>.
<P>The dependencies between modules mean that the build must
run in a particular order.
</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
FontMetrics
</TD>
<TD>
A Java class that defines a font metrics object, which
contains information about the rendering of a particular font
on a particular screen.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
full build
</TD>
<TD>
This is a full build of StarOffice, respecting the
dependencies between modules.
<P>A weekly build of StarOffice. Release Engineering in Sun
uses powerful hardware to build StarOffice and perform a full
build once a week. Each module delivers shared headers, shared
libraries, and binaries to a collection directory called
<CODE>solver</CODE>, under the root
directory. When the full build is complete, Release
Engineering makes the latest <CODE>solver</CODE>
available to all developers as a tarball.</P>
<P>Each week the source code is tagged with a new build
number, incremented by one from the previous number.</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
IDL
</TD>
<TD>
Interface Definition Language.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
incompatible modification
</TD>
<TD>
A modification that is not compatible, in a binary sense,
with the last full build. The updated files require a
complete recompilation.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
JNI
</TD>
<TD>
Java Native Invocation.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
milestone build
</TD>
<TD>
A regular build of the office suite. This build is assigned a
milestone number, and it is uploaded to the
<a href="/download/index.html">Downloading Stable Build/Source</a> page.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
MIME
</TD>
<TD>
Multipurpose Internet Mail Extensions.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
minor update
</TD>
<TD>
An update where complete recompilation is not required, but where
all sources and output are copied into a separate workspace.
These workspaces are identified with the characters a-z.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
module
</TD>
<TD>
An application, function, or simply a summary of classes. A
module builds a particular component of the office suite.
For example, the <CODE>sw</CODE> module builds
the Word Processing application.
<P>A module is the smallest unit that you can build.</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
output tree
</TD>
<TD>
This is a directory structure that the build process
populates with all the files necessary to build.
The output tree is <CODE>solver</CODE>.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
PCL
</TD>
<TD>
Printer Control Language. A document description language
used by Hewlett-Packard Laserjet printers.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
platform
</TD>
<TD>
A combination of a hardware architecture, a compiler, and an operating
system.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
project
</TD>
<TD>
A logical grouping of modules. For example, the
XML Office project includes the <CODE>xmloff</CODE>
and <CODE>sax</CODE> modules.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
repository
</TD>
<TD>
The location where CVS stores its work files.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
respin build
</TD>
<TD>
This is a build that ignores the dependencies between
modules. Ignoring dependencies allows you to, for example,
modify a base library header file without needing to perform a
full build. <I>See also</I> compatible modification.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
SAL
</TD>
<TD>
System Abstraction Layer.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
SAX
</TD>
<TD>
Simple API for XML.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
<CODE>solver</CODE> milestone build
</TD>
<TD>
<I>See</I> milestone build.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
source tree
</TD>
<TD>
This is a directory structure that stores all of the source
code for the OpenOffice.org project.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
STL
</TD>
<TD>
Standard Template Library.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
stub
</TD>
<TD>
A module file that has no function other than to replace
functionality that cannot be provided by the OpenOffice.org project. For
example, the <CODE>xprinter_stub</CODE> module is
a stub for the XPrinter functions that are not open source.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
top-level update
</TD>
<TD>
All the source is checked out by its top-level revision and
then built. This build is always an incompatible build.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
UCB
</TD>
<TD>
Universal Content Broker. This was formerly known as the
Common Hierarchical Access Object System (CHAOS).
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
UDK
</TD>
<TD>
UNO Developer Kit.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
UNO
</TD>
<TD>
Universal Network Objects.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
VCL
</TD>
<TD>
Visual Class Library.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
VOS
</TD>
<TD>
Virtual Operating System.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
workspace
</TD>
<TD>
The area where all sources are available for building a
project is called workspace.
</TD>
</TR>
<TR VALIGN=TOP>
<TD>
XML
</TD>
<TD>
Extensible Markup Language.
</TD>
</TR>
</TBODY>
</TABLE>
</body>
</html>