Author: mseidel
Date: Tue Jan 1 22:37:08 2019
New Revision: 1850139
URL: http://svn.apache.org/viewvc?rev=1850139&view=rev
Log:
Removed whitespace, fixed typos
Modified:
openoffice/trunk/main/odk/docs/install.html
openoffice/trunk/main/odk/docs/notsupported.html
openoffice/trunk/main/odk/docs/tools.html
openoffice/trunk/main/odk/index.html
Modified: openoffice/trunk/main/odk/docs/install.html
URL:
http://svn.apache.org/viewvc/openoffice/trunk/main/odk/docs/install.html?rev=1850139&r1=1850138&r2=1850139&view=diff
==============================================================================
--- openoffice/trunk/main/odk/docs/install.html (original)
+++ openoffice/trunk/main/odk/docs/install.html Tue Jan 1 22:37:08 2019
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--
#**************************************************************
-#
+#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
@@ -9,16 +9,16 @@
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
-#
+#
# http://www.apache.org/licenses/LICENSE-2.0
-#
+#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
-#
+#
#**************************************************************
-->
<html>
@@ -31,65 +31,65 @@
</head>
<body class="sdkbody"><a name="install"></a>
<table class="table1" cellpadding=0>
- <tr style="background-image:url(images/sdk_head-2.png)">
+ <tr style="background-image:url(images/sdk_head-2.png)">
<td colspan="3" align="left"><img src="images/sdk_head-1.png" width="800"
height="120" usemap="#Map" border="0"></td>
</tr>
- <tr>
- <td colspan="3"><img class="nothing10" src="images/nada.gif"></td>
+ <tr>
+ <td colspan="3"><img class="nothing10" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="3"><img class="nothing1" src="images/nada.gif"></td>
</tr>
- <tr>
- <td>
+ <tr>
+ <td>
<table class="table3">
- <tr>
+ <tr>
<td colspan="2" class="head1">Installation Guide</td>
<td align="right"><a href="../index.html" title="link to the
SDK start page"><img class="navigate" src="images/nav_home.png"></a></td>
- </tr>
+ </tr>
</table>
</td>
</tr>
<tr>
- <td>
+ <td>
<table class="table3">
- <tr>
+ <tr>
<td colspan="2">
- <p>The Apache OpenOffice %PRODUCT_RELEASE% SDK comes with a
set of development tools, base
- libraries, header files and helper class files that can be
used to
- develop Java/C++ components, to embed the Apache OpenOffice
%PRODUCT_RELEASE% application in
- your own programs, or to use the API (scripting or remote
control the
- office). For a complete working environment, we have some
additional
+ <p>The Apache OpenOffice %PRODUCT_RELEASE% SDK comes with a
set of development tools, base
+ libraries, header files and helper class files that can be
used to
+ develop Java/C++ components, to embed the Apache OpenOffice
%PRODUCT_RELEASE% application in
+ your own programs, or to use the API (scripting or remote
control the
+ office). For a complete working environment, we have some
additional
requirements:</p>
</td>
- </tr>
- <tr valign="top">
+ </tr>
+ <tr valign="top">
<td><b>Apache OpenOffice %PRODUCT_RELEASE% installation</b></td>
- <td class="content80">The SDK works on top of an existing
office
+ <td class="content80">The SDK works on top of an existing office
installation and uses the same libraries as the office
installation.</td>
- </tr>
- <tr valign="middle">
+ </tr>
+ <tr valign="middle">
<td colspan="2"><img class="line"
src="images/sdk_line-1.gif"></td>
</tr>
- <tr valign="top">
+ <tr valign="top">
<td><b>JDK (1.5 or higher)</b></td>
<td class="content80">
- <p>A JDK is necessary for developing Java components or
applications. An appropriate Java SDK can be found on <a target="_blank"
href="http://java.sun.com/products"; title="link to the Java SDK download page
(online)">http://java.sun.com/products</a>.</p>
+ <p>A JDK is necessary for developing Java components or
applications. An appropriate Java SDK can be found on <a target="_blank"
href="https://java.sun.com/products"; title="link to the Java SDK download page
(online)">https://java.sun.com/products</a>.</p>
<p>Recommendation is to use Java 6 excepting for Mac OS
because initially Mac OS supported a 64bit version of Java 6 only.</p>
<p><b>Note</b>: The Java compiler is
<b><u>optional</u></b>!</p></td>
</tr>
- <tr valign="middle">
+ <tr valign="middle">
<td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
- <tr valign="top">
+ <tr valign="top">
<td><b>C++ compiler</b></td>
- <td class="content80">A C++ compiler is necessary for developing C++
- components or applications. UNO depends on a compiler
dependent language
- binding, so that we use the appropriate compiler where a
language binding
+ <td class="content80">A C++ compiler is necessary for developing C++
+ components or applications. UNO depends on a compiler
dependent language
+ binding, so that we use the appropriate compiler where a
language binding
exists:
<table class="table4">
<tr>
@@ -107,33 +107,33 @@
</table>
<p><b>Note</b>: The C++ compiler is <b><u>optional</u></b>!
If you use the Express edition you have to ensure that the <a
href="https://www.microsoft.com/en-us/download/details.aspx?id=29";>Microsoft
Visual C++ 2008 Redistributable Package (x86)</a> is also installed. You can
download this package from Microsoft directly.</p></td>
</tr>
- <tr valign="middle">
+ <tr valign="middle">
<td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
- <tr valign="top">
+ <tr valign="top">
<td><b>Microsoft .NET Framework SDK version 1.0 or higher</b></td>
- <td class="content80">The SDK is required for building CLI
applications.
+ <td class="content80">The SDK is required for building CLI
applications.
That is, programs written in languages, such as C# or
VB.NET.<br>
<p><b>Note</b>: The .NET Framework is
<b><u>optional</u></b>!</p></td>
</tr>
- <tr valign="middle">
+ <tr valign="middle">
<td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
- <tr valign="top">
+ <tr valign="top">
<td><b>GNU make (3.79.1 or higher)</b></td>
<td class="content80">
<p>GNU make is used to build the examples of the SDK. GNU
make is available from <a target="_blank" href="http://www.gnu.org"; title="link
to www.gnu.org (online)">http://www.gnu.org</a>. It can be downloaded via FTP
from <a target="_blank" href="ftp://ftp.gnu.org/gnu/make"; title="link to
gnumake on www.gnu.org (online)">ftp://ftp.gnu.org/gnu/make</a></p>
<p><b>Note</b>: Windows user can find an executable of gnu
make under <a target="_blank" href="http://www.mingw.org/wiki/Getting_Started";
title="link to the MinGW Getting Started wiki
(online)">http://www.mingw.org/wiki/Getting_Started</a> (see the mingw32-make
link under "Manual Installation"). Do not use the Cygwin make,
because it does not
work well. On Solaris gnu make can be found often under
<b><i>/usr/sfw/bin/gmake</i></b>, but keep in mind that you have to use
<b>'gmake'</b> then. Or you can find gnu make also under <a target="_blank"
href="http://www.sunfreeware.com/"; title="link to www.sunfreeware.com
(online)">http://www.sunfreeware.com/</a>.</td>
</tr>
- <tr valign="middle">
+ <tr valign="middle">
<td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
- <tr valign="top">
+ <tr valign="top">
<td><b>zip tool (2.3 or higher)</b></td>
- <td class="content80">The zip tool is used to create UNO packages.
zip is
+ <td class="content80">The zip tool is used to create UNO packages.
zip is
a new requirement to make the SDK independent of a Java
SDK.<br>
- If you do not have these already, you can download them from
<a target="_blank" href="http://www.info-zip.org"; title="link to
www.ubfi-zip.org (online)">http://www.info-zip.org</a>. Note: The cygwin
zip.exe does not work for the build under
+ If you do not have these already, you can download them from
<a target="_blank" href="http://www.info-zip.org"; title="link to
www.ubfi-zip.org (online)">http://www.info-zip.org</a>. Note: The cygwin
zip.exe does not work for the build under
the 4NT shell. You have to use the native w32 version.</td>
</tr>
<tr valign="middle">
@@ -146,90 +146,90 @@
<a target="_blank"
href="https://sourceforge.net/projects/unxutils/files/latest/download";
title="link to UnxUtils
(online)">https://sourceforge.net/projects/unxutils/files/latest/download</a>.</p>
</td>
</tr>
- <tr valign="middle">
+ <tr valign="middle">
<td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<td><b>Boost (<b>Unix only</b> and optional)</b></td>
<td class="content80">The boost library is used today on Unix
systems as replacement for the stlport library. The stlport library is removed
and replaced by either the compiler stl (on Windows) or the boost stl on all
Unix based systems. We are planning to switch to the compiler stl completely as
soon as possible. The boost headers/library are <b>optional</b> and for C++
development only if stl containers are used.
<p><b>Download:</b> <a target="_blank"
href="https://sourceforge.net/projects/boost/files/boost/1.48.0/boost_1_48_0.tar.bz2/download";
title="link to boost version 1.48.0
(online)">https://sourceforge.net/projects/boost/files/boost/1.48.0/boost_1_48_0.tar.bz2/download</a>.</p>
</td>
- <tr valign="middle">
+ <tr valign="middle">
<td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
- <tr>
+ <tr>
<td><img class="nothing10" src="images/nada.gif"></td>
<td align="right">
<a href="#install" title="link to the top of this
page"><img class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a></td>
</tr>
- <tr valign="middle">
+ <tr valign="middle">
<td colspan="2">
<p>The SDK provides an implicit configuration mechanism, which
- configures the SDK build environment to your personal needs
the first
+ configures the SDK build environment to your personal needs
the first
time you use the SDK environment. This configuration step
creates a
new setsdkenv_XXX script in the user's home directory:</p>
<ul>
<li><b>$HOME/$OO_SDK_NAME/setsdkenv_unix.sh</b> -> for Unix
- <li><b>C:\Documents and Settings\<username>\Application
Data\%OO_SDK_NAME%\setsdkenv_windows.bat</b> -> for Windows2000/XP
or later
+ <li><b>C:\Documents and Settings\<username>\Application
Data\%OO_SDK_NAME%\setsdkenv_windows.bat</b> -> for Windows 2000/XP
or later
</ul>
- <p>The automatically started configure script (Unix and
Windows2000/XP)
- requests relevant information and directories (SDK, the
Office, GNU make,
- Java, C++), in order to prepare a working SDK environment.
After completing the
- configure script once, the newly created script is always
used to set the
- necessary environment variables for using the SDK and the
required
+ <p>The automatically started configure script (Unix and
Windows 2000/XP)
+ requests relevant information and directories (SDK, the
Office, GNU make,
+ Java, C++), in order to prepare a working SDK environment.
After completing the
+ configure script once, the newly created script is always
used to set the
+ necessary environment variables for using the SDK and the
required
tools.</P>
- <p>On UNIX operating systems, the configure script uses Perl.
LINUX systems should have
- installed a working Perl version, and on Solaris you can find
a working
- Perl version under <a target="_blank"
href="http://www.sunfreeware.com/"; title="link to www.sunfreeware.com
(online)">http://www.sunfreeware.com/</a> if
- necessary. On Windows, the configure script uses Windows
Script and
- a JScipt. If you have problems with Windows Script, you can
download a
- newer version of <a
href="http://www.microsoft.com/downloads/details.aspx?FamilyId=C717D943-7E4B-4622-86EB-95A22B832CAA&displaylang=en";
title="link to the download page for the Windows Script">Windows Script</a>.
+ <p>On UNIX operating systems, the configure script uses Perl.
Linux systems should have
+ installed a working Perl version, and on Solaris you can find
a working
+ Perl version under <a target="_blank"
href="http://www.sunfreeware.com/"; title="link to www.sunfreeware.com
(online)">http://www.sunfreeware.com/</a> if
+ necessary. On Windows, the configure script uses Windows
Script and
+ a JScipt. If you have problems with Windows Script, you can
download a
+ newer version of <a
href="https://www.microsoft.com/downloads/details.aspx?FamilyId=C717D943-7E4B-4622-86EB-95A22B832CAA&displaylang=en";
title="link to the download page for the Windows Script">Windows Script</a>.
</p>
- <p>On other versions of Windows, use the batch
- file template
<b><OO_SDK_HOME>\setsdkenv_windows.template</b>,
+ <p>On other versions of Windows, use the batch
+ file template
<b><OO_SDK_HOME>\setsdkenv_windows.template</b>,
rename it to *.bat, and adapt it to your local
environment.</p>
- <p>If you use the template batch file, edit and set
+ <p>If you use the template batch file, edit and set
the following variables:</p>
<table class="table4">
<tr valign="top">
<td class="cell20"><b>OFFICE_HOME</b></td>
- <td class="cell80">Path to an existing Apache OpenOffice
- installation, e.g. "/opt/openoffice4". Be sure
+ <td class="cell80">Path to an existing Apache OpenOffice
+ installation, e.g. "/opt/openoffice4". Be sure
that it is not a user installation only.</td>
</tr>
<tr><a name="oosdkname"></a>
<td class="cell20"><b>OO_SDK_NAME</b></td>
- <td class="cell80">The configuration uses the
- directory name of the SDK, but you can use another name as
well.
- It is important that the name does not contain spaces,
because of a limitation
- of gnu make which cannot handle spaces correctly. This name
is, for
- example, used to create an output directory in the users home
directory
+ <td class="cell80">The configuration uses the
+ directory name of the SDK, but you can use another name as
well.
+ It is important that the name does not contain spaces,
because of a limitation
+ of gnu make which cannot handle spaces correctly. This name
is, for
+ example, used to create an output directory in the users home
directory
for any generated output when you use the SDK build
environment.</td>
</tr>
<tr>
<td class="cell20"><b>OO_SDK_HOME</b></td>
- <td class="cell80">Path to the SDK root directory, e.g.
- "/usr/local/StarOffice8_SDK"</td>
+ <td class="cell80">Path to the SDK root directory, e.g.
+ "/opt/openoffice4/sdk/"</td>
</tr>
<tr>
<td class="cell20"><b>OO_SDK_JAVA_HOME</b></td>
- <td class="cell80">Path to a JDK root directory. The JDK is
- <b>optional</b> and only necessary if you like to run the
Java examples
- or if you like to use the SDK environment to develop your own
Java
+ <td class="cell80">Path to a JDK root directory. The JDK is
+ <b>optional</b> and only necessary if you like to run the
Java examples
+ or if you like to use the SDK environment to develop your own
Java
solution.</td>
</tr>
<tr>
<td class="cell20"><b>OO_SDK_CPP_HOME</b></td>
- <td class="cell80">Path to the C++ compiler (on Windows, the
directory
- where the "<i>vcvar32.bat</i>" file can be found).
The C++
- compiler is <b>optional</b> and only necessary for building
the C++
+ <td class="cell80">Path to the C++ compiler (on Windows, the
directory
+ where the "<i>vcvar32.bat</i>" file can be found).
The C++
+ compiler is <b>optional</b> and only necessary for building
the C++
examples.</td>
</tr>
<tr>
<td class="cell20"><b>OO_SDK_CLI_HOME</b></td>
- <td class="cell80">Path to the C# compiler and VB.NET
compiler (on
- Windows, this directory can be found under the system
directory (e.g.
- c:\WINXP\Microsoft.NET\Framework\v1.0.3705). The compilers
are
+ <td class="cell80">Path to the C# compiler and VB.NET
compiler (on
+ Windows, this directory can be found under the system
directory (e.g.
+ c:\Windows\Microsoft.NET\Framework\v1.0.3705). The compilers
are
<b>optional</b> and only necessary for building the CLI
examples.<br>
<b>Note: Windows only!</b></td>
</tr>
@@ -255,33 +255,33 @@
</tr>
<tr>
<td class="cell20"><b>OO_SDK_OUTPUT_DIR</b></td>
- <td class="cell80">Path to an existing directory where the
example output
- is generated. The output directory is <b>optional</b>, by
default
- the output is generated in the SDK directory itself. If an
output
- directory is specified, the output is generated in a SDK
dependent
+ <td class="cell80">Path to an existing directory where the
example output
+ is generated. The output directory is <b>optional</b>, by
default
+ the output is generated in the SDK directory itself. If an
output
+ directory is specified, the output is generated in a SDK
dependent
subdirectory in this directory (e.g. <OO_SDK_OUTPUT_DIR>
/Apache OpenOffice %PRODUCT_RELEASE%/LINUXExample.out)</td>
</tr>
<tr>
<td class="cell20"><b>SDK_AUTO_DEPLOYMENT</b></td>
- <td class="cell80">If this variable is set, the component
examples are automatically deployed into the Office installation referenced by
+ <td class="cell80">If this variable is set, the component
examples are automatically deployed into the Office installation referenced by
OFFICE_HOME. See also chapter <a
href="https://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/unopkg";
title="link to the "Extension Manager - unopkg" chapter in the
Developer's Guide">"Extension Manager - unopkg"</a> from the
Developer's Guide.
This variable is only relevant when OFFICE_HOME is set.</td>
</tr>
</table>
- <p>You must run the <b>setsdkenv_XXX</b> script every time
you want to
+ <p>You must run the <b>setsdkenv_XXX</b> script every time
you want to
use the configured SDK environment. The settings are local
for the current
- shell on Windows or the new started shell on UNIX. On UNIX
you
- can now source one of the prepared environment
- script files ("setsdkenv_unix.sh" or
- "setsdkenv_unix.csh" dependending on the shell you
use) to prepare
+ shell on Windows or the new started shell on UNIX. On UNIX you
+ can now source one of the prepared environment
+ script files ("setsdkenv_unix.sh" or
+ "setsdkenv_unix.csh" depending on the shell you
use) to prepare
your current shell instead of starting a new shell.</p>
</td>
</tr>
- <tr valign="middle">
+ <tr valign="middle">
<td colspan="2"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
- <tr>
+ <tr>
<td><img class="nothing10" src="images/nada.gif"></td>
<td align="right">
<a href="#install" title="link to the top of this
page"><img class="navigate" src="images/nav_up.png"></a>
@@ -290,8 +290,8 @@
<tr>
<td colspan="2">
<p class="head2">Manual Setting</p>
- <p>If you do not want to use the script to set your working
- environment, you must set the appropriate environment
variables
+ <p>If you do not want to use the script to set your working
+ environment, you must set the appropriate environment
variables
yourself. The script sets the following environment
variables:</p>
<p class="head3">Common Environment Variables</p>
<table class="table4">
@@ -305,11 +305,11 @@
</tr>
<tr valign="top">
<td class="cell20">OO_SDK_OFFICE_LIB_DIR</td>
- <td class="cell80">The path to the office program directory in the
office installtion (e.g. <i>$OFFICE_HOME/program</i>).</td>
+ <td class="cell80">The path to the office program directory in the
office installation (e.g. <i>$OFFICE_HOME/program</i>).</td>
</tr>
<tr valign="top">
<td class="cell20">OO_SDK_OFFICE_JAVA_DIR</td>
- <td class="cell80">The path to the classes directory in the office
program directory where Java JARs are located (e.g.
+ <td class="cell80">The path to the classes directory in the office
program directory where Java JARs are located (e.g.
<i>$OFFICE_HOME/program/classes</i>).</td>
</tr>
<tr valign="top">
@@ -321,22 +321,22 @@
$OO_SDK_OFFICE_JAVA_DIR/unoloader.jar;
[$OO_SDK_OFFICE_JAVA_DIR/unoil.jar;]
$CLASSPATH</i><br>
- <p>The classpath will be set or extended to the necessary jar files
of
+ <p>The classpath will be set or extended to the necessary jar files
of
the specified office installation.</p>
</td>
</tr>
<tr valign="top">
<td class="cell20">OFFICE_PROGRAM_PATH</td>
<td class="cell80">=<i>$OFFICE_HOME/program</i><br>
- <p>This variable is used to find, for example, the office
type library and
+ <p>This variable is used to find, for example, the office
type library and
the UNO package deployment tool.</p>
</td>
</tr>
<tr valign="top">
<td class="cell20">UNO_PATH</td>
<td class="cell80">=<i>$OFFICE_PROGRAM_PATH</i><br>
- <p>This variable is used to ensure that the new C++ UNO bootstrap
- mechanism uses the configured office installation of the SDK.
Normally
+ <p>This variable is used to ensure that the new C++ UNO bootstrap
+ mechanism uses the configured office installation of the SDK.
Normally
the bootstrap mechanism finds the default office installation
for the
user on the system. This variable is optional but is set from
the scripts
to ensure a homogeneous environment. Especially useful during
development
@@ -351,7 +351,7 @@
<td class="cell20">LD_LIBRARY_PATH</td>
<td class="cell80">=<i>$OO_SDK_OFFICE_LIB_DIR:
$OO_SDK_HOME/(solsparc|solintel)/lib: $LD_LIBRARY_PATH</i><br>
<p>The LD_LIBRARY_PATH will be set or will be extended by the
office
- library path, the platform dependent lib directory for
several additional
+ library path, the platform dependent lib directory for
several additional
libraries.</p>
</td>
</tr>
@@ -359,8 +359,8 @@
<td class="cell20">PATH</td>
<td
class="cell80">=<i>$OO_SDK_HOME/(solsparc|solintel)/bin:$OO_SDK_MAKE_HOME:
$OO_SDK_ZIP_HOME: [$OO_SDK_CPP_HOME:] [$OO_SDK_JAVA_HOME/bin:]
$OO_SDK_OFFICE_BIN_DIR: $PATH</i><br>
<p>The PATH variable will be extended by the paths for the SDK
development
- tools, the compiler, the JDK, GNU make, the zip tool and the
- OO_SDK_OFFICE_BIN_DIR, where the compiler or the JDK are
+ tools, the compiler, the JDK, GNU make, the zip tool and the
+ OO_SDK_OFFICE_BIN_DIR, where the compiler or the JDK are
optional.</p>
</td>
</tr>
@@ -377,7 +377,7 @@
<td class="cell20">LD_LIBRARY_PATH</td>
<td class="cell80">=<i>$OO_SDK_OFFICE_LIB_DIR:
$SDK_HOME/linux/lib: $LD_LIBRARY_PATH</i><br>
<p>The LD_LIBRARY_PATH will be set or will be extended by the
office
- library path, the platform dependent lib directory for some
additional
+ library path, the platform dependent lib directory for some
additional
libraries.</p>
</td>
</tr>
@@ -385,8 +385,8 @@
<td class="cell20">PATH</td>
<td
class="cell80">=<i>$OO_SDK_HOME/linux/bin:$OO_SDK_MAKE_HOME: $OO_SDK_ZIP_HOME:
[$OO_SDK_CPP_HOME:] [$OO_SDK_JAVA_HOME/bin:] $OO_SDK_OFFICE_BIN_DIR:
$PATH</i><br>
<p>The PATH variable will be extended by the paths for the
SDK development
- tools, the compiler, the JDK, GNU make, the zip tool and the
- OO_SDK_OFFICE_BIN_DIR, where the compiler and the JDK are
+ tools, the compiler, the JDK, GNU make, the zip tool and the
+ OO_SDK_OFFICE_BIN_DIR, where the compiler and the JDK are
optional.</p>
</td>
</tr>
@@ -401,42 +401,42 @@
<table class="table4">
<tr valign="top">
<td class="cell20">PATH</td>
- <td class="cell80">=<i>%OO_SDK_HOME%\windows\bin;
%OO_SDK_MAKE_HOME%; %OO_SDK_ZIP_HOME%; [%OO_SDK_CLI_HOME%;]
[%OO_SDK_CPP_HOME%;] [%OO_SDK_JAVA_HOME%\bin;] %OO_SDK_OFFICE_BIN_DIR%;
%PATH%</i><br>
+ <td class="cell80">=<i>%OO_SDK_HOME%\Windows\bin;
%OO_SDK_MAKE_HOME%; %OO_SDK_ZIP_HOME%; [%OO_SDK_CLI_HOME%;]
[%OO_SDK_CPP_HOME%;] [%OO_SDK_JAVA_HOME%\bin;] %OO_SDK_OFFICE_BIN_DIR%;
%PATH%</i><br>
<p>The PATH variable will be extended by the paths for the
SDK development
- tools, the compiler, the JDK, GNU make, the zip tool and the
+ tools, the compiler, the JDK, GNU make, the zip tool and the
OO_SDK_OFFICE_BIN_DIR.</p>
</td>
</tr>
<tr valign="top">
<td class="cell20">LIB</td>
<td class="cell80">=<i>%OO_SDK_HOME%\windows\lib;
%LIB%</i><br>
- <p>The LIB variable will be extended by the path to the
import libraries
+ <p>The LIB variable will be extended by the path to the
import libraries
that are necessary for Windows.</p>
</td>
</tr>
<tr valign="top">
- <td colspan="2" class="cell80">In addition to setting these
environment
- variables, the script calls the
"<i>vcvar32.bat</i>" batch file
- which is provided by the Microsoft Developer Studio to set
the necessary
+ <td colspan="2" class="cell80">In addition to setting these
environment
+ variables, the script calls the
"<i>vcvar32.bat</i>" batch file
+ which is provided by the Microsoft Developer Studio to set
the necessary
environment variables for the compiler.</td>
</tr>
</table>
</td>
</tr>
</table>
- </td>
+ </td>
</tr>
</table>
</td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="nothing30" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
- <tr>
- <td colspan="3">
+ <tr>
+ <td colspan="3">
<div class="centertext">
<p><img class="apachelogo" src="images/sdk-footer-logo.png"
title="Apache Logo" alt="Apache Logo">
Copyright © 2011-2019 The Apache Software Foundation,
Licensed under the Apache License, Version 2.0. Apache, the Apache feather
logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache
Software Foundation. Other names may be trademarks of their respective
owners.<p>
Modified: openoffice/trunk/main/odk/docs/notsupported.html
URL:
http://svn.apache.org/viewvc/openoffice/trunk/main/odk/docs/notsupported.html?rev=1850139&r1=1850138&r2=1850139&view=diff
==============================================================================
--- openoffice/trunk/main/odk/docs/notsupported.html (original)
+++ openoffice/trunk/main/odk/docs/notsupported.html Tue Jan 1 22:37:08 2019
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--
#**************************************************************
-#
+#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
@@ -9,16 +9,16 @@
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
-#
+#
# http://www.apache.org/licenses/LICENSE-2.0
-#
+#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
-#
+#
#**************************************************************
-->
<html>
@@ -35,7 +35,7 @@
<td colspan="3" align="left"><img src="images/sdk_head-1.png" width="800"
height="120" usemap="#Map" border="0"></td>
</tr>
<tr>
- <td colspan="3"><img class="nothing10" src="images/nada.gif"></td>
+ <td colspan="3"><img class="nothing10" src="images/nada.gif"></td>
</tr>
<tr>
<td colspan="3">
Modified: openoffice/trunk/main/odk/docs/tools.html
URL:
http://svn.apache.org/viewvc/openoffice/trunk/main/odk/docs/tools.html?rev=1850139&r1=1850138&r2=1850139&view=diff
==============================================================================
--- openoffice/trunk/main/odk/docs/tools.html (original)
+++ openoffice/trunk/main/odk/docs/tools.html Tue Jan 1 22:37:08 2019
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--
#**************************************************************
-#
+#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
@@ -9,16 +9,16 @@
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
-#
+#
# http://www.apache.org/licenses/LICENSE-2.0
-#
+#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
-#
+#
#**************************************************************
-->
<html>
@@ -31,43 +31,43 @@
<body class="sdkbody"><a name="tools"></a>
<table class="table1" cellpadding=0>
- <tr style="background-image:url(images/sdk_head-2.png)">
+ <tr style="background-image:url(images/sdk_head-2.png)">
<td colspan="3" align="left"><img src="images/sdk_head-1.png" width="800"
height="120" usemap="#Map" border="0"></td>
</tr>
- <tr>
- <td colspan="3"><img class="nothing10" src="images/nada.gif"></td>
+ <tr>
+ <td colspan="3"><img class="nothing10" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="3"><img class="nothing1"
src="images/nada.gif"></td>
</tr>
- <tr>
- <td>
+ <tr>
+ <td>
<table class="table3">
- <tr>
+ <tr>
<td colspan="2" class="head1">Development Tools</td>
<td align="right"><a href="../index.html" title="link
to the SDK start page"><img class="navigate" src="images/nav_home.png"></a></td>
- </tr>
+ </tr>
</table>
</td>
- </tr>
- <tr>
- <td>
+ </tr>
+ <tr>
+ <td>
<table class="table3">
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#unopkg" title="link to the unopkg tool
description">unopkg</a></td>
- <td class="content87">The new UNO package deployment tool. It
comes
+ <td class="content87">The new UNO package deployment tool. It
comes
with the office installation and can be found in the
program
directory of the office installation.</td>
</tr>
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#unoexe" title="link to the uno tool
description">uno</a></td>
- <td class="content87">Tool to provide a UNO runtime environment
and
+ <td class="content87">Tool to provide a UNO runtime environment
and
provide configured (deployed) or single components.
This tool
comes with the office installation and can be found
in the program
directory of the office installation.</td>
@@ -75,42 +75,42 @@
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#regmerge" title="link to the regmerge tool
description">regmerge</a></td>
- <td class="content87">Tool to merge several registry (e.g. type
+ <td class="content87">Tool to merge several registry (e.g. type
libraries) files into one file. <b>Note:</b> Since
OpenOffice.org 3 it is not longer part of the SDK but it comes directly with
the office as part of the <b>ure</b>.</td>
</tr>
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#regview" title="link to the regview tool
description">regview</a></td>
- <td class="content87">Tool to view the content of a registry
file
- in a human readable manner. Special support for type
library
+ <td class="content87">Tool to view the content of a registry file
+ in a human readable manner. Special support for type
library
nodes. <b>Note:</b> Since OpenOffice.org 3 it is not
longer part of the SDK but it comes directly with the office as part of the
<b>ure</b>.</td>
</tr>
- <tr valign="middle">
+ <tr valign="middle">
<td colspan="3"><img class="line"
src="images/sdk_line-1.gif"></td>
</tr>
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#idlc" title="link to the idlc tool
description">idlc</a></td>
- <td class="content87">The UNOIDL compiler, generates a common
- binary type library format as base for all codemaker
tools and
+ <td class="content87">The UNOIDL compiler, generates a common
+ binary type library format as base for all codemaker
tools and
the UNO runtime type library.</td>
</tr>
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#cppumaker" title="link to the cppumaker tool
description">cppumaker</a></td>
- <td class="content87">Tool for generating C++ code for the
UNOIDL
+ <td class="content87">Tool for generating C++ code for the UNOIDL
types stored in a type library.</td>
</tr>
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#javamaker" title="link to the javamaker tool
description">javamaker</a></td>
- <td class="content87">Tool for generating Java class files for
the
+ <td class="content87">Tool for generating Java class files for
the
UNOIDL types stored in a type library.</td>
</tr>
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#climaker" title="link to the climaker tool
description">climaker</a></td>
- <td class="content87">Tool for generating CLI assemblies for the
+ <td class="content87">Tool for generating CLI assemblies for the
UNOIDL types stored in a type library (windows
only).</td>
</tr>
<tr valign="top">
@@ -126,37 +126,37 @@
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#regmerge" title="link to the regmerge tool
description">regmerge</a></td>
- <td class="content87">Tool to merge several registry (e.g. type
+ <td class="content87">Tool to merge several registry (e.g. type
libraries) files into one file.</td>
</tr>
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#regview" title="link to the regview tool
description">regview</a></td>
- <td class="content87">Tool to view the content of a registry
file
- in a human readable manner. Special support for type
library
+ <td class="content87">Tool to view the content of a registry file
+ in a human readable manner. Special support for type
library
nodes.</td>
</tr>
<tr valign="top">
<td class="content3"><img src="images/arrow-1.gif"></td>
<td><a href="#autodoc" title="link to the autodoc tool
description">autodoc</a></td>
- <td class="content87">Tool to generate javadoc-like
documentation
+ <td class="content87">Tool to generate javadoc-like documentation
for C/C++ and UNOIDL files.</td>
</tr>
</table>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a name="unopkg"></a>unopkg</td>
<td align="right">
<a style="a:link:visited #FFFFFF;" href="#tools"
title="link to the tools overview"><img class="navigate"
src="images/nav_up.png"></a>
@@ -164,16 +164,16 @@
</tr>
<tr>
<td colspan="3">
- <p>'unopkg' is a tool for easy deployment of UNO packages in
an existing
- office installation. UNO packages are UNO components (single
libraries or
+ <p>'unopkg' is a tool for easy deployment of UNO packages in
an existing
+ office installation. UNO packages are UNO components (single
libraries or
Jar files or more complex zip files that contains one or more
libraries|
- Jar files, type libraries and configuration items), scripts
and
- Apache OpenOffice %PRODUCT_RELEASE% Basic libraries as zip
package. 'unopkg' is not part of the
- SDK but comes with the office directly and is a development
tool as well
+ Jar files, type libraries and configuration items), scripts
and
+ Apache OpenOffice %PRODUCT_RELEASE% Basic libraries as zip
package. 'unopkg' is not part of the
+ SDK but comes with the office directly and is a development
tool as well
as an end user tool to deploy extension into an office
installation.</p>
- <p>More details concerning deployment and this tool can be
find in the
+ <p>More details concerning deployment and this tool can be
find in the
Developer's Guide: <a
href="https://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/unopkg";
title="link to the "Extension Manager - unopkg" chapter in the
Developer's Guide">Extension Manager - <i>unopkg</i></a>.</p>
- <p><b>Note:</b> This tool works only in the
<i><office>/program</i>
+ <p><b>Note:</b> This tool works only in the
<i><office>/program</i>
directory!</p>
<p class="head2">Usage:</p>
<blockquote>
@@ -200,7 +200,7 @@
</tr>
<tr>
<td class="cell15"><code>reinstall</code></td>
- <td class="cell85">export feature: reinstall all
deployed
+ <td class="cell85">export feature: reinstall all
deployed
packages</td>
</tr>
<tr>
@@ -209,7 +209,7 @@
</tr>
<tr>
<td class="cell15"><code>gui</code></td>
- <td class="cell15">raise Package Manager Graphical User
Interface
+ <td class="cell15">raise Package Manager Graphical User
Interface
(GUI)</td>
</tr>
</table>
@@ -236,13 +236,13 @@
</tr>
<tr>
<td class="cell15"><code>--log-file <file></code></td>
- <td class="cell85">custom log file; default:
+ <td class="cell85">custom log file; default:
<i><cache-dir>/log.txt</i>.</td>
</tr>
<tr>
<td class="cell15"><code>--shared</code></td>
- <td class="cell85">expert feature: operate on shared
installation
- deployment context; run only when no concurrent Office
process(es) are
+ <td class="cell85">expert feature: operate on shared
installation
+ deployment context; run only when no concurrent Office
process(es) are
running!</td>
</tr>
<tr>
@@ -258,31 +258,31 @@
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a name="unoexe"></a>uno</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
- <p>The UNO-starter is for running a component or service
process, and
- providing a runtime environment. Raising a component might
look like
+ <p>The UNO-starter is for running a component or service
process, and
+ providing a runtime environment. Raising a component might
look like
this </p>
- <p><code>[c:\] uno.exe -c MyComponent -l mycomp.dll -r
myregistry.rdb
+ <p><code>[c:\] uno.exe -c MyComponent -l mycomp.dll -r
myregistry.rdb
-- foo bar</code></p>
<p>or</p>
- <p><code>[c:\] uno.exe -s foo.bar.FooBarService -r
myregistry.rdb
+ <p><code>[c:\] uno.exe -s foo.bar.FooBarService -r
myregistry.rdb
-- foo bar</code></p>
- <p>The starter loads the component and instantiates it. The
component
+ <p>The starter loads the component and instantiates it. The
component
must export the interface <a
href="common/ref/com/sun/star/lang/XMain.html" title="link into the IDL
reference to the interface
com.sun.star.lang.XMain">com.sun.star.lang.XMain</a>:</p>
<p>
<code>interface XMain : com::sun::star::uno::XInterface <br>
@@ -296,9 +296,9 @@
};
</code>
</p>
- <p>Method run() will be called and returns the error code
given, back
- to the system. If the uno starter is executed with the -u
(URL) option,
- then XInitialization is used instead of XMain. The -u option
is described
+ <p>Method run() will be called and returns the error code
given, back
+ to the system. If the uno starter is executed with the -u
(URL) option,
+ then XInitialization is used instead of XMain. The -u option
is described
later.</p>
<p class="head2">Usage:</p>
<blockquote>
@@ -315,8 +315,8 @@
<table class="table4">
<tr>
<td class="cell15"><code><HostName></code></td>
- <td class="cell85">Specifying a host name might be necessary to
- distinguish the network interface to be used, if a
machine is part of
+ <td class="cell85">Specifying a host name might be necessary to
+ distinguish the network interface to be used, if a
machine is part of
two networks.</td>
</tr>
<tr>
@@ -325,7 +325,7 @@
</tr>
<tr>
<td class="cell15"><code><Name></code></td>
- <td class="cell85">Identifier for demanded called component
+ <td class="cell85">Identifier for demanded called component
instances.</td>
</tr>
<tr>
@@ -334,50 +334,50 @@
(e.g., c:\myreg.rdb) are used by the ServiceManager.
The <i>ro</i>
ones are opened for reading only; whereas, a single
<i>rw</i> one
will be opened for reading and writing. If the
<i>rw</i> one does
- not exist, then it may be created. Components may read
and write to
+ not exist, then it may be created. Components may read
and write to
store their persistent state.</td>
</tr>
<tr>
<td class="cell15"><code>--singleaccept</code></td>
- <td class="cell85">The uno starter will accept one connection,
+ <td class="cell85">The uno starter will accept one connection,
provide the component instance and die.</td>
</tr>
<tr>
<td class="cell15"><code>--singleinstance</code></td>
- <td class="cell85">The uno starter will accept any number of
- connections, but will provide the same single component
instance any
+ <td class="cell85">The uno starter will accept any number of
+ connections, but will provide the same single component
instance any
time instead of creating a new instance for each
connection.</td>
</tr>
</table>
<p><b>Service <a
href="common/ref/com/sun/star/bridge/UnoUrlResolver.html" title="link into the
IDL reference to the service
com.sun.star.bridge.UnoUrlResolver">com.sun.star.bridge.UnoUrlResolver</a></b></p>
- <p>You can easily connect to a server started with the
- <code>-u (url)</code> option by using this service, giving
the same url
+ <p>You can easily connect to a server started with the
+ <code>-u (url)</code> option by using this service, giving
the same url
to resolve. The service provides you an instance from
remote.</p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a name="idlc"></a>idlc</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
- <p>'idlc' is the UNOIDL compiler. It is a full featured
compiler used
- to check UNODL type definitions and transform valid type
definitions
- into a binary type library format, which is later used by all
codemaker
+ <p>'idlc' is the UNOIDL compiler. It is a full featured
compiler used
+ to check UNODL type definitions and transform valid type
definitions
+ into a binary type library format, which is later used by all
codemaker
tools. It is also used as a dynamic type library for UNO at
runtime.<br>
You can find a syntax description for UNOIDL <a
href="https://wiki.openoffice.org/wiki/Documentation/DevGuide/AppendixD/UNOIDL_Syntax_Specification";
title="link to the "UNOIDL Syntax Specification" chapter in the
Developer's Guide">here</a>.</p>
<p class="head2">Usage:</p>
@@ -388,12 +388,12 @@
<table class="table4">
<tr>
<td class="cell15"><code>file_1 ... file_n</code></td>
- <td class="cell85">specifies one or more idl files.
Only files with
+ <td class="cell85">specifies one or more idl files.
Only files with
the extension '.idl' are valid.</td>
</tr>
<tr>
<td class="cell15"><code>@<filename></code></td>
- <td class="cell85">filename specifies the name of a
command
+ <td class="cell85">filename specifies the name of a
command
file.</td>
</tr>
</table>
@@ -403,14 +403,14 @@
<table class="table4">
<tr>
<td class="cell15"><code>-O<path></code></td>
- <td class="cell85">path describes the output directory.
The
- generated output is a registry file with the same name
as the idl
+ <td class="cell85">path describes the output directory.
The
+ generated output is a registry file with the same name
as the idl
input file.</td>
</tr>
<tr>
<td class="cell15"><code>-I<path></code></td>
- <td class="cell85">path specifies a directory where
included files
- that will be searched by the preprocessor are located.
Multiple
+ <td class="cell85">path specifies a directory where
included files
+ that will be searched by the preprocessor are located.
Multiple
directories can be combined with ';'.</td>
</tr>
<tr>
@@ -419,7 +419,7 @@
</tr>
<tr>
<td class="cell15"><code>-C</code></td>
- <td class="cell85">generates complete type information,
including
+ <td class="cell85">generates complete type information,
including
additional service information and documentation.</td>
</tr>
<tr>
@@ -429,31 +429,31 @@
</table>
</p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a
name="cppumaker"></a>cppumaker</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
- <p>The 'cppumaker' generates a C++ representation for idl
types. The
- cppumaker works on a typelibrary, which is generated by the
UNOIDL
+ <p>The 'cppumaker' generates a C++ representation for idl
types. The
+ cppumaker works on a typelibrary, which is generated by the
UNOIDL
compiler (<a href="#idlc" link="link to the idlc tool
description">idlc</a>).
- It generates the output for all specified types and for all
+ It generates the output for all specified types and for all
types the specified types depend on.</p>
<p class="head2">Usage:</p>
<blockquote>
@@ -464,115 +464,115 @@
<table class="table4">
<tr>
<td class="cell15"><code>-O<path></code></td>
- <td class="cell85">path describes the root directory
for the
- generated output. The output directory tree is
generated under this
+ <td class="cell85">path describes the root directory
for the
+ generated output. The output directory tree is
generated under this
directory.</td>
</tr>
<tr>
<td class="cell15"><code>-T<name><br>
|-T<t1>;<t2>...</code></td>
- <td class="cell85">name specifies a type or a list of
types. The
- output for this type and all dependent types are
generated. If no '-T'
- option is specified, then output for all types is
generated. It is also
- possible to use a wildcard 'xy.*' to generate a
complete module
- inclusive all subdirectories. The use of '-T*' is
equivalent to no '-T'
- option. Example: 'com.sun.star.uno.XInterface' or
+ <td class="cell85">name specifies a type or a list of
types. The
+ output for this type and all dependent types are
generated. If no '-T'
+ option is specified, then output for all types is
generated. It is also
+ possible to use a wildcard 'xy.*' to generate a
complete module
+ inclusive all subdirectories. The use of '-T*' is
equivalent to no '-T'
+ option. Example: 'com.sun.star.uno.XInterface' or
'com.sun.star.uno.*' are valid types.
</td>
</tr>
<tr>
<td class="cell15"><code>-B<name></code></td>
- <td class="cell85">name specifies the base node. All
types are
- searched under this node. Default is the root '/' of
the registry
+ <td class="cell85">name specifies the base node. All
types are
+ searched under this node. Default is the root '/' of
the registry
files.</td>
</tr>
<tr>
<td class="cell15"><code>-L</code></td>
- <td class="cell85">UNO type functions are generated
lightweight, that
- means only the name and typeclass are given and
everything else is
- retrieved from the type library dynamically. The
default is that UNO
- type functions provides enough type information for
boostrapping C++.
+ <td class="cell85">UNO type functions are generated
lightweight, that
+ means only the name and typeclass are given and
everything else is
+ retrieved from the type library dynamically. The
default is that UNO
+ type functions provides enough type information for
bootstrapping C++.
'-L' should be the default for external components.</td>
</tr>
<tr>
<td class="cell15"><code>-C</code></td>
- <td class="cell85">UNO type functions are generated
comprehensive
- that means all necessary information is available for
bridging the
+ <td class="cell85">UNO type functions are generated
comprehensive
+ that means all necessary information is available for
bridging the
type in UNO.
</td>
</tr>
<tr>
<td class="cell15"><code>-G</code></td>
- <td class="cell85">generate only target files which do
not
+ <td class="cell85">generate only target files which do
not
exist.</td>
</tr>
<tr>
<td class="cell15"><code>-Gc</code></td>
- <td class="cell85">generate only target files whose
content will
+ <td class="cell85">generate only target files whose
content will
be changed.</td>
</tr>
<tr>
<td class="cell15"><code>-X<name></code></td>
- <td class="cell85">extra types, which are not be taken
into account
+ <td class="cell85">extra types, which are not be taken
into account
for generation.</td>
</tr>
</table>
</p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a
name="javamaker"></a>javamaker</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
- <p>The 'javamaker' generates the appropriate Java class file
for each idl
- type. The javamaker works on a typelibrary which is generated
by the
+ <p>The 'javamaker' generates the appropriate Java class file
for each idl
+ type. The javamaker works on a typelibrary which is generated
by the
UNOIDL compiler (<a href="#idlc" link="link to the idlc tool
description">idlc</a>).
It generates the output for all specified types and for all
types the specified types depend on.</p>
<p class="head2">Usage:</p>
<blockquote>
<b><code>javamaker [-options] file_1 ... file_n -Xfile_n+1
-Xfile_n+2</code></b>
- </blockquote>
+ </blockquote>
<p class="head2">Options:</p>
<p>
<table class="table4">
<tr>
<td class="cell15"><code>-O<path></code></td>
- <td class="cell85">path describes the root directory
for the
- generated output. The output directory tree is
generated under this
+ <td class="cell85">path describes the root directory
for the
+ generated output. The output directory tree is
generated under this
directory.</td>
</tr>
<tr>
<td
class="cell15"><code>-T<name>|-T<t1>;<t2>...</code></td>
- <td class="cell85">name specifies a type or a list of
types. The
- output for this type and all dependent types are
generated. If no '-T'
- option is specified, then output for all types is
generated. It is also
- possible to use a wildcard 'xy.*' to generate a
complete module
- inclusive all subdirectories. The use of '-T*' is
equivalent to no '-T'
- option. Example: 'com.sun.star.uno.XInterface'
+ <td class="cell85">name specifies a type or a list of
types. The
+ output for this type and all dependent types are
generated. If no '-T'
+ option is specified, then output for all types is
generated. It is also
+ possible to use a wildcard 'xy.*' to generate a
complete module
+ inclusive all subdirectories. The use of '-T*' is
equivalent to no '-T'
+ option. Example: 'com.sun.star.uno.XInterface'
or 'com.sun.star.uno.*' are valid types.
</td>
</tr>
<tr>
<td class="cell15"><code>-B<name></code></td>
- <td class="cell85">name specifies the base node. All
types are
- searched under this node. Default is the root '/' of
the registry
+ <td class="cell85">name specifies the base node. All
types are
+ searched under this node. Default is the root '/' of
the registry
files.</td>
</tr>
<tr>
@@ -581,52 +581,52 @@
</tr>
<tr>
<td class="cell15"><code>-G</code></td>
- <td class="cell85">generate only target files which do
not
+ <td class="cell85">generate only target files which do
not
exist.</td>
</tr>
<tr>
<td class="cell15"><code>-Gc</code></td>
- <td class="cell85">generate only target files whose
content will
+ <td class="cell85">generate only target files whose
content will
be changed.</td>
</tr>
<tr>
<td class="cell15"><code>-X<name></code></td>
- <td class="cell85">extra types, which will not be taken
into account
+ <td class="cell85">extra types, which will not be taken
into account
for generation.</td>
</tr>
</table>
</p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a
name="climaker"></a>climaker</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
- <p>The 'climaker' (windows only) generates the appropriate
CLI assemblies file for each idl
- type. The climaker works on a typelibrary which is generated
by the
+ <p>The 'climaker' (windows only) generates the appropriate
CLI assemblies file for each idl
+ type. The climaker works on a typelibrary which is generated
by the
UNOIDL compiler (<a href="#idlc" link="link to the idlc tool
description">idlc</a>).
It generates the output for all specified types and for all
types the specified types depend on.</p>
<p class="head2">Usage:</p>
<blockquote>
<b><code>climaker <switches> [registry-file-1
registry-file-2 ...]</code></b>
- </blockquote>
+ </blockquote>
<p class="head2">Options:</p>
<p>
<table class="table4">
@@ -691,25 +691,25 @@
</p>
<p><b>Example:</b> <code>climaker --out cli_mytypes.dll
--reference cli_uretypes.dll --extra types.rdb mytypes.rdb</code></p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a
name="uno-skeletonmaker"></a>uno-skeletonmaker</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
<p>The 'uno-skeletonmaker' is a tool to simplify the UNO
component development. It has different modes, from simply dumping code
definitions for different languages on stdout up to generating complete code
skeletons. The generation of code skeletons support common component skeletons
as well as specialized skeletons for special service provider interfaces.</p>
@@ -818,28 +818,28 @@
</table>
</p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
- <td>
+ <td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a
name="regcomp"></a>regcomp</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
- <p>'regcomp' is a tool to register|revoke external UNO
components
+ <p>'regcomp' is a tool to register|revoke external UNO
components
into|from a registry which is used in a UNO environment.</p>
<p class="head2">Usage:</p>
<blockquote>
@@ -850,61 +850,61 @@
<table class="table4">
<tr>
<td class="cell15"><code>-register|revoke</code></td>
- <td class="cell85">register means that the components
will be
+ <td class="cell85">register means that the components
will be
installed and revoke means that they will be
removed.</td>
</tr>
<tr>
<td
class="cell15"><code>-br<registryfile></code></td>
<td class="cell85">the name of the registry used for
bootstrapping
- the program. If the bootstrap registry is specified and
has the same
+ the program. If the bootstrap registry is specified and
has the same
name as the registration registry, '-r' is
optional.</td>
</tr>
<tr>
<td
class="cell15"><code>-r<registryfile></code></td>
- <td class="cell85">the name of the registry (will be
created if
+ <td class="cell85">the name of the registry (will be
created if
it does not exist) where the component should be
registered.</td>
</tr>
<tr>
<td
class="cell15"><code>-c<locationUrls></code></td>
- <td class="cell85">the location of a component (DLL,
Class name,
- or an url of a jar file) or a list of urls separated by
';'s. Note
- that, if a list of urls is specified, the components
must all need
+ <td class="cell85">the location of a component (DLL,
Class name,
+ or an url of a jar file) or a list of urls separated by
';'s. Note
+ that, if a list of urls is specified, the components
must all need
the same loader.</td>
</tr>
<tr>
<td
class="cell15"><code>-l<componentLoaderName></code></td>
- <td class="cell85">the name of the needed loader, if no
loader is
- specified the 'com.sun.star.loader.SharedLibrary' is
used. Supported
- loaders: 'com.sun.star.loader.SharedLibrary' |
+ <td class="cell85">the name of the needed loader, if no
loader is
+ specified the 'com.sun.star.loader.SharedLibrary' is
used. Supported
+ loaders: 'com.sun.star.loader.SharedLibrary' |
'com.sun.star.loader.Java'.</td>
</tr>
</table>
</p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
<td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a
name="regmerge"></a>regmerge</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
- <p>'regmerge' is a small tool to merge different registry
files under a
- specified key into another registry file. If a value already
exists in
- the target file the value is overwritten by the value of the
source
+ <p>'regmerge' is a small tool to merge different registry
files under a
+ specified key into another registry file. If a value already
exists in
+ the target file the value is overwritten by the value of the
source
file.</p>
<p class="head2">Usage:</p>
<blockquote>
@@ -919,45 +919,45 @@
</tr>
<tr>
<td class="cell15"><code><mergefile></code></td>
- <td class="cell85">specifies the merged registry file.
If this file
+ <td class="cell85">specifies the merged registry file.
If this file
doesn't exist, it is created.</td>
</tr>
<tr>
<td class="cell15"><code><mergeKeyName></code></td>
- <td class="cell85">specifies the merge key, everything
is merged
+ <td class="cell85">specifies the merge key, everything
is merged
under this key. If this key doesn't exist, it is
created.</td>
</tr>
<tr>
<td class="cell15"><code><regfile_1> ...
<regfile_n></code></td>
- <td class="cell85">specifies one or more registry files
that are
+ <td class="cell85">specifies one or more registry files
that are
merged.</td>
</tr>
</table>
</p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
<td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a
name="regview"></a>regview</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
- <p>'regview' is a tool to show the contents of a registry
file. The tool
- dumps the hierarchical structure and the values of the nodes
in a human
+ <p>'regview' is a tool to show the contents of a registry
file. The tool
+ dumps the hierarchical structure and the values of the nodes
in a human
readable manner to stdout.</p>
<p class="head2">Usage:</p>
<blockquote>
@@ -968,46 +968,46 @@
<table class="table4">
<tr>
<td class="cell15">-br<registryfile></code></td>
- <td class="cell85">the name of the registry whose
contents should
+ <td class="cell85">the name of the registry whose
contents should
be viewed.</td>
</tr>
<tr>
<td class="cell15"><code><keyName></code></td>
- <td class="cell85">the name of a registry key. The name
must be
- fully qualified; for example, '/' means the root key
and
- '/UCR/com/sun/star/uno/XInterface' shows the type
specification of the
- XInterface type. If no key is specified, the tool dumps
the whole
+ <td class="cell85">the name of a registry key. The name
must be
+ fully qualified; for example, '/' means the root key and
+ '/UCR/com/sun/star/uno/XInterface' shows the type
specification of the
+ XInterface type. If no key is specified, the tool dumps
the whole
content of the registry file.</td>
</tr>
</table>
</p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
<tr>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
<td>
<table class="table2">
- <tr>
+ <tr>
<td colspan="2" class="head1"><a
name="autodoc"></a>autodoc</td>
<td align="right">
<a href="#tools" title="link to the tools overview"><img
class="navigate" src="images/nav_up.png"></a>
<a href="../index.html" title="link to the SDK start
page"><img class="navigate" src="images/nav_home.png"></a>
</td>
- </tr>
+ </tr>
<tr>
<td colspan="3">
- <p>The 'autodoc' tool is used for creating javadoc-like
documentation
+ <p>The 'autodoc' tool is used for creating javadoc-like
documentation
from C++ and UNOIDL source code.</p>
- <p>There are some conventions to follow when documenting C++-
or
+ <p>There are some conventions to follow when documenting C++-
or
UNOIDL-sourcecode. See also the <a
href="https://wiki.openoffice.org/wiki/Documentation/DevGuide/AppendixB/IDL_Documentation_Guidelines";
title="link to the UNOIDL Documentation Guidelines">UNOIDL Documentation
Guidelines</a>.<br>
- If you are not familiar with these, but do know javadoc: For simple
C++
+ If you are not familiar with these, but do know javadoc: For simple
C++
sourcecode documentation, using javadoc-style comments will
work.</p>
<p class="head2">Usage:</p>
<blockquote>
@@ -1019,16 +1019,16 @@
<table class="table4">
<tr>
<td class="cell15"><code>-v <VerboseNr></code></td>
- <td class="cell85"><VerboseNr> == 5 displays the parsed
source
+ <td class="cell85"><VerboseNr> == 5 displays the parsed
source
code tokens, so you can locate which piece caused an
parsing error.<br>
- <VerboseNr> == 2 displays not only the parsed source code,
+ <VerboseNr> == 2 displays not only the parsed source code,
but also the comments.<br><br>
This option must be the first one, if it is used.</td>
</tr>
<tr>
<td class="cell15"><code>-name "<Title>"</code></td>
- <td class="cell85"><Title> occurs as the title of the
start
- page of the HTML output. If this option is omitted, a
default title is
+ <td class="cell85"><Title> occurs as the title of the
start
+ page of the HTML output. If this option is omitted, a
default title is
created.</td>
</tr>
<tr>
@@ -1040,20 +1040,20 @@
<tr>
<td class="cell15"><code>-lg <SourcecodeLanguage></code></td>
<td class="cell85">Possible values are: c++ | idl.<br><br>
- This also specifies which files will be parsed: "c++"
parses
- all files with the endings .hxx and .h, "idl"
parses all
+ This also specifies which files will be parsed: "c++"
parses
+ all files with the endings .hxx and .h, "idl"
parses all
files with the ending '.idl' .<br>
To change this behaviour, see at option <code>-f</code>.</td>
</tr>
<tr>
<td class="cell15"><code>-p <ProjectName>
<ProjectDirectory></code></td>
- <td class="cell85">this option can be used to divide large
code
+ <td class="cell85">this option can be used to divide large
code
bases into different projects.<br>
<ProjectName> gives a user-defined name for the project.<br>
- <ProjectDirectory> is the root to which all paths, given
with the
- following options <code>-t,-d</code> and <code>-f</code>,
are
+ <ProjectDirectory> is the root to which all paths, given
with the
+ following options <code>-t,-d</code> and <code>-f</code>,
are
relative.<br>
- This option can be omitted when there are no projects and
all paths in
+ This option can be omitted when there are no projects and
all paths in
the following options are relative to the working
directory.<br><br>
The "{ ... }*" around the options
<code>-p,-t,-d,-f</code>
indicates, that this whole block of options can be
repeated, each block
@@ -1061,47 +1061,47 @@
</tr>
<tr>
<td class="cell15"><code>-t <SourceTree></code></td>
- <td class="cell85">specifies that all files in the
directory
- <SourceTree> and it's subdirectories are parsed,
where the file
+ <td class="cell85">specifies that all files in the directory
+ <SourceTree> and it's subdirectories are parsed,
where the file
ending matches the option <code>-lg</code>.<br>
- There can be given multiple directories after one <code>-t</code>
+ There can be given multiple directories after one <code>-t</code>
option.<br>
- All relative paths are relative to the
project-rootdirectory,
+ All relative paths are relative to the project-rootdirectory,
given with the <code>-p</code> option.<br>
</td>
</tr>
<tr>
<td class="cell15"><code>-d
<SourceDirectory></code></td>
- <td class="cell85">Specifies that all files in th directory
- <SourceDirectory>, but NOT it's subdirectories, are
parsed, where
+ <td class="cell85">Specifies that all files in th directory
+ <SourceDirectory>, but NOT it's subdirectories, are
parsed, where
the file ending matches the option <code>-lg</code>.<br>
- There can be multiple directories given after one <code>-d</code>
+ There can be multiple directories given after one <code>-d</code>
option.<br>
- All relative paths are relative to the
project-rootdirectory,
+ All relative paths are relative to the project-rootdirectory,
given with the <code>-p</code> option.</td>
</tr>
<tr>
<td class="cell15"><code>-f <SourceFile></code></td>
- <td class="cell85">parses the given file. The ending does not have
+ <td class="cell85">parses the given file. The ending does not have
to match the <code>-lg</code> option.<br>
There can be multiple files given after one <code>-f</code>
option.<br>
- All relative paths are relative to the
project-rootdirectory,
+ All relative paths are relative to the project-rootdirectory,
given with the <code>-p</code> option.</td>
</tr>
</table>
- </p><b>Remark:</b> The sequence of options matters! Use them
in the order given
+ </p><b>Remark:</b> The sequence of options matters! Use them
in the order given
in the "Usage"-paragraph.</p>
</td>
- </tr>
+ </tr>
</table>
</td>
<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
</tr>
- <tr>
+ <tr>
<td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
</tr>
- <tr>
- <td colspan="3">
+ <tr>
+ <td colspan="3">
<div class="centertext">
<p><img class="apachelogo" src="images/sdk-footer-logo.png"
title="Apache Logo" alt="Apache Logo">
Copyright © 2011-2019 The Apache Software Foundation,
Licensed under the Apache License, Version 2.0. Apache, the Apache feather
logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache
Software Foundation. Other names may be trademarks of their respective
owners.<p>
Modified: openoffice/trunk/main/odk/index.html
URL:
http://svn.apache.org/viewvc/openoffice/trunk/main/odk/index.html?rev=1850139&r1=1850138&r2=1850139&view=diff
==============================================================================
--- openoffice/trunk/main/odk/index.html (original)
+++ openoffice/trunk/main/odk/index.html Tue Jan 1 22:37:08 2019
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--
#**************************************************************
-#
+#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
@@ -9,16 +9,16 @@
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
-#
+#
# http://www.apache.org/licenses/LICENSE-2.0
-#
+#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
-#
+#
#**************************************************************
-->
<html>
@@ -36,7 +36,7 @@
<td colspan="3" align="left"><img src="docs/images/sdk_head-1.png"
width="800" height="120" usemap="#Map" border="0"></td>
</tr>
<tr>
- <td colspan="3"><img class="nothing30" src="docs/images/nada.gif"></td>
+ <td colspan="3"><img class="nothing30" src="docs/images/nada.gif"></td>
</tr>
<tr>
<td colspan="3">
