content/installation/index.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<head>
	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
	<TITLE></TITLE>
	<META NAME="GENERATOR" CONTENT="StarOffice 8  (Solaris Sparc)">
	<META NAME="CREATED" CONTENT="20021022;14462835">
	<META NAME="CHANGED" CONTENT="20070730;17033000">
</head>
<body LANG="de-DE" DIR="LTR">
<H1>Installation Project</H1>
<P><B>Project Owner:</B> <A HREF="mailto:ingo.schmidt@sun.com">Ingo
Schmidt</A> 
</P>
<P>The Installation project contains several different modules, that
are necessary to create OpenOffice.org installation sets. This
includes the description of the installation sets as well as the
packaging process in which the native installation sets are created.
Additionally the product definition is part of the Installation
project. Further modules are added, that contain files required for
additional functionality for the installation (Download installation
sets, language packs, Readme-Files, License-Files, ...) and for the
Office suite (extras, wizards). 
</P>
<P>The Installation project includes the following: 
</P>
<UL>
	<LI><P STYLE="margin-bottom: 0in">A platform independent description
	language in which the composition of an installed product can be
	described. This description is done in small script particles (scp),
	that can be linked in different versions to create different
	products. 
	</P>
	<LI><P STYLE="margin-bottom: 0in">Tools that analyze and link the
	script particles and create a script for each product and each
	platform. 
	</P>
	<LI><P STYLE="margin-bottom: 0in">A packaging process, that analyzes
	the product describing scripts and that creates the corresponding
	installation sets in the format of the native installer. 
	</P>
	<LI><P STYLE="margin-bottom: 0in">Source code for the setup
	executable, that can be used to start the installation process on
	the Windows platform. 
	</P>
	<LI><P STYLE="margin-bottom: 0in">NSIS code, that is used to create
	one-file download installation sets for the Windows platform. 
	</P>
	<LI><P STYLE="margin-bottom: 0in">Java code, for an Installation
	Wizard with a graphical user interface (GUI). This Wizard is
	available as preview in OpenOffice.org 2.2. 
	</P>
	<LI><P STYLE="margin-bottom: 0in">The 'extras'. A collection of all
	kinds of (binary) files that are needed by various parts of
	OpenOffice.org. 
	</P>
</UL>
<P>Beginning with OpenOffice.org 2.0 the installation process of
OpenOffice.org was completely changed. In the past, OpenOffice.org
used its own setup application, that was platform independent. Now
the installation is done with the platform specific installers:</P>
<UL>
	<LI><P STYLE="margin-bottom: 0in">Microsoft Installer (MSI) for
	Windows platforms</P>
	<LI><P STYLE="margin-bottom: 0in; page-break-before: always">RedHat
	Package Manager (RPM) for Linux</P>
	<LI><P>Solaris Packages (PKG) for Solaris</P>
</UL>
<P><BR><BR>
</P>
<H2>NEW: Java GUI installation wizard</H2>
<P>Beginning with the release of OpenOffice.org 2.3 a new Java GUI
installation wizard is included into the products &bdquo;OpenOffice.org
with JRE&ldquo; (Java Runtime Environment). This installation wizard
simplifies the installation on Unix platforms. The selection of the
components or the setting of the destination directory can be done
with the help of a GUI. Nevertheless the installation is still based
on native installation packages. Currently RPMs and Solaris packages
are supported by the Java GUI installer. Of course Java is a
requirement on your system, if you want to use this installation
wizard. 
</P>
<P>If you want to help creating the Java GUI installation wizard,
your help is very appreciated. It is very important, that the
installer supports more platforms and package formats than he does
today. For example Debian packages should be added soon. Furthermore
testing of this new product is very important, because a lot of
functionality is added to OpenOffice.org. Of course translation is
important, that the wizard soon supports all available OpenOffice.org
languages. 
</P>
<P>Next to a <A HREF="Java_GUI_Installer_Quick_Guide.odt">short
introduction</A> into the Java GUI installation wizard and next to
the <A HREF="Java_GUI_Installer.odt">specification</A>, there are
also installation sets of an OpenOffice.org 2.2 available, that
contain this installation wizard as preview. Please feel free to test
this new installation process. Every feedback and every help is very
appreciated. If you have downloaded this installation sets, read the
<A HREF="Java_GUI_Installer_Quick_Guide.odt">Quick Guide</A> to learn
more about the Installation Wizard. Currently installation sets are
available for the RPM installation on Linux and for the installation
of Solaris packages on Solaris Sparc and Solaris x86. 
</P>
<P>
Test the new JavaFX download installer <A HREF="testarea/install/index.html">here</A>.
</P>
<H2>ToDo List</H2>
<P>In the installation project, there are several places, where you
can help to improve OpenOffice.org. The installation project covers
the complete section from finding the files in the solver until they
are located on the user's hard disc. This means packaging of
intallation sets, supporting as many package formats as possible and
then taking care of a successful and convenient installation. If you
have more ideas, than listed below, please do not hesitate to contact
us. 
</P>
<UL>
	<LI><P STYLE="margin-bottom: 0in">The new Java GUI installation will
	be part of OpenOffice.org 2.3 with JRE. For this installation
	wizard, help is required for the following tasks: 
	</P>
	<UL>
		<LI><P STYLE="margin-bottom: 0in">Adding support of additional
		package formats to the Java GUI Installation Wizard.</P>
		<LI><P STYLE="margin-bottom: 0in">Testing of the new Java GUI
		Installation Wizard, so that we can introduce it with only few
		problems left.</P>
	</UL>
	<LI><P>It is also always important, to increase the number of
	platforms, on which OpenOffice.org 2.x can be installed natively.
	Alternatively it can be useful to offer alternative installation
	processes, if native installers are not desired. 
	</P>
	<LI><P>Sometimes it is necessary to think about new processes during
	packaging. Is it an alternative to use DeltaRPMs for smaller and
	easier update packages on Linux (RPM)? And how about using &quot;WIX&quot;
	(http://sourceforge.net/projects/wix), to create the OpenOffice.org
	msi database? 
	</P>
	<LI><P>We are always looking for feedback, to be better informed
	about your packaging and installation experience. If you want to
	give us your feedback, please do not hesitate to do so. 
	</P>
</UL>
<P><BR><BR>
</P>
<H2>Documentation and Resources</H2><A NAME="doc"></A>
<TABLE WIDTH=100% BORDER=0 CELLPADDING=4 CELLSPACING=0 BGCOLOR="#ffffff">
	<COL WIDTH=64*>
	<COL WIDTH=162*>
	<COL WIDTH=31*>
	<TR>
		<TD COLSPAN=3 WIDTH=100% BGCOLOR="#00315a">
			<P ALIGN=CENTER><FONT COLOR="#ffffff"><FONT FACE="arial, helvetica"><FONT SIZE=2><B>Documentation
			and Resources</B></FONT></FONT></FONT></P>
		</TD>
	</TR>
	<TR>
		<TH WIDTH=25% BGCOLOR="#99ccff">
			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="arial, helvetica"><FONT SIZE=2><B>Document</B></FONT></FONT></FONT></P>
		</TH>
		<TH WIDTH=63% BGCOLOR="#99ccff">
			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="arial, helvetica"><FONT SIZE=2><B>Summary</B></FONT></FONT></FONT></P>
		</TH>
		<TH WIDTH=12% BGCOLOR="#99ccff">
			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="arial, helvetica"><FONT SIZE=2><B>Format
			and Size</B></FONT></FONT></FONT></P>
		</TH>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=25% BGCOLOR="#f0f0f0">
			<P><A HREF="how_to_repackage_oo.html">Howto repackage OOo</A></P>
		</TD>
		<TD WIDTH=63% BGCOLOR="#f0f0f0">
			<P>This document describe how to create a standard unix package
			out of an OpenOffice.org installation set</P>
		</TD>
		<TD WIDTH=12% BGCOLOR="#f0f0f0">
			<P>HTML, ca.&nbsp;8 kb</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=25% BGCOLOR="#f0f0f0">
			<P><A HREF="how_to_repackage_so.html">Howto repackage SO/SS</A></P>
		</TD>
		<TD WIDTH=63% BGCOLOR="#f0f0f0">
			<P>This document describe how to create a standard unix package
			out of a StarOffice/StarSuite installation set</P>
		</TD>
		<TD WIDTH=12% BGCOLOR="#f0f0f0">
			<P>HTML, ca.&nbsp;11 kb</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=25% BGCOLOR="#f0f0f0">
			<P><A HREF="how_to_create_native_installer.html">Howto Create
			Native Installer</A></P>
		</TD>
		<TD WIDTH=63% BGCOLOR="#f0f0f0">
			<P>This document describes how to create native installation sets
			for OpenOffice.org 2.0.</P>
			<P>The EPM patch can be downloaded <A HREF="epm-3.7.patch">here</A>.</P>
		</TD>
		<TD WIDTH=12% BGCOLOR="#f0f0f0">
			<P>HTML, ca. 11 kb</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=25% BGCOLOR="#f0f0f0">
			<P><A HREF="01RESPONSE_SO52_final_rev2.pdf">01RESPONSE_SO52_final_rev2.pdf</A></P>
		</TD>
		<TD WIDTH=63% BGCOLOR="#f0f0f0">
			<P>This document describe how to install OpenOffice.org 1.x
			without any user interaction via a response file</P>
		</TD>
		<TD WIDTH=12% BGCOLOR="#f0f0f0">
			<P>PDF, ca.&nbsp;244 kb</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=25% BGCOLOR="#f0f0f0">
			<P><A HREF="Java_GUI_Installer_Quick_Guide.odt">Java GUI Installer
			Quick Guide</A></P>
		</TD>
		<TD WIDTH=63% BGCOLOR="#f0f0f0">
			<P>The Java GUI Installer Quick Guide shortly describes the
			advantages and the usage of the new Java GUI Installer</P>
		</TD>
		<TD WIDTH=12% BGCOLOR="#f0f0f0">
			<P>HTML, ca.&nbsp;11 kb</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=25% BGCOLOR="#f0f0f0">
			<P><A HREF="Java_GUI_Installer.odt">Java GUI Installer
			Specification</A></P>
		</TD>
		<TD WIDTH=63% BGCOLOR="#f0f0f0">
			<P>The specification of the Java GUI Installer. Not final yet.</P>
		</TD>
		<TD WIDTH=12% BGCOLOR="#f0f0f0">
			<P>HTML, ca.&nbsp;11 kb</P>
		</TD>
	</TR>
</TABLE>
<P><BR><BR>
</P>
<H2>Installation CVS Modules</H2>
<P STYLE="margin-bottom: 0in"><BR>
</P>
<TABLE WIDTH=100% BORDER=0 CELLPADDING=4 CELLSPACING=0 BGCOLOR="#ffffff">
	<COL WIDTH=44*>
	<COL WIDTH=212*>
	<TR>
		<TD COLSPAN=2 WIDTH=100% BGCOLOR="#00315a">
			<P ALIGN=CENTER><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Modules
			in Installation Project</B> </FONT></FONT></FONT>
			</P>
		</TD>
	</TR>
	<TR>
		<TH WIDTH=17% BGCOLOR="#99ccff">
			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Module
			</B></FONT></FONT></FONT>
			</P>
		</TH>
		<TH WIDTH=83% BGCOLOR="#99ccff">
			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Function
			</B></FONT></FONT></FONT>
			</P>
		</TH>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=17% BGCOLOR="#f0f0f0">
			<P><CODE>scp2</CODE></P>
		</TD>
		<TD WIDTH=83% BGCOLOR="#f0f0f0">
			<P>The module scp2 contains the script particle, which can be used
			to define installation set. Usually a <CODE>.scp</CODE> source
			file summarizes all script objects which are necessary for special
			functionality. The individual <CODE>scp</CODE> files can be merged
			into different installation scripts during the link processes. For
			a description of the script language in the scp2-project <A HREF="How_to_scp_in_ooo.html">click
			here</A>. 
			</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=17% BGCOLOR="#f0f0f0">
			<P><CODE>solenv</CODE></P>
		</TD>
		<TD WIDTH=83% BGCOLOR="#f0f0f0">
			<P>The module solenv contains the code, that is required for
			creating setup scripts from the script particles defined in scp2
			and also the code that is required to create native installation
			sets from the setup scripts.</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=17% BGCOLOR="#f0f0f0">
			<P><CODE>instsetoo_native</CODE></P>
		</TD>
		<TD WIDTH=83% BGCOLOR="#f0f0f0">
			<P>instsetoo_native is the module, in which the products are
			defined and in which the installation sets are created. 
			</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=17% BGCOLOR="#f0f0f0">
			<P><CODE>setup_native</CODE></P>
		</TD>
		<TD WIDTH=83% BGCOLOR="#f0f0f0">
			<P>A module for native installer specific code. This includes for
			Windows the Windows Installer custom actions and the NSIS code for
			download installation sets. For Unixes this module contains
			different shellscripts, that are required for download
			installation sets or for the installation of language packs.</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=17% BGCOLOR="#f0f0f0">
			<P><CODE>desktop</CODE></P>
		</TD>
		<TD WIDTH=83% BGCOLOR="#f0f0f0">
			<P>The desktop module contains the implementation of the setup
			executable for the Windows platform. The setup.exe is used to
			search for the Windows Installer service, install this service if
			necessary and start the installation with the correct language.
			The code for the setup executable is located in the directory
			desktop/win32/source/setup . 
			</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=17% BGCOLOR="#f0f0f0">
			<P><CODE>readlicense</CODE></P>
		</TD>
		<TD WIDTH=83% BGCOLOR="#f0f0f0">
			<P>Readme and license files. 
			</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=17% BGCOLOR="#f0f0f0">
			<P><CODE>extras</CODE></P>
		</TD>
		<TD WIDTH=83% BGCOLOR="#f0f0f0">
			<P>Contains all non-code files that are vital for OpenOffice.org
			to run properly. 
			</P>
			<UL>
				<LI><P STYLE="margin-bottom: 0in"><CODE>autotext</CODE> contains
				text blocks that are used by various wizards. 
				</P>
				<LI><P STYLE="margin-bottom: 0in"><CODE>database</CODE> contains
				the bibliography database of OpenOffice.org. 
				</P>
				<LI><P STYLE="margin-bottom: 0in"><CODE>gallery</CODE> contains
				clipart that is needed by OpenOffice.org's main functionality. 
				</P>
				<LI><P STYLE="margin-bottom: 0in"><CODE>misc_config</CODE> holds
				miscellanious preferences files. 
				</P>
				<LI><P STYLE="margin-bottom: 0in">The <CODE>palettes</CODE> of
				OpenOffice (colors, gradients, etc...) are found in this module. 
				</P>
				<LI><P STYLE="margin-bottom: 0in">Files responsible for the OS
				file type recognition are found within <CODE>shellnew.</CODE> 
				</P>
				<LI><P STYLE="margin-bottom: 0in">The symbols of OpenOffice.org
				(toolbox icons) are found in this module. 
				</P>
				<LI><P STYLE="margin-bottom: 0in">document <CODE>templates</CODE>
				that are needed for the wizards are found here. 
				</P>
				<LI><P>User dictionary are stored in <CODE>wordbook</CODE>. 
				</P>
			</UL>
			<P>Files not vital for OpenOffice.org's main functionality like
			sample documents, other document templates and additional clipart
			are not stored in the module 'extras'. They can be copied right
			out of a StarOffice installation. However it may be possible to
			set up dedicated sub modules if commiters wish to contribute
			examples of these file types. 
			</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=17% BGCOLOR="#f0f0f0">
			<P><CODE>wizards</CODE></P>
		</TD>
		<TD WIDTH=83% BGCOLOR="#f0f0f0">
			<P>Basic macros and libraries for the autopilots such as the
			wizard for importing foreign file type documents. 
			</P>
		</TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=17% BGCOLOR="#f0f0f0">
			<P><CODE>javainstaller2</CODE></P>
		</TD>
		<TD WIDTH=83% BGCOLOR="#f0f0f0">
			<P>The module javainstaller2 contains the code for a Java GUI
			installation wizard. This wizard is available in a preview in
			OpenOffice.org 2.2. It is planned to be official part of
			OpenOffice.org in version 2.3. The installation wizard simplifies
			the installation process for platforms, on which no GUI installer
			is available. A quick guide to the Java GUI installer can be found
			at <A HREF="Java_GUI_Installer_Quick_Guide.odt">Java GUI Installer
			Quick Guide</A>. The specification of the Java GUI installation
			wizard is also available: <A HREF="Java_GUI_Installer.odt">Java
			GUI Installer</A>. 
			</P>
		</TD>
	</TR>
</TABLE>
<P><BR><BR>
</P>
<H2>Proposals</H2>
<TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=0 BGCOLOR="#ffffff">
	<COL WIDTH=95*>
	<COL WIDTH=96*>
	<COL WIDTH=59*>
	<COL WIDTH=6*>
	<TR>
		<TD COLSPAN=4 WIDTH=100% BGCOLOR="#00315a">
			<P ALIGN=CENTER><FONT COLOR="#ffffff"><!-- 1. row: "Documentation"
		100% with
	 --><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Proposals<!-- 2. row: "Title" & "Description" & "Author"
		40/40/20% for every column
	 -->
			</B></FONT></FONT></FONT>
			</P>
		</TD>
	</TR>
	<TR>
		<TD WIDTH=37% BGCOLOR="#99ccff">
			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Title
			</B></FONT></FONT></FONT>
			</P>
		</TD>
		<TD WIDTH=38% BGCOLOR="#99ccff">
			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Description
			</B></FONT></FONT></FONT>
			</P>
		</TD>
		<TD WIDTH=23% BGCOLOR="#99ccff">
			<P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Author<!-- 3. row: first content line
    	dialog proposal
	 --><!-- 4. row: second content line
    	system integration
	 --><!-- Standard_Printer --><!-- HelpAgent --><!-- Setup Features -->
			</B></FONT></FONT></FONT>
			</P>
		</TD>
		<TD WIDTH=2% VALIGN=TOP></TD>
	</TR>
	<TR VALIGN=TOP>
		<TD WIDTH=37% BGCOLOR="#f0f0f0">
			<P ALIGN=LEFT><BR>
			</P>
		</TD>
		<TD WIDTH=38% BGCOLOR="#f0f0f0">
			<P ALIGN=LEFT><BR>
			</P>
		</TD>
		<TD WIDTH=23% BGCOLOR="#f0f0f0"></TD>
		<TD WIDTH=2%></TD>
	</TR>
</TABLE>
<P><BR><BR>
</P>
</body>
</HTML>