odk/docs/tools.html

   1 <html>
   2 <head>
   3   <title>[TITLE] SDK - Development Tools</title>
   4   <link rel="stylesheet" type="text/css" href="sdk_styles.css">
   5   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   6   <meta name="author" content="J&uuml;rgen Schmidt">
   7   <meta name="created" content="2004-12-14">
   8 </head>
   9
  10 <body class="sdkbody"><a name="tools"/>
  11 <table class="table1" cellpadding=0>
  12   <tr style="background-image:url(images/sdk_head-2.gif); backgorund-position: bottom; ">
  13     <td colspan="2" align="left"><img src="images/sdk_head-1.gif" width="335" height="109" usemap="#Map" border="0"></td>
  14     <td align=right><img src="images/sdk_head-3.gif" width="32" height="109"></td>
  15   </tr>
  16   <tr>
  17     <td colspan="3"><img  class="nothing10" src="images/nada.gif"></td>
  18   </tr>
  19   <tr>
  20     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
  21     <td>
  22       <table class="table2">
  23             <tr>
  24                   <td colspan="3"><img class="nothing1" src="images/nada.gif"></td>
  25         </tr>
  26         <tr>
  27           <td>
  28           <table class="table3">
  29                   <tr>
  30                         <td colspan="2" class="head1">Development Tools</td>
  31                         <td align="right"><a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a></td>
  32                   </tr>
  33                   </table>
  34           </td>
  35         </tr>
  36         <tr>
  37           <td>
  38           <table class="table3">
  39             <tr valign="top">
  40               <td class="content3"><img src="images/arrow-1.gif"></td>
  41               <td><a href="#unopkg"  title="link to the unopkg tool description">unopkg</a></td>
  42               <td class="content87">The new UNO package deployment tool. It comes
  43                           with the office installation and can be found in the program
  44                           directory of the office installation.</td>
  45             </tr>
  46             <tr valign="top">
  47               <td class="content3"><img src="images/arrow-1.gif"></td>
  48               <td><a href="#unoexe"  title="link to the uno tool description">uno</a></td>
  49               <td class="content87">Tool to provide a UNO runtime environment and
  50                           provide configured (deployed) or single components. This tool
  51                           comes with the office installation and can be found in the program
  52                           directory of the office installation.</td>
  53             </tr>
  54            <tr valign="top">
  55               <td class="content3"><img src="images/arrow-1.gif"></td>
  56               <td><a href="#regmerge"  title="link to the regmerge tool description">regmerge</a></td>
  57               <td class="content87">Tool to merge several registry (e.g. type
  58                           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>
  59             </tr>
  60             <tr valign="top">
  61               <td class="content3"><img src="images/arrow-1.gif"></td>
  62               <td><a href="#regview"  title="link to the regview tool description">regview</a></td>
  63               <td class="content87">Tool to view the content of a registry file
  64                           in a human readable manner. Special support for type library
  65                           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>
  66             </tr>
  67             <tr valign="middle">
  68               <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
  69             </tr>
  70             <tr valign="top">
  71               <td class="content3"><img src="images/arrow-1.gif"></td>
  72               <td><a href="#idlc" title="link to the idlc tool description">idlc</a></td>
  73               <td class="content87">The UNOIDL compiler, generates a common
  74                           binary type library format as base for all codemaker tools and
  75                           the UNO runtime type library.</td>
  76             </tr>
  77             <tr valign="top">
  78               <td class="content3"><img src="images/arrow-1.gif"></td>
  79               <td><a href="#cppumaker" title="link to the cppumaker tool description">cppumaker</a></td>
  80               <td class="content87">Tool for generating C++ code for the UNOIDL
  81                           types stored in a type library.</td>
  82             </tr>
  83             <tr valign="top">
  84               <td class="content3"><img src="images/arrow-1.gif"></td>
  85               <td><a href="#javamaker" title="link to the javamaker tool description">javamaker</a></td>
  86               <td class="content87">Tool for generating Java class files for the
  87                           UNOIDL types stored in a type library.</td>
  88             </tr>
  89             <tr valign="top">
  90               <td class="content3"><img src="images/arrow-1.gif"></td>
  91               <td><a href="#uno-skeletonmaker" title="link to the uno-skeletonmaker tool description">uno-skeletonmaker</a></td>
  92               <td class="content87">Tool for dumping type definitions on stdout or generating complete code skeletons for Java/C++.</td>
  93             </tr>
  94             <tr valign="top">
  95               <td class="content3"><img src="images/arrow-1.gif"></td>
  96               <td><a href="#regcomp"  title="link to the regcomp tool description">regcomp</a></td>
  97               <td class="content87">A simple UNO component registration tool.</td>
  98             </tr>
  99             <tr valign="top">
 100               <td class="content3"><img src="images/arrow-1.gif"></td>
 101               <td><a href="#regmerge"  title="link to the regmerge tool description">regmerge</a></td>
 102               <td class="content87">Tool to merge several registry (e.g. type
 103                           libraries) files into one file.</td>
 104             </tr>
 105             <tr valign="top">
 106               <td class="content3"><img src="images/arrow-1.gif"></td>
 107               <td><a href="#regview"  title="link to the regview tool description">regview</a></td>
 108               <td class="content87">Tool to view the content of a registry file
 109                           in a human readable manner. Special support for type library
 110                           nodes.</td>
 111             </tr>
 112             <tr valign="top">
 113               <td class="content3"><img src="images/arrow-1.gif"></td>
 114               <td><a href="#autodoc"  title="link to the autodoc tool description">autodoc</a></td>
 115               <td class="content87">Tool to generate javadoc-like documentation
 116                           for C/C++ and UNOIDL files.</td>
 117             </tr>
 118             </table>
 119           </td>
 120                 </tr>
 121       </table>
 122     </td>
 123         <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 124   </tr>
 125   <tr>
 126     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 127   </tr>
 128   <tr>
 129     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 130     <td>
 131       <table class="table2">
 132         <tr>
 133                   <td colspan="2" class="head1"><a name="unopkg"/>unopkg</td>
 134                   <td align="right">
 135                         <a style="a:link:visited #FFFFFF;" href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 136                         <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a></td>
 137         </tr>
 138                 <tr>
 139                   <td colspan="3">
 140                   <p>'unopkg' is a tool for easy deployment of UNO packages in an existing
 141                   office installation. UNO packages are UNO components (single libraries or
 142                   Jar files or more complex zip files that contains one or more libraries|
 143                   Jar files, type libraries and configuration items), scripts  and
 144                   [PRODUCTNAME] Basic libraries as zip package. 'unopkg' is not part of the
 145                   SDK but comes with the office directly and is a development tool as well
 146                   as an end user tool to deploy extension into an office installation.</p>
 147                   <p>More details concerning deployment and this tool can be find in the
 148                   Developer's Guide: <a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/unopkg" title="link to the &quot;Extension Manager - unopkg&quot; chapter in the Developer's Guide">Extension Manager - <i>unopkg</i></a>.</p>
 149                   <p><b>Note:</b> This tool works only in the <i>&lt;office&gt;/program</i>
 150                   directory!</p>
 151                   <p class="head2">Usage:</p>
 152                   <blockquote>
 153                   <b><code>
 154                     unopkg add &lt;options&gt; package-path...<br>
 155                         unopkg remove &lt;options&gt; package-name...<br>
 156                         unopkg list &lt;options&gt; package-name...<br>
 157                         unopkg reinstall &lt;options&gt;<br>
 158                         unopkg gui<br>
 159                         unopkg -V<br>
 160                         unopkg -h<br>
 161                   </code></b>
 162                   </blockquote>
 163                   <p class="head2">Sub-commands:</p>
 164                   <p>
 165                   <table class="table4">
 166                   <tr>
 167                     <td class="cell15"><code>add</code></td>
 168                         <td class="cell85">add packages</td>
 169                   </tr>
 170                         <tr>
 171                         <td class="cell15"><code>remove</code></td>
 172                         <td class="cell85">remove packages by name</td>
 173           </tr>
 174                   <tr>
 175             <td class="cell15"><code>reinstall</code></td>
 176                         <td class="cell85">export feature: reinstall all deployed
 177                         packages</td>
 178           </tr>
 179                   <tr>
 180             <td class="cell15"><code>list</code></td>
 181                         <td class="cell85">list information about deployed packages</td>
 182           </tr>
 183                   <tr>
 184             <td class="cell15"><code>gui</code></td>
 185                         <td class="cell15">raise Package Manager Graphical User Interface
 186                         (GUI)</td>
 187           </tr>
 188                   </table>
 189                   </p>
 190                   <p class="head2">Options:</p>
 191                   <p>
 192                   <table class="table4">
 193                   <tr>
 194             <td class="cell15"><code>-h, --help</code></td>
 195             <td class="cell85">show this help on the command line</td>
 196           </tr>
 197                   <tr>
 198             <td class="cell15"><code>-V, --version</code></td>
 199                         <td class="cell85">shows version information
 200                         </td>
 201           </tr>
 202           <tr>
 203             <td class="cell15"><code>-v, --verbose</code></td>
 204                         <td class="cell85">dump verbose output to stdout</td>
 205           </tr>
 206                   <tr>
 207             <td class="cell15"><code>-f, --force</code></td>
 208                         <td class="cell85">force overwriting existing packages</td>
 209           </tr>
 210           <tr>
 211             <td class="cell15"><code>--log-file &lt;file&gt;</code></td>
 212                         <td class="cell85">custom log file; default:
 213                         <i>&lt;cache-dir&gt/log.txt</i>.</td>
 214           </tr>
 215           <tr>
 216             <td class="cell15"><code>--shared</code></td>
 217                         <td class="cell85">expert feature: operate on shared installation
 218                         deployment context; run only when no concurrent Office process(es) are
 219                         running!</td>
 220           </tr>
 221           <tr>
 222                     <td class="cell15"><code>--deployment-context &lt;context&gt</code>
 223                         </td>
 224                         <td class="cell85">expert feature: explicit deployment context</td>
 225           </tr>
 226                   </table>
 227                   </p>
 228                   </td>
 229                 </tr>
 230       </table>
 231     </td>
 232         <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 233   </tr>
 234   <tr>
 235     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 236   </tr>
 237   <tr>
 238     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 239     <td>
 240       <table class="table2">
 241         <tr>
 242                   <td colspan="2" class="head1"><a name="unoexe"/>uno</td>
 243                   <td align="right">
 244                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 245                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 246                   </td>
 247         </tr>
 248                 <tr>
 249                   <td colspan="3">
 250                   <p>The UNO-starter is for running a component or service process, and
 251                   providing a runtime environment. Raising a component might look like
 252                   this </p>
 253                   <p><code>[c:\] uno.exe -c MyComponent -l mycomp.dll -r myregistry.rdb
 254                   -- foo bar</code></p>
 255                   <p>or</p>
 256                   <p><code>[c:\] uno.exe -s foo.bar.FooBarService -r myregistry.rdb
 257                   -- foo bar</code></p>
 258                   <p>The starter loads the component and instantiates it. The component
 259                   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>
 260                   <p>
 261                   <code>interface XMain : com::sun::star::uno::XInterface <br>
 262             { <br>
 263               &nbsp;&nbsp;&nbsp; /** This method is called to run the component.<br>
 264               &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
 265               &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; @param aArguments command line arguments <br>
 266               &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; @return process error code to be returned to system <br>
 267               &nbsp;&nbsp;&nbsp; */ <br>
 268               &nbsp;&nbsp;&nbsp; long run( [in] sequence&lt; string &gt; arguments ); <br>
 269             };
 270           </code>
 271                   </p>
 272                   <p>Method run() will be called and returns the error code given, back
 273                   to the system. If the uno starter is executed with the -u (URL) option,
 274                   then XInitialization is used instead of XMain. The -u option is described
 275                   later.</p>
 276                   <p class="head2">Usage:</p>
 277                   <blockquote>
 278                   <b><code>uno (-c&lt;ComponentImplementationName&gt; -l &lt;LocationUrl&gt;
 279                     | -s &lt;ServiceName&gt;) <br>
 280             [-ro &lt;ReadOnlyRegistry1&gt;] [-ro &lt;ReadOnlyRegistry2&gt;] ... [-rw &lt;ReadWriteRegistry&gt;]<br>
 281             [-u uno:(socket[,host=&lt;HostName&gt;][,port=&lt;nnn&gt;]|pipe[,name=&lt;PipeName&gt;]);iiop|urp;&lt;Name&gt;<br>
 282             [--singleaccept] [--singleinstance]] <br>
 283             [-- &lt;Argument1 Argument2 ...&gt;]
 284           </code></b>
 285                   </blockquote>
 286                   <p class="head2">Options:</p>
 287                   <p>
 288                   <table class="table4">
 289           <tr>
 290             <td class="cell15"><code>&lt;HostName&gt;</code></td>
 291             <td class="cell85">Specifying a host name might be necessary to
 292                         distinguish the network interface to be used,if a machine is part of
 293                         two networks.</td>
 294           </tr>
 295           <tr>
 296             <td class="cell15"><code>&lt;PipeName&gt;</code></td>
 297             <td class="cell85">Name of a named pipe.</td>
 298           </tr>
 299           <tr>
 300             <td class="cell15"><code>&lt;Name&gt;</code></td>
 301             <td class="cell85">Identifier for demanded called component
 302                         instances.</td>
 303           </tr>
 304           <tr>
 305             <td class="cell15"><code>&lt;Registries&gt;</code></td>
 306             <td class="cell85">The optional <code>&lt;Registries&gt;</code>
 307                         (e.g., c:\myreg.rdb) are used by the ServiceManager. The <i>ro</i>
 308                         ones are opened for reading only; whereas, a single <i>rw</i> one
 309                         will be opened for reading and writing. If the <i>rw</i> one does
 310                         not exist, then it may be created. Components may read and write to
 311                         store their persistent state.</td>
 312           </tr>
 313           <tr>
 314             <td class="cell15"><code>--singleaccept</code></td>
 315             <td class="cell85">The uno starter will accept one connection,
 316                         provide the component instance and die.</td>
 317           </tr>
 318           <tr>
 319             <td class="cell15"><code>--singleinstance</code></td>
 320             <td class="cell85">The uno starter will accept any number of
 321                         connections, but will provide the same single component instance any
 322                         time instead of creating a new instance for each connection.</td>
 323           </tr>
 324           </table>
 325                   <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>
 326                   <p>You can easily connect to a server started with the
 327                   <code>-u (url)</code> option by using this service, giving the same url
 328                   to resolve. The service provides you an instance from remote.</p>
 329                   </p>
 330                   </td>
 331                 </tr>
 332       </table>
 333     </td>
 334     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 335   </tr>
 336   <tr>
 337     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 338   </tr>
 339   <tr>
 340     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 341     <td>
 342       <table class="table2">
 343         <tr>
 344                   <td colspan="2" class="head1"><a name="idlc"/>idlc</td>
 345                   <td align="right">
 346                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 347                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 348                   </td>
 349         </tr>
 350                 <tr>
 351                   <td colspan="3">
 352                   <p>'idlc' is the UNOIDL compiler.  It is a full featured compiler used
 353                   to check UNODL type definitions and transform valid type definitions
 354                   into a binary type library format, which is later used by all codemaker
 355                   tools. It is also used as a dynamic type library for UNO at runtime.<br>
 356                   You can find a syntax description for UNOIDL <a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/AppendixD/UNOIDL_Syntax_Specification" title="link to the &quot;UNOIDL Syntax Specification&quot; chapter in the Developer's Guide">here</a>.</p>
 357                   <p class="head2">Usage:</p>
 358                   <blockquote>
 359                   <b><code>idlc [-options] file_1 ... file_n | @&lt;filename&gt;</code></b>
 360                   </blockquote>
 361                   <p>
 362                   <table class="table4">
 363                   <tr>
 364             <td class="cell15"><code>file_1 ... file_n</code></td>
 365                         <td class="cell85">specifies one or more idl files. Only files with
 366                         the extension '.idl' are valid.</td>
 367           </tr>
 368                   <tr>
 369             <td class="cell15"><code>@&lt;filename&gt;</code></td>
 370                         <td class="cell85">filename specifies the name of a command
 371                         file.</td>
 372           </tr>
 373                   </table>
 374                   </p>
 375                   <p class="head2">Options:</p>
 376                   <p>
 377                   <table class="table4">
 378                   <tr>
 379             <td class="cell15"><code>-O&lt;path&gt;</code></td>
 380                         <td class="cell85">path describes the output directory. The
 381                         generated output is a registry file with the same name as the idl
 382                         input file.</td>
 383           </tr>
 384           <tr>
 385                     <td class="cell15"><code>-I&lt;path&gt;</code></td>
 386                         <td class="cell85">path specifies a directory where included files
 387                         that will be searched by the preprocessor are located. Multiple
 388                         directories can be combined with ';'.</td>
 389           </tr>
 390                   <tr>
 391             <td class="cell15"><code>-D&lt;name&gt;</code></td>
 392                         <td class="cell85">name defines a macro for the preprocessor.</td>
 393           </tr>
 394                   <tr>
 395             <td class="cell15"><code>-C</code></td>
 396                         <td class="cell85">generates complete type information, including
 397                         additional service information and documentation.</td>
 398           </tr>
 399                   <tr>
 400             <td class="cell15"><code>-h|?</code></td>
 401                         <td class="cell85">print this help message and exit.</td>
 402           </tr>
 403                   </table>
 404                   </p>
 405                   </td>
 406                 </tr>
 407       </table>
 408     </td>
 409     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 410   </tr>
 411   <tr>
 412     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 413   </tr>
 414   <tr>
 415     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 416     <td>
 417       <table class="table2">
 418         <tr>
 419                   <td colspan="2" class="head1"><a name="cppumaker"/>cppumaker</td>
 420                   <td align="right">
 421                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 422                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 423                   </td>
 424         </tr>
 425                 <tr>
 426                   <td colspan="3">
 427                   <p>The 'cppumaker' generates a C++ representation for idl types. The
 428                   cppumaker works on a typelibrary, which is generated by the UNOIDL
 429                   compiler (<a href="#idlc" link="link to the idlc tool description">
 430                   idlc</a>). It generates the output for all specified types and for all
 431                   types the specified types depend on.</p>
 432                   <p class="head2">Usage:</p>
 433                   <blockquote>
 434                   <b><code>cppumaker [-options] file_1 ... file_n</code></b>
 435                   </blockquote>
 436                   <p class="head2">Options:</p>
 437                   <p>
 438                   <table class="table4">
 439                   <tr>
 440             <td class="cell15"><code>-O&lt;path&gt;</code></td>
 441                         <td class="cell85">path describes the root directory for the
 442                         generated output. The output directory tree is generated under this
 443                         directory.</td>
 444           </tr>
 445                   <tr>
 446             <td class="cell15"><code>-T&lt;name&gt;<br>
 447                         |-T&lt;t1&gt;;&lt;t2&gt;...</code></td>
 448                         <td class="cell85">name specifies a type or a list of types. The
 449                         output for this type and all dependent types are generated. If no '-T'
 450                         option is specified, then output for all types is generated. It is also
 451                         possible to use a wildcard 'xy.*' to generate a complete module
 452                         inclusive all subdirectories. The use of '-T*' is equivalent to no '-T'
 453                         option. Example: 'com.sun.star.uno.XInterface' or
 454                         'com.sun.star.uno.*' are valid types.
 455                         </td>
 456           </tr>
 457                   <tr>
 458             <td class="cell15"><code>-B&lt;name&gt;</code></td>
 459                         <td class="cell85">name specifies the base node. All types are
 460                         searched under this node. Default is the root '/' of the registry
 461                         files.</td>
 462           </tr>
 463                   <tr>
 464             <td class="cell15"><code>-L</code></td>
 465                         <td class="cell85">UNO type functions are generated lightweight, that
 466                         means only the name and typeclass are given and everything else is
 467                         retrieved from the type library dynamically. The default is that UNO
 468                         type functions provides enough type information for boostrapping C++.
 469                         '-L' should be the default for external components.</td>
 470           </tr>
 471                   <tr>
 472             <td class="cell15"><code>-C</code></td>
 473                         <td class="cell85">UNO type functions are generated comprehensive
 474                         that means all necessary information is available for bridging the
 475                         type in UNO.
 476             </td>
 477           </tr>
 478                   <tr>
 479             <td class="cell15"><code>-G</code></td>
 480                         <td class="cell85">generate only target files which do not
 481                         exist.</td>
 482           </tr>
 483           <tr>
 484             <td class="cell15"><code>-Gc</code></td>
 485                         <td class="cell85">generate only target files whose content will
 486                         be changed.</td>
 487                   </tr>
 488                   <tr>
 489             <td class="cell15"><code>-X&lt;name&gt;</code></td>
 490                         <td class="cell85">extra types, which are not be taken into account
 491                         for generation.</td>
 492           </tr>
 493                   </table>
 494                   </p>
 495                   </td>
 496                 </tr>
 497       </table>
 498     </td>
 499     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 500   </tr>
 501   <tr>
 502     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 503   </tr>
 504   <tr>
 505     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 506     <td>
 507       <table class="table2">
 508         <tr>
 509                   <td colspan="2" class="head1"><a name="javamaker"/>javamaker</td>
 510                   <td align="right">
 511                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 512                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 513                   </td>
 514         </tr>
 515                 <tr>
 516                   <td colspan="3">
 517                   <p>The 'javamaker' generates the appropriate Java class file for each idl
 518                   type. The javamaker works on a typelibrary which is generated by the
 519                   UNOIDL compiler (<a href="#idlc" link="link to the idlc tool description">
 520                   idlc</a>). It generates the output for all specified types and for all
 521 types the specified types depend on.</p>
 522                   <p class="head2">Usage:</p>
 523                   <blockquote>
 524                   <b><code>javamaker [-options] file_1 ... file_n -Xfile_n+1 -Xfile_n+2</code></b>
 525                   </blockquote>
 526                   <p class="head2">Options:</p>
 527                   <p>
 528                   <table class="table4">
 529                   <tr>
 530             <td class="cell15"><code>-O&lt;path&gt;</code></td>
 531                         <td class="cell85">path describes the root directory for the
 532                         generated output. The output directory tree is generated under this
 533                         directory.</td>
 534           </tr>
 535                   <tr>
 536             <td class="cell15"><code>-T&lt;name&gt;|-T&lt;t1&gt;;&lt;t2&gt;...</code></td>
 537                         <td class="cell85">name specifies a type or a list of types. The
 538                         output for this type and all dependent types are generated. If no '-T'
 539                         option is specified, then output for all types is generated. It is also
 540                         possible to use a wildcard 'xy.*' to generate a complete module
 541                         inclusive all subdirectories. The use of '-T*' is equivalent to no '-T'
 542                         option. Example: 'com.sun.star.uno.XInterface'
 543                         or 'com.sun.star.uno.*' are valid types.
 544             </td>
 545           </tr>
 546                   <tr>
 547                     <td class="cell15"><code>-B&lt;name&gt;</code></td>
 548                         <td class="cell85">name specifies the base node. All types are
 549                         searched under this node. Default is the root '/' of the registry
 550                         files.</td>
 551           </tr>
 552           <tr>
 553             <td class="cell15"><code>-nD</code></td>
 554                         <td class="cell85">no dependent types are generated.</td>
 555           </tr>
 556                   <tr>
 557             <td class="cell15"><code>-G</code></td>
 558                         <td class="cell85">generate only target files which do not
 559                         exist.</td>
 560           </tr>
 561                   <tr>
 562             <td class="cell15"><code>-Gc</code></td>
 563                         <td class="cell85">generate only target files whose content will
 564                         be changed.</td>
 565           </tr>
 566           <tr>
 567             <td class="cell15"><code>-X&lt;name&gt;</code></td>
 568                         <td class="cell85">extra types, which will not be taken into account
 569                         for generation.</td>
 570           </tr>
 571                   </table>
 572                   </p>
 573                   </td>
 574                 </tr>
 575       </table>
 576     </td>
 577     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 578   </tr>
 579   <tr>
 580     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 581   </tr>
 582   <tr>
 583     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 584     <td>
 585       <table class="table2">
 586         <tr>
 587                   <td colspan="2" class="head1"><a name="uno-skeletonmaker"/>uno-skeletonmaker</td>
 588                   <td align="right">
 589                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 590                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 591                   </td>
 592         </tr>
 593                 <tr>
 594                   <td colspan="3">
 595                   <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>
 596                   <p class="head2">Usage:</p>
 597                   <blockquote>
 598                   <b><code>
 599                         uno-skeletonmaker (-env:INIFILENAME=&lt;url&gt; | -env:UNO_TYPES=&lt;url>) dump [&lt;options>] -t &lt;type&gt; ...<br>
 600                         uno-skeletonmaker (-env:INIFILENAME=&lt;url&gt; | -env:UNO_TYPES=&lt;url&gt;) component [&lt;options&gt;] -n &lt;name&gt; -t &lt;type&gt; ...<br>
 601                         uno-skeletonmaker (-env:INIFILENAME=&lt;url&gt; | -env:UNO_TYPES=&lt;url&gt;) calc-add-in [&lt;options&gt;] -n &lt;name&gt; -t &lt;add-in_service&gt;<br>
 602                         uno-skeletonmaker (-env:INIFILENAME=&lt;url&gt; | -env:UNO_TYPES=&lt;url&gt;) add-on [&lt;options&gt;] -n &lt;name&gt; -p &lt;protocol_name:command,...&gt;
 603                         uno-skeletonmaker -V, --version<br>
 604                         uno-skeletonmaker -h, --help<br>
 605                   </code></b>
 606                   </blockquote>
 607                   <p class="head2">Sub-commands:</p>
 608                   <p>
 609                   <table class="table4">
 610                   <tr>
 611                     <td class="cell15"><code>dump</code></td>
 612                     <td class="cell85">dump declarations on stdout (e.g. constructors, methods, type mapping for properties) or complete method bodies with method forwarding.</td>
 613                   </tr>
 614                   <tr>
 615                     <td class="cell15"><code>component</code></td>
 616                     <td class="cell85">generates language specific code skeleton files using the implementation name as the file and class name</td>
 617                   </tr>
 618                   <tr>
 619                     <td class="cell15"><code>calc-add-in</code></td>
 620                     <td class="cell85">generates a language specific code skeleton for a Calc Add-Ins using the implementation name as the file and class name. A service type is necessary, referencing an interface which defines the new add-in functions.</td>
 621                   </tr>
 622                   <tr>
 623                     <td class="cell15"><code>add-on</code></td>
 624                     <td class="cell85">generates a language specific code skeleton for an add-on compnent using the implementation name as the file and class name. The protocol name(s) and the corresponding command(s) have to be specified with the '-p' option.</td>
 625                   </tr>
 626                   </table>
 627                   </p>
 628                   <p class="head2">Options:</p>
 629                   <p>
 630                   <table class="table4">
 631                   <tr>
 632             <td class="cell15"><code>-env:INIFILENAME=&lt;url&gt;</code></td>
 633                         <td class="cell85">url specifies a URL to an UNO ini|rc file of an existing UNO environment (URE, office installation).</td>
 634           </tr>
 635                   <tr>
 636             <td class="cell15"><code>-env:UNO_TYPES=&lt;url&gt;</code></td>
 637                         <td class="cell85">url specifies a binary type library file. It can be a space separated list of urls.</td>
 638           </tr>
 639                   <tr>
 640                     <td class="cell15"><code>-a, --all</code></td>
 641                         <td class="cell85">list all interface methods, not only the direct ones</td>
 642           </tr>
 643           <tr>
 644             <td class="cell15"><code>--(java4|java5|cpp)</code></td>
 645                         <td class="cell85">select the target language<br>
 646                         --java4 generate output for Java 1.4 or earlier<br>
 647                         --java5 generate output for Java 1.5 or later (is currently the default)<br>
 648                         --cpp generate output for C++</td>
 649           </tr>
 650                   <tr>
 651             <td class="cell15"><code>-sn, --shortnames</code></td>
 652                         <td class="cell85">using namespace abbreviation 'css:': for     '::com::sun::star::', only valid for sub-command 'dump' and target language 'cpp'. It is default for the sub-command 'component'.</td>
 653           </tr>
 654                   <tr>
 655             <td class="cell15"><code>--propertysetmixin</code></td>
 656                         <td class="cell85">the generated skeleton implements the cppu::PropertySetMixin helper if a referenced new style service specifies an interface which provides attributes (directly or inherited).</td>
 657           </tr>
 658           <tr>
 659             <td class="cell15"><code>-lh --licenseheader</code></td>
 660                         <td class="cell85">generates a default OpenOffice.org LGPL license header at the beginning of a component source file. This option is taken into account in 'component' mode only and if -o is unequal 'stdout'.</td>
 661           </tr>
 662           <tr>
 663             <td class="cell15"><code>-bc<br>--backward-compatible</code></td>
 664                         <td class="cell85">specifies that the generated calc add-in is backward compatible to older office versions and implement the former required add-in interfaces where the implementation is mapped on the new add-in configuration. In this case the config schema needs to be bundled with the extension add-in as well. Default is a minimal add-in component skeleton based on the add-in configuration coming with the office since OO.org 2.0.4.</td>
 665           </tr>
 666           <tr>
 667             <td class="cell15"><code>-o &lt;path&gt;</code></td>
 668                         <td class="cell85">path specifies an existing directory where the output files are generated to, only valid for sub-command 'component'. If path=stdout the generated code is generated on standard out instead of a file.</td>
 669           </tr>
 670           <tr>
 671             <td class="cell15"><code>-l &lt;file&gt;</code></td>
 672                         <td class="cell85">specifies a binary type library (can be used more than once). The type library is integrated as an additional type provider in the bootstrapped type system.</td>
 673           </tr>
 674           <tr>
 675             <td class="cell15"><code>-n &lt;name&gt;</code></td>
 676                         <td class="cell85">specifies an implementation name for the component (used as classname, filename and package|namespace name). In 'dump' mode it is used as classname (e.g. &quot;MyBase::&quot;, C++ only) to generate method bodies not inline.</td>
 677           </tr>
 678           <tr>
 679             <td class="cell15"><code>-d &lt;name&gt;</code></td>
 680                         <td class="cell85">specifies a base classname or a delegator. In 'dump' mode it is used as a delegator to forward methods. It can be used as '&lt;name&gt;::' for base forwarding, or '&lt;name&gt;-&gt;|.' for composition. Using &quot;_&quot; means that a default bodies with default return values are dumped.</td>
 681           </tr>
 682           <tr>
 683             <td class="cell15"><code>-t &lt;name&gt;</code></td>
 684                         <td class="cell85">specifies an UNOIDL type name, e.g. com.sun.star.text.XText (can be used more than once).</td>
 685           </tr>
 686           <tr>
 687             <td class="cell15"><code>-p &lt;protocol:cmd(s)&gt;</code></td>
 688                         <td class="cell85">specifies an add-on protocol name and the corresponding command names, where the commands are a ',' separated list of unique commands. This option is only valid for add-ons.</td>
 689           </tr>
 690           <tr>
 691             <td class="cell15"><code>-V, --version</code></td>
 692                         <td class="cell85">print version number and exit.</td>
 693           </tr>
 694           <tr>
 695             <td class="cell15"><code>-h, --help</code></td>
 696                         <td class="cell85">print this help and exit.</td>
 697           </tr>
 698                   </table>
 699                   </p>
 700                   </td>
 701                 </tr>
 702       </table>
 703     </td>
 704     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 705   </tr>
 706   <tr>
 707     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 708   </tr>
 709   <tr>
 710     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 711     <td>
 712       <table class="table2">
 713         <tr>
 714                   <td colspan="2" class="head1"><a name="regcomp"/>regcomp</td>
 715                   <td align="right">
 716                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 717                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 718                   </td>
 719         </tr>
 720                 <tr>
 721                   <td colspan="3">
 722                   <p>'regcomp' is a tool to register|revoke external UNO components
 723                   into|from a registry which is used in a UNO environment.</p>
 724                   <p class="head2">Usage:</p>
 725                   <blockquote>
 726                   <b><code>regcomp -revoke [-br&lt;registryfile&gt;] -r &lt;registryfile&gt; -c &lt;locationUrl&gt;[-l&lt;componentLoaderName&gt;]</code></b>
 727                   </blockquote>
 728                   <p class="head2">Options:</p>
 729                   <p>
 730                   <table class="table4">
 731                   <tr>
 732                         <td class="cell15"><code>-register|revoke</code></td>
 733                         <td class="cell85">register means that the components will be
 734                         installed and revoke means that they will be removed.</td>
 735                   </tr>
 736                   <tr>
 737                         <td class="cell15"><code>-br&lt;registryfile&gt;</code></td>
 738                         <td class="cell85">the name of the registry used for bootstrapping
 739                         the program. If the bootstrap registry is specified and has the same
 740                         name as the registration registry, '-r' is optional.</td>
 741                   </tr>
 742                   <tr>
 743                         <td class="cell15"><code>-r&lt;registryfile&gt;</code></td>
 744                         <td class="cell85">the name of the registry (will be created if
 745                         it does not exist) where the component should be registered.</td>
 746                   </tr>
 747                   <tr>
 748                         <td class="cell15"><code>-c&lt;locationUrls&gt;</code></td>
 749                         <td class="cell85">the location of a component (DLL, Class name,
 750                         or an url of a jar file) or a list of urls separated by ';'s. Note
 751                         that, if a list of urls is specified, the components must all need
 752                         the same loader.</td>
 753                   </tr>
 754                   <tr>
 755                         <td class="cell15"><code>-l&lt;componentLoaderName&gt;</code></td>
 756                         <td class="cell85">the name of the needed loader, if no loader is
 757                         specified the 'com.sun.star.loader.SharedLibrary' is used. Supported
 758                         loaders: 'com.sun.star.loader.SharedLibrary' |
 759                         'com.sun.star.loader.Java'.</td>
 760                   </tr>
 761                   </table>
 762                   </p>
 763                   </td>
 764                 </tr>
 765       </table>
 766     </td>
 767     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 768   </tr>
 769   <tr>
 770     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 771   </tr>
 772   <tr>
 773     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 774     <td>
 775       <table class="table2">
 776         <tr>
 777                   <td colspan="2" class="head1"><a name="regmerge"/>regmerge</td>
 778                   <td align="right">
 779                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 780                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 781                   </td>
 782         </tr>
 783                 <tr>
 784                   <td colspan="3">
 785                   <p>'regmerge' is a small tool to merge different registry files under a
 786                   specified key into another registry file. If a value already exists in
 787                   the target file the value is overwritten by the value of the source
 788                   file.</p>
 789                   <p class="head2">Usage:</p>
 790                   <blockquote>
 791                   <b><code>regmerge [-v|--verbose] &lt;mergefile&gt; &lt;mergeKeyName&gt; &lt;regfile_1&gt; ... &lt;regfile_n&gt;</code></b>
 792                   </blockquote>
 793                   <p class="head2">Options:</p>
 794                   <p>
 795                   <table class="table4">
 796                   <tr>
 797             <td class="cell15"><code>-v|--verbose</code></td>
 798                         <td class="cell85">verbose output on stdout.</td>
 799           </tr>
 800                   <tr>
 801             <td class="cell15"><code>&lt;mergefile&gt;</code></td>
 802                         <td class="cell85">specifies the merged registry file. If this file
 803                         doesn't exist, it is created.</td>
 804                   </tr>
 805                   <tr>
 806             <td class="cell15"><code>&lt;mergeKeyName&gt;</code></td>
 807                         <td class="cell85">specifies the merge key, everything is merged
 808                         under this key. If this key doesn't exist, it is created.</td>
 809           </tr>
 810                   <tr>
 811             <td class="cell15"><code>&lt;regfile_1&gt; ... &lt;regfile_n&gt;</code></td>
 812                         <td class="cell85">specifies one or more registry files that are
 813                         merged.</td>
 814                   </tr>
 815                   </table>
 816                   </p>
 817                   </td>
 818                 </tr>
 819       </table>
 820     </td>
 821     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 822   </tr>
 823   <tr>
 824     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 825   </tr>
 826   <tr>
 827     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 828     <td>
 829       <table class="table2">
 830         <tr>
 831                   <td colspan="2" class="head1"><a name="regview"/>regview</td>
 832                   <td align="right">
 833                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 834                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 835                   </td>
 836         </tr>
 837                 <tr>
 838                   <td colspan="3">
 839                   <p>'regview' is a tool to show the contents of a registry file. The tool
 840                   dumps the hierarchical structure and the values of the nodes in a human
 841                   readable manner to stdout.</p>
 842                   <p class="head2">Usage:</p>
 843                   <blockquote>
 844                   <b><code>regview &lt;registryfile&gt; [&lt;keyName&gt;]</code></b>
 845                   </blockquote>
 846                   <p class="head2">Options:</p>
 847                   <p>
 848                   <table class="table4">
 849                   <tr>
 850             <td class="cell15">-br&lt;registryfile&gt;</code></td>
 851                         <td class="cell85">the name of the registry whose contents should
 852                         be viewed.</td>
 853           </tr>
 854                   <tr>
 855             <td class="cell15"><code>&lt;keyName&gt;</code></td>
 856                         <td class="cell85">the name of a registry key. The name must be
 857                         fully qualified; for example, '/' means the root key and
 858                         '/UCR/com/sun/star/uno/XInterface' shows the type specification of the
 859                         XInterface type. If no key is specified, the tool dumps the whole
 860                         content of the registry file.</td>
 861                   </tr>
 862                   </table>
 863                   </p>
 864                   </td>
 865                 </tr>
 866       </table>
 867     </td>
 868     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 869   </tr>
 870   <tr>
 871     <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
 872   </tr>
 873   <tr>
 874     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 875     <td>
 876       <table class="table2">
 877         <tr>
 878                   <td colspan="2" class="head1"><a name="autodoc"/>autodoc</td>
 879                   <td align="right">
 880                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 881                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 882                   </td>
 883         </tr>
 884                 <tr>
 885                   <td colspan="3">
 886                   <p>The 'autodoc' tool is used for creating javadoc-like documentation
 887                   from C++ and UNOIDL source code.</p>
 888                   <p>There are some conventions to follow when documenting C++- or
 889                   UNOIDL-sourcecode. See also the <a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/AppendixB/IDL_Documentation_Guidelines" title="link to the UNOIDL Documentation Guidelines">UNOIDL Documentation Guidelines</a>.<br>
 890           If you are not familiar with these, but do know javadoc: For simple C++
 891                   sourcecode documentation, using javadoc-style comments will work.</p>
 892                   <p class="head2">Usage:</p>
 893                   <blockquote>
 894                   <b><code>autodoc [ -v &lt;VerboseNr&gt; ] [ -name "&lt;TitleForTheDocu&gt;" ] -html &lt;OutputDirectory&gt; -lg &lt;SourcecodeLanguage&gt;<br>
 895           { [ -p &lt;ProjectName&gt; &lt;ProjectRootDirectory&gt; ] &nbsp;-t &lt;SourceTree&gt;* | -d &lt;SourceDirectory&gt;* | -f &lt;SourceFile&gt;* }*</code></b>
 896                   </blockquote>
 897                   <p class="head2">Options:</p>
 898                   <p>
 899                   <table width="100%" border="1" cellpadding="4" cellspacing="0">
 900                   <tr>
 901             <td class="cell15"><code>-v &lt;VerboseNr&gt;</code></td>
 902             <td class="cell85">&lt;VerboseNr&gt; == 5 displays the parsed source
 903                     code tokens, so you can locate which piece caused an parsing error.<br>
 904             &lt;VerboseNr&gt; == 2 displays not only the parsed source code,
 905                     but also the comments.<br><br>
 906                     This option must be the first one, if it is used.</td>
 907           </tr>
 908           <tr>
 909             <td class="cell15"><code>-name "&lt;Title&gt;"</code></td>
 910                     <td class="cell85">&lt;Title&gt; occurs as the title of the start
 911                     page of the HTML output. If this option is omitted, a default title is
 912                     created.</td>
 913           </tr>
 914           <tr>
 915             <td class="cell15"><code>-html &lt;OutputDirectory&gt;</code></td>
 916             <td class="cell85">specifies the root directory where the HTML output
 917                     is created.<br>
 918             Autodoc does not remove old files there, though it overwrites them.</td>
 919           </tr>
 920           <tr>
 921             <td class="cell15"><code>-lg &lt;SourcecodeLanguage&gt;</code></td>
 922                     <td class="cell85">Possible values are: c++ | idl.<br><br>
 923             This also specifies which files will be parsed: &quot;c++&quot; parses
 924                         all files with the endings .hxx and .h, &quot;idl&quot; parses all
 925                         files with the ending '.idl' .<br>
 926             To change this behaviour, see at option <code>-f</code>.</td>
 927           </tr>
 928                   <tr>
 929             <td class="cell15"><code>-p &lt;ProjectName&gt; &lt;ProjectDirectory&gt;</code></td>
 930                     <td class="cell85">this option can be used to divide large code
 931                     bases into different projects.<br>
 932             &lt;ProjectName&gt; gives a user-defined name for the project.<br>
 933             &lt;ProjectDirectory&gt; is the root to which all paths, given with the
 934                     following options <code>-t,-d</code> and <code>-f</code>, are
 935                         relative.<br>
 936                     This option can be omitted when there are no projects and all paths in
 937                     the following options are relative to the working directory.<br><br>
 938                     The &quot;{ ... }*&quot; around the options <code>-p,-t,-d,-f</code>
 939                         indicates, that this whole block of options can be repeated, each block
 940                         starting with a new <code>-p</code>.</td>
 941           </tr>
 942           <tr>
 943             <td class="cell15"><code>-t &lt;SourceTree&gt;</code></td>
 944                     <td class="cell85">specifies that all files in the directory
 945                     &lt;SourceTree&gt; and it's subdirectories are parsed, where the file
 946                     ending matches the option <code>-lg</code>.<br>
 947             There can be given multiple directories after one <code>-t</code>
 948                         option.<br>
 949             All relative paths &nbsp;are relative to the project-rootdirectory,
 950                     given with the <code>-p</code> option.<br>
 951             </td>
 952           </tr>
 953           <tr>
 954                     <td class="cell15"><code>-d &lt;SourceDirectory&gt;</code></td>
 955             <td class="cell85">Specifies that all files in th directory
 956                     &lt;SourceDirectory&gt;, but NOT it's subdirectories, are parsed, where
 957                     the file ending matches the option <code>-lg</code>.<br>
 958             There can be multiple directories given after one <code>-d</code>
 959                         option.<br>
 960             All relative paths &nbsp;are relative to the project-rootdirectory,
 961                         given with the <code>-p</code> option.</td>
 962           </tr>
 963           <tr>
 964             <td class="cell15"><code>-f &lt;SourceFile&gt;</code></td>
 965             <td class="cell85">parses the given file. The ending does not have
 966                     to match the <code>-lg</code> option.<br>
 967             There can be multiple files given after one <code>-f</code> option.<br>
 968             All relative paths &nbsp;are relative to the project-rootdirectory,
 969                     given with the <code>-p</code> option.</td>
 970           </tr>
 971                   </table>
 972                   </p><b>Remark:</b> The sequence of options matters! Use them in the order given
 973                   in the &quot;Usage&quot;-paragraph.</p>
 974                   </td>
 975                 </tr>
 976       </table>
 977     </td>
 978     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 979   </tr>
 980   <tr>
 981     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 982   </tr>
 983   <tr>
 984     <td colspan="3">
 985       <div align="center"><p>Copyright 2009 Sun Microsystems, Inc.</p></div>
 986     </td>
 987   </tr>
 988 </table>
 989 <map name="Map">
 990   <area shape="rect" coords="10,10,80,50" href="http://www.sun.com">
 991   <area shape="rect" coords="155,65,335,85" href="../index.html">
 992 </map>
 993 </body>
 994 </html>