You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by ks...@apache.org on 2011/11/26 00:40:49 UTC
svn commit: r1206378 - in
/incubator/ooo/ooo-site/trunk/content/installation/proposals: ./
netinstall.html setup_feature/ setup_feature/setup_features60_proposal.html
temp/ ui/ ui/flowchart.sxd ui/setupui.sxw
Author: kschenk
Date: Fri Nov 25 23:40:48 2011
New Revision: 1206378
URL: http://svn.apache.org/viewvc?rev=1206378&view=rev
Log:
kls-- updating installation/proposals
Added:
incubator/ooo/ooo-site/trunk/content/installation/proposals/
incubator/ooo/ooo-site/trunk/content/installation/proposals/netinstall.html (with props)
incubator/ooo/ooo-site/trunk/content/installation/proposals/setup_feature/
incubator/ooo/ooo-site/trunk/content/installation/proposals/setup_feature/setup_features60_proposal.html (with props)
incubator/ooo/ooo-site/trunk/content/installation/proposals/temp/
incubator/ooo/ooo-site/trunk/content/installation/proposals/ui/
incubator/ooo/ooo-site/trunk/content/installation/proposals/ui/flowchart.sxd (with props)
incubator/ooo/ooo-site/trunk/content/installation/proposals/ui/setupui.sxw (with props)
Added: incubator/ooo/ooo-site/trunk/content/installation/proposals/netinstall.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/proposals/netinstall.html?rev=1206378&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/proposals/netinstall.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/proposals/netinstall.html Fri Nov 25 23:40:48 2011
@@ -0,0 +1,177 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="AUTHOR" CONTENT="Dirk Völzke">
+ <META NAME="CREATED" CONTENT="20020114;11420500">
+ <META NAME="CHANGEDBY" CONTENT="Dirk Völzke">
+ <META NAME="CHANGED" CONTENT="20020116;15265600">
+</HEAD>
+<BODY LANG="de-DE">
+<H1 LANG="en-US" CLASS="western">Setup network installation</H1>
+<H2 LANG="en-US" CLASS="western">abstract</H2>
+<P LANG="en-US" CLASS="western">multi user operating systems become
+more important today so it would be good if our setup program would
+offer better support for these operating systems.</P>
+<H2 LANG="en-US" CLASS="western">Installation models</H2>
+<P LANG="en-US" CLASS="western">For better support of the multi user
+systems we will differentiate between three installation models.
+These models are the single user installation, the multi user
+installation and the network installation.</P>
+<H6 LANG="en-US" CLASS="western">Single user installation ( Windows
+98/ME )</H6>
+<P LANG="en-US" CLASS="western">In a single user installation the
+product will be installed in one single step on the computer of the
+user. All necessary system configuration ( like writing something
+into the registry, installing fonts, creating program groups, etc. )
+will be done for this single user. After the installation the product
+is ready for use.</P>
+<P LANG="en-US" CLASS="western">When someone else uses the product on
+this computer, he will use the same (user) configuration.</P>
+<H6 LANG="en-US" CLASS="western">Multi user installation (Windows NT,
+2000, XP, UNIX)</H6>
+<P LANG="en-US" CLASS="western">The system administrator installs the
+product into a common location on the computer which can be accessed
+by every user. During this installation, most of the system
+configuration will be done like font installation or file types
+registration or the creation of program groups and links to the
+program files etc. for all users.</P>
+<P LANG="en-US" CLASS="western">Before a user can use the product for
+the first time, he has to run the user installation to copy all the
+user specific data into a user specific folder. When he tries to
+start the product without running the user installation first, the
+user installation will be started by the product automatically. When
+the user installation has finished, the product will be started
+again.</P>
+<P LANG="en-US" CLASS="western">The difference to the single user
+installation is that different users of the same computer share the
+same product installation but use their own user data.</P>
+<H6 LANG="en-US" CLASS="western">Network installation (all OS, setup
+– net)</H6>
+<P LANG="en-US" CLASS="western">The system administrator installs the
+complete product on a network volume that is accessible for all
+users. No system specific or user specific installation will be done.
+All files and information necessary for user installation (e.g. fonts
+) will be stored beside the product so they are available later for
+the user installation.</P>
+<P LANG="en-US" CLASS="western">A user who wants to use the product
+has to start the setup program in the network installation to install
+the user specific data on his workstation. This will install the
+fonts, register the file types, etc. After this installation the
+user can use the product. When the user tries to start the product
+without running the user installation first, the user installation
+will be started by the product automatically. When the user
+installation has finished, the product will be started again.</P>
+<P LANG="en-US" CLASS="western">In difference to the multi user
+installation the network installation doesn't make any system
+configuration nor installs any system files on the user's computer.
+This will be done later when the user runs the user installation.</P>
+<H2 LANG="en-US" CLASS="western">Typical layout of an installation</H2>
+<P LANG="en-US" CLASS="western">We will always use the network
+installation as a base for all three kinds of installation. The
+network installation will be done using the default directories
+appropriate for the operating system. Optional you can choose another
+directory if you want.
+</P>
+<P LANG="en-US" CLASS="western"><B>Windows NT / 2000 / XP</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt"><program
+files>\<product name>\...</FONT></FONT></P>
+<P LANG="en-US" CLASS="western"><B>UNIX / Linux</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt">/opt/<product
+name></FONT></FONT></P>
+<P LANG="en-US" CLASS="western">The user installation uses the system
+default directories, too. These directories are:</P>
+<P LANG="en-US" CLASS="western"><B>Windows NT / 2000 / XP</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt"><document
+and settings>\<user>\<local settings>\Sun
+Microsystems\<product name>\...</FONT></FONT></P>
+<P LANG="en-US" CLASS="western"><B>UNIX / Linux</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt">$home/.<product
+name></FONT></FONT></P>
+<P LANG="en-US" CLASS="western">When performing a single user
+installation, both installations will be done into the same base
+directory the user chooses. This could look like:</P>
+<P LANG="en-US" CLASS="western"><B>Windows NT / 2000 / XP</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt"><program
+files>\<product name>\...<BR><program files>\<product
+name>\user\...</FONT></FONT></P>
+<P LANG="en-US" CLASS="western"><B>UNIX / Linux</B></P>
+<P LANG="en-US" CLASS="western"><FONT SIZE=2 STYLE="font-size: 9pt"><FONT FACE="Courier, monospace">/$home/<product
+name></FONT></FONT><BR><FONT SIZE=2 STYLE="font-size: 9pt"><FONT FACE="Courier, monospace">/$home/<product
+name>/user</FONT></FONT></P>
+<H6 LANG="en-US" CLASS="western">Starting the product after a
+multiuser or network installation</H6>
+<P LANG="en-US" CLASS="western">The product has to check on startup,
+whether the user has already done a user installation. To do this
+the product has to read its version key from the <B>bootstrap.ini</B><SPAN STYLE="font-weight: medium">
+file which should reside next to the executable of the product. In
+the next step the product looks for this key in the file </SPAN><B>sversion.ini
+/ .sversionrc</B><SPAN STYLE="font-weight: medium"> ( this file is
+located in the <documents and settings>\<user>\<application
+data> directory for Windows and in the $home directory for UNIX /
+Linux ). There a three possible scenarios.</SPAN></P>
+<P LANG="en-US" CLASS="western"><I>a.) The key couldn't be found in
+the sversion.ini or there is no sversion.ini</I></P>
+<P LANG="en-US" CLASS="western" STYLE="font-style: normal">When the
+key couldn't be found then probably the user hasn't done the user
+installation. Therefor the product launches the user installation and
+quits. The setup launches the product after the successful user
+installation.</P>
+<P LANG="en-US" CLASS="western"><I>b) The path behind the key is
+invalid</I></P>
+<P LANG="en-US" CLASS="western" STYLE="font-style: normal">When the
+key could be found in both file but the path behind the key in the
+sversion.ini file is wrong, then something probably went wrong,
+therefor the setup program should be started in repair mode. So the
+product launches the setup, quits and after the successful repair the
+setup launches the product again.</P>
+<P LANG="en-US" CLASS="western"><I>c) The path behind the key is
+valid</I></P>
+<P LANG="en-US" CLASS="western" STYLE="font-style: normal">The
+product launches as usual.</P>
+<H6 LANG="en-US" CLASS="western">Starting the setup program in a
+multi user or network installation</H6>
+<P LANG="en-US" CLASS="western">When the setup is started inside a
+multi user or network installation, the setup can't decide
+automatically whether it should be used to modify or repair the
+current installation or if it is used to perform a user installation
+or modify or repair a user installation.</P>
+<P LANG="en-US" CLASS="western">When the setup finds the version key
+in the sversion.ini it will present the user the option to repair or
+deinstall or modify the user installation.</P>
+<P LANG="en-US" CLASS="western">When the setup can't find the version
+key it will present the user the option to do a user installation.</P>
+<P LANG="en-US" CLASS="western">To repair or modify or deinstall the
+multi user / network installation the setup has to be called with the
+option <B>-net</B><SPAN STYLE="font-weight: medium">. For better
+access to this option the setup should install an additional link (
+or program shortcut ) in the multi user / network installation that
+starts the setup with this option. To prevent<SPAN LANG="en-US">
+unauthorized </SPAN>access to this installation, the setup could ask
+for a password the system administrator provides during installation
+and that could be stored MD5 encoded in the installation database.</SPAN></P>
+<H2 LANG="en-US" CLASS="western">Problems</H2>
+<P LANG="en-US" CLASS="western">For a network or a multi user
+installation privileged access rights might be required.</P>
+<P LANG="en-US" CLASS="western">The user installation of a network
+installation might require privileged rights for the user's
+workstation, too, for the installation of fonts etc.</P>
+<P LANG="en-US" CLASS="western">When you try to repair an
+installation, the setup doesn't know, whether it should repair the
+user or the network ( or multi user ) installation.</P>
+<P LANG="en-US" CLASS="western">When the multi user / network
+installation has changed, it might be necessary to redo the user
+installation.</P>
+<H2 LANG="en-US" CLASS="western">Questions</H2>
+<P LANG="en-US" CLASS="western">Choose the installation method
+automatically? E.g. use single user installation for Windows 98/ME
+and the multi user installation for all other Windows versions or use
+always the multi user installation ( this uses a little bit more
+space on your harddrive for the user installation data? Use the
+network installation when installing on UNIX or Linux?</P>
+<P LANG="en-US" CLASS="western" STYLE="font-weight: medium">We prefer
+always doing a multi user / network installation with an immediately
+following user installation when necessary.</P>
+</BODY>
+</HTML>
Propchange: incubator/ooo/ooo-site/trunk/content/installation/proposals/netinstall.html
------------------------------------------------------------------------------
svn:eol-style = native
Added: incubator/ooo/ooo-site/trunk/content/installation/proposals/setup_feature/setup_features60_proposal.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/proposals/setup_feature/setup_features60_proposal.html?rev=1206378&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/proposals/setup_feature/setup_features60_proposal.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/proposals/setup_feature/setup_features60_proposal.html Fri Nov 25 23:40:48 2011
@@ -0,0 +1,660 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="AUTHOR" CONTENT=" ">
+ <META NAME="CREATED" CONTENT="20001213;10454075">
+ <META NAME="CHANGEDBY" CONTENT=" ">
+ <META NAME="CHANGED" CONTENT="20010216;12114919">
+ <META NAME="SDFOOTNOTE" CONTENT=";;;;;C">
+ <STYLE>
+ <!--
+ @page { size: 21cm 29.7cm; margin: 2cm }
+ H1 { margin-bottom: 0.21cm; font-family: "Arial", sans-serif; font-size: 16pt }
+ TD P { margin-bottom: 0.21cm }
+ P { margin-bottom: 0.21cm }
+ -->
+ </STYLE>
+</HEAD>
+<BODY>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Arial, sans-serif"><FONT SIZE=4>
+Proposal for a StarOffice / OpenOffice.org 6.0 Setup Feature List</FONT></FONT></P>
+<P ALIGN=CENTER>Version 1, 02/16/2001,
+<A HREF="mailto:Leyla.Schroeder@germany.sun.com">Leyla.Schroeder@germany.sun.com</A></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">Priorities:</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">1 – Must</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">2 – Should</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">3 - Can / Nice to
+have</FONT></P>
+<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000080" CELLPADDING=4 CELLSPACING=0>
+ <COL WIDTH=51*>
+ <COL WIDTH=161*>
+ <COL WIDTH=44*>
+ <THEAD>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Installation in General</H1>
+ </TD>
+ </TR>
+ </THEAD>
+ <TBODY>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>CD / AutoRun</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>AutoRun should be supported under Windows</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>CD / Introscreen</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>An introduction screen should offer installation of the
+ programs that are available on the CD:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">StarOffice / OpenOffice.org
+ 6.0</P>
+ <LI><P STYLE="margin-bottom: 0cm">Acrobat Reader</P>
+ <LI><P>Java Runtime Environment</P>
+ </UL>
+ <P>Furthermore, links to additional information should be
+ offered:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">Documentation</P>
+ <LI><P>Patches (for Solaris)</P>
+ </UL>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Download / Customization</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Download packages should be generated during online-connection
+ to include only those components, the user selects in his
+ session. Therefore we need a tool to create a binary installable
+ file which includes only the required modules.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Installation package</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The different installation packages should only show those
+ files to the user, that are important to him:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">setup.exe</P>
+ <LI><P STYLE="margin-bottom: 0cm">readme.txt</P>
+ <LI><P STYLE="margin-bottom: 0cm">lincense.txt</P>
+ <LI><P STYLE="margin-bottom: 0cm">jre-(...).exe</P>
+ <LI><P>setup.inf</P>
+ </UL>
+ <P>The installation files (f_00xx) should be moved to a
+ sub-folder.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Setup / Wizard</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The setup should run in window mode, not full screen. The new
+ wizard only consists of sequenced dialog windows.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Setup / Design</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The design of the setup dialogs must be worked over (=>
+ white background with Sun colors).</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Setup / Help</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><SPAN STYLE="background: transparent">Pressing the Help button
+ should open the Help in a second, resizable window. For the
+ display our own Textengine (MultiLineEdit) should be used.</SPAN></P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER><SPAN STYLE="background: transparent">2</SPAN></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Setup / Readme</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><SPAN STYLE="background: transparent">For displaying the
+ Readme in a more readable form, an additional button should be
+ offered in the dialog that opens the Readme in a HTML view.</SPAN></P>
+ <P><SPAN STYLE="background: transparent">If no browser exists on
+ the system, the button is disabled. Here only the view in the
+ text field of the dialog is available. (The txt format of the
+ Readme must still exist in the installation package.)</SPAN></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER><SPAN STYLE="background: transparent">3</SPAN></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Migration</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>A migration 5.2 => 6.0 should include:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined AutoCorrect
+ settings</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined AutoText modules</P>
+ <LI><P STYLE="margin-bottom: 0cm">User's Basic macros</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined gallery themes</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined templates</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined dictionaries</P>
+ <LI><P STYLE="margin-bottom: 0cm">User's AddIns</P>
+ <LI><P STYLE="margin-bottom: 0cm">User's Workfolder</P>
+ <LI><P STYLE="margin-bottom: 0cm">Database migration
+ including:<BR>- Addressbook data<BR>- Bibliography data</P>
+ <LI><P><SPAN STYLE="background: transparent">User's
+ configuration data (from user/config), including:<BR>-
+ Palettes<BR>- User-defined Math symbols<BR>- User data<BR>(Further
+ configuration data has to be defined in detail.)</SPAN></P>
+ </UL>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / Program</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>An installation package for multiple languages is needed for
+ the OEM version.</P>
+ <P><FONT FACE="Times New Roman, serif"><SPAN STYLE="background: transparent">Thereby
+ choosing a language is valid for the program language (for menus,
+ dialogs) and the document language (samples, templates).</SPAN></FONT></P>
+ <P>Changing the language after installation should be possible
+ via setup (modify installation).</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / linguistic (CJK)</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The Standard installation installs a default set of languages
+ for the linguistic. This set depends on the Office language to be
+ installed. Here the language modules for the CJK version must be
+ re-defined.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / linguistic</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>AutoText and AutoCorrect data must be written language
+ dependent into the installation.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Languages / linguistic</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><SPAN STYLE="background: transparent">The languages for the
+ linguistic that are installed should include not only spell
+ checking, thesaurus and hyphenation but also language-dependent
+ AutoText modules and replacement and exception settings of
+ AutoCorrect.</SPAN></P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER><SPAN STYLE="background: transparent">1</SPAN></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Installation path</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The default installation path should
+ be:<BR>$:\Programs\(%Productname)60 under
+ Windows<BR>\home\(UserID)\(%productname)60 under Linux/Unix</P>
+ <P>The variable stands for StarOffice60, OpenOffice60,
+ StarSuite60.</P>
+ <P>If using the variable is not possible, the installation path
+ has to use "Office60" instead of the product name.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Installation space</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The user should get more information about the available space
+ when selecting the installation path. (=> list box with
+ devices and available/estimated required space)</P>
+ <P>As we cannot show how many space is really needed for a
+ customized installation as long as the user has not selected the
+ modules to be installed, here the installation path has to be
+ determined by the user after selecting the modules.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Dialog buttons</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Button for starting installation/deinstallation must be
+ renamed from "Complete" to "Install"/"Uninstall"</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Java setup</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The user should be better informed for what installing the JRE
+ is good for (Applets, Java services). For this the setup dialog
+ should give a hint and/or the help must be improved.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="3" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Progress bar</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>During the installation process a progress bar appears with
+ text display for actual process description.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Install on demand</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Features, that are not installed yet, will be installed on
+ demand. Thereby the needed files are left on the source (CD or
+ network share) and can be copied down automatically the first
+ time they are used.</P>
+ <P>The user's workflow will not be aborted by this process.</P>
+ <P><A NAME="DDE_LINK1"></A>(It is not clear, if this feature can
+ be realized.)</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">File type info</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>If more than one installation exists on the system, the file
+ type info should be assigned to the latest installation.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>Done</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Adabas</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Adabas must be re-integrated in the setup.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Custom Installation</H1>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Module selection</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The user may not be allowed to deselect something, that is
+ necessary for a feature/component to be installed.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Subtree icons</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Icons in the subtree should be replaced by more meaningful
+ ones.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><FONT FACE="Times New Roman, serif">Module descriptions</FONT></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Module descriptions must be improved</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / dictionaries</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The dictionaries of the add-on folder must be included in the
+ setup to offer more than 5 languages.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Filterlist</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The filterlist must be reviewed and updated.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Fonts</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>It must be clear to the user which fonts will be installed and
+ for what they are needed. For this a font list must be offered
+ that shows all fonts to be installed (same as Writer / Textfilter
+ Im/Export). Selecting a font entry would display a description.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Product name</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The module selection list box should use the variable for the
+ product name like:
+ </P>
+ <P>- %Productname components</P>
+ <P>+Writer<BR>+Calc</P>
+ <P>Whenever the product name itself is clear, we can use just the
+ short names (Writer, Calc etc. instead of %Productname Writer,
+ %Productname Calc). Thus the variable is necessary only the first
+ time.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Summary</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Before starting the installation the user should get a summary
+ of the settings made.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Change / Repair / Deinstallation</H1>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Control Panel</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Win95/98/NT:<BR>When starting deinstallation from the Control
+ Panel's Add/Remove Programs of Windows the option Deinstallation
+ must be selected as default. (Windows only)</P>
+ <P>Win2000:<BR>Here we should offer one Change and one Remove
+ button (instead of Change/Remove). When Change is selected, the
+ default option is "Change installation", when Remove is
+ selected, a message box should appear to ask, if StarOffice /
+ OpenOffice.org really should be deleted.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="3" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Restricted User</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Under W2000/NT installation, deinstallation and changes of the
+ installation are not allowed for restricted users and may not be
+ possible.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>File Deletion</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>All program files and folders of the StarOffice /
+ OpenOffice.org installation must be deleted when deinstalling,
+ only those created or modified by the user remain on the disc
+ (unless, before starting the deinstallation, the user explicitly
+ states that these files have to be deleted, too).</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1 (Windows)</P>
+ <P ALIGN=CENTER>2 (others)</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Repair / Description</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Option is often not understood, must be made more transparent
+ (change text).</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Repair / Source</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Repairing from CD should be possible.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Network installation</H1>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>/net</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>For calling a network installation we should offer a new
+ possibility (in addition to using DOS box + /net). For this
+ clicking on setupnet.lnk starts network installation:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">setup.exe (calls single-user
+ installation)</P>
+ <LI><P>setupnet.lnk (executes the command "setup -net")</P>
+ </UL>
+ <P>Changing an installation should be possible via
+ double-clicking on the setupnet.lnk, which must remain on the CD)</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Multilingual version</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Installing StarOffice / OpenOffice.org in more than one
+ language should be possible for the network installation. The
+ administrator can choose the language to be installed from all
+ available languages that we offer. The user can choose his
+ language from this sub-set. Only one language can be selected by
+ the user. Thus he should be able to change it later by the setup.</P>
+ <P>=> The workstation installation needs a page for choosing
+ the language.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Naming</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The workstation installation offers the two options "Standard
+ Workstation Installation" and Standard Installation local".
+ </P>
+ <P>These options should be renamed to</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">Workstation Installation</P>
+ <LI><P>Local Installation</P>
+ </UL>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ </TBODY>
+</TABLE>
+<H1><BR><BR>
+</H1>
+<DIV TYPE=FOOTER>
+ <P ALIGN=RIGHT STYLE="margin-top: 0.5cm; margin-bottom: 0cm"><SDFIELD TYPE=PAGE SUBTYPE=RANDOM FORMAT=PAGE>1</SDFIELD></P>
+</DIV>
+</BODY>
+</HTML>
\ No newline at end of file
Propchange: incubator/ooo/ooo-site/trunk/content/installation/proposals/setup_feature/setup_features60_proposal.html
------------------------------------------------------------------------------
svn:eol-style = native
Added: incubator/ooo/ooo-site/trunk/content/installation/proposals/ui/flowchart.sxd
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/proposals/ui/flowchart.sxd?rev=1206378&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/ooo/ooo-site/trunk/content/installation/proposals/ui/flowchart.sxd
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/ooo/ooo-site/trunk/content/installation/proposals/ui/setupui.sxw
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/proposals/ui/setupui.sxw?rev=1206378&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/ooo/ooo-site/trunk/content/installation/proposals/ui/setupui.sxw
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream