INTEGRATION: CWS jsc20 (1.20.76); FILE MERGED

2008/01/08 15:35:48 jsc 1.20.76.1: #i82046# adapt DevGuide links to wiki

1 files changed, 4 insertions, 98 deletions

diff --git a/odk/docs/tools.html b/odk/docs/tools.html
index 289f7699f497..ee92a4d51b7b 100644
--- a/odk/docs/tools.html
+++ b/odk/docs/tools.html
@@ -45,12 +45,6 @@
             </tr>
             <tr valign="top">
               <td class="content3"><img src="images/arrow-1.gif"></td>
-              <td><a href="#pkgchk"  title="link to the pkgchk tool description">pkgchk</a></td>
-              <td class="content87">The old UNO package deployment tool. It also comes 
-			  with the office installation but it is <b><i>deprecated</i></b>.</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 
 			  provide configured (deployed) or single components. This tool
@@ -150,7 +144,7 @@
 		  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 
-		  Developer's Guide: <a href="./DevelopersGuide/Components/Components.xhtml#1_9_1_UNO_Package_Installation_Using_unopkg" title="link to &quot;UNO Package Installation Using unopkg&quot; chapter in the Developer's Guide">4.9.1 UNO Package Installation Using <i>unopkg</i></a>.</p>
+		  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>
 		  <p><b>Note:</b> This tool works only in the <i>&lt;office&gt;/program</i> 
 		  directory!</p>
 		  <p class="head2">Usage:</p>
@@ -234,94 +228,6 @@
 		</tr>
       </table>
     </td>
-    <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
-  </tr>
-  <tr> 
-    <td colspan="3"><img class="line" src="images/sdk_line-2.gif"></td>
-  </tr>
-  <tr>
-    <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
-    <td> 
-      <table class="table2">
-        <tr> 
-		  <td colspan="2" class="head1"><a name="pkgchk"/>pkgchk</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>
-		  <td colspan="3">
-		  <p>'pkgchk' is <u><b>deprecated</b></u> and you should use the new 
-		  <a href="#unopkg" title="link to the new unopkg tool">'unopkg'</a> 
-		  deployment tool.</p>
-		  <p>'pkgchk' 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) and 
-          StarOffice 8 Basic libraries as zip package. More detailed information 
-		  concerning deplyoment can be find in the Developer's Guide: <a href="./DevelopersGuide/Components/Components.xhtml#1_9_Deployment_Options_for_Components" title="link into the &quot;Deployment Options for Components&quot; chapter in the Developer's Guide">4.9 Deployment Options for Components</a>.</p>
-		  <p><b>Note:</b> This tool works only in the <i>&lt;office&gt;/program</i> 
-		  directory!</p>
-		  <p class="head2">Usage:</p>
-		  <blockquote>
-		  <b><code>pkgchk &lt;options&gt; [package1 package2 ... ]</code></b>
-		  </blockquote>
-		  <p class="head2">Options:</p>
-		  <p>
-		  <table class="table4">
-		  <tr>
-            <td class="cell15"><code>-s, --shared|revoke</code></td>
-            <td class="cell85">check/install shared components; default: 
-			user</td>
-		  </tr>
-		  <tr>
-            <td class="cell15"><code>-r, --renewal</code></td>
-			<td class="cell85">re-install all packages (useful for cache 
-			inconsistencies).</td>
-          </tr>
-		  <tr>
-            <td class="cell15"><code>-f, --force-overwrite</code></td>
-			<td class="cell85">force overwrite existing packages when copying 
-			from command line.</td>
-          </tr>
-          <tr>
-            <td class="cell15"><code>-v, --verbose</code></td>
-			<td class="cell85">verbose output to stdout.</td>
-          </tr>
-          <tr>
-            <td class="cell15"><code>-l, --log &lt;file&gt;</code></td>
-			<td class="cell85">custom log file; default: 
-			<i>&lt;cache&gt/log.txt.</i></td>
-          </tr>
-          <tr>
-            <td class="cell15"><code>--strict_error_handling</code></td>
-			<td class="cell85">break process immediately if errors occur.</td>
-          </tr>
-          <tr>
-            <td class="cell15"><code>--supersede_basic_libs</code></td>
-			<td class="cell85">overwrite existing basic library entries of 
-			same name.</td>
-          </tr>
-          <tr>
-            <td class="cell15"><code>--check_unorc_only</code></td>
-			<td class="cell85">check/patch only the unorc (Unix), uni.ini 
-			(Windows).</td>
-          </tr>
-          <tr>
-            <td class="cell15"><code>--no_unorc_patch</code></td>
-			<td class="cell85">don't touch unorc (Unix), uni.ini (Windows).</td>
-          </tr>
-		  <tr>
-            <td class="cell15"><code>-h, --help</code></td>
-			<td class="cell85">print a command line help to stdout.</td>
-          </tr>
-          </table>
-          </p>
-		  </td>
-		</tr>  
-      </table>
-    </td>
 	<td class="content1"><img class="nothing8" src="images/nada.gif"></td>
   </tr>
   <tr> 
@@ -446,7 +352,7 @@
 		  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="DevelopersGuide/Appendix/IDLSyntax/IDLSyntax.xhtml#1_UNOIDL_Syntax_Specification" title="link to the &quot;UNOIDL Syntax Specification&quot; chapter in the Developer's Guide">here</a>.</p>
+		  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>
 		  <p class="head2">Usage:</p>
 		  <blockquote>
 		  <b><code>idlc [-options] file_1 ... file_n | @&lt;filename&gt;</code></b>
@@ -1158,7 +1064,7 @@ types the specified types depend on.</p>
 		  <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 
-		  UNOIDL-sourcecode. See also the <a href="DevelopersGuide/Appendix/IDLDocumentationGuide/IDLDocumentationGuide.xhtml#1_IDL_Documentation_Guidelines" title="link to the UNOIDL Documentation Guidelines">UNOIDL Documentation Guidelines</a>.<br>
+		  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>
           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>
@@ -1254,7 +1160,7 @@ types the specified types depend on.</p>
   </tr>
   <tr> 
     <td colspan="3"> 
-      <div align="center"><p>Copyright 2005 Sun Microsystems, Inc.</p></div>
+      <div align="center"><p>Copyright 2008 Sun Microsystems, Inc.</p></div>
     </td>
   </tr>
 </table>