incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1206297 [4/19] - in /incubator/ooo/ooo-site/trunk/content/framework: documentation/ documentation/devmanual/ documentation/filters/ documentation/filterui/ documentation/mimetypes/ documentation/others/ drafts/ proposals/ proposals/apply/ ...
Date Fri, 25 Nov 2011 20:02:33 GMT
Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/helpagent/helpagentproposal01.htm
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/helpagent/helpagentproposal01.htm?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/proposals/helpagent/helpagentproposal01.htm (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/proposals/helpagent/helpagentproposal01.htm Fri Nov 25 20:00:55 2011
@@ -0,0 +1,272 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE>Proposal for a new Help Agent</TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Solaris Sparc)">
+	<META NAME="AUTHOR" CONTENT="Lutz Hoeger">
+	<META NAME="CREATED" CONTENT="20010209;15581100">
+	<META NAME="CHANGEDBY" CONTENT="Lutz Hoeger">
+	<META NAME="CHANGED" CONTENT="20010209;15581700">
+	<META NAME="CLASSIFICATION" CONTENT="Help Agent in StarOffice / OpenOffice.org">
+	<META NAME="KEYWORDS" CONTENT="User assistance, documentation, help system, Help Agent">
+	<STYLE>
+	<!--
+		@page { size: 21cm 29.7cm; margin: 2cm }
+		P { margin-bottom: 0.21cm; font-family: "sunserif regular", "SunSerif-Regular", "Geneva", "Arial", "Helvetica", "Lucida Sans", Sans-Serif; font-size: 10pt; page-break-before: auto }
+		H1 { margin-top: 0.63cm; margin-bottom: 0.21cm; font-family: "sunsans demi", "SunSans-Demi", "Geneva", "Arial", "Helvetica", "Lucida Sans", Sans-Serif; font-size: 14pt; font-weight: demi-bold; page-break-before: auto }
+		H2 { margin-bottom: 0.21cm; font-family: "sunsans demi", "SunSans-Demi", "Geneva", "Arial", "Helvetica", "Lucida Sans", Sans-Serif; font-size: 12pt; font-weight: demi-bold; page-break-before: auto }
+	-->
+	</STYLE>
+</HEAD>
+<BODY>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Sunsans Heavy"><FONT SIZE=4 STYLE="font-size: 16pt">Proposal
+for a new Help Agent</FONT></FONT></P>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; font-style: normal; font-weight: demi-bold; page-break-after: avoid">
+<FONT FACE="sunsans heavy, SunSans-Heavy, Geneva, Arial, Helvetica, Lucida Sans, Sans-Serif"><FONT SIZE=4>Version
+1, Lutz H&ouml;ger, 02/09/2001</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<DIV ID="Table of Contents1">
+	<DIV ID="Table of Contents1_Head">
+		<P STYLE="margin-top: 0.42cm; font-weight: medium; page-break-after: avoid">
+		<FONT FACE="Sunsans Demi"><FONT SIZE=4>Table of Contents</FONT></FONT></P>
+	</DIV>
+	<P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#1.Preface|outline">Preface</A></FONT></P>
+	<P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#2.Problem|outline">Problem</A></FONT></P>
+	<P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#3.Solution|outline">Solution</A></FONT></P>
+	<P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.Details|outline">Details</A></FONT></P>
+	<P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.1.WhenshouldtheHelpAgentbetriggered?|outline">When
+	should the Help Agent be triggered?</A></FONT></P>
+	<P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.2.Let'sgetvisual|outline">Let's
+	get visual</A></FONT></P>
+	<P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.3.UsingtheHelpAgent|outline">Using
+	the Help Agent</A></FONT></P>
+	<P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.4.Advancedfeatures|outline">Advanced
+	features</A></FONT></P>
+	<P STYLE="margin-left: 0.5cm; margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#4.5.ConfiguringtheHelpAgent|outline">Configuring
+	the Help Agent</A></FONT></P>
+	<P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#5.ImplementationSteps|outline">Implementation
+	Steps</A></FONT></P>
+	<P STYLE="margin-bottom: 0.2cm"><FONT FACE="SunSans-Demi"><A HREF="#6.OpenIssues|outline">Open
+	Issues</A></FONT></P>
+</DIV>
+<H1><A NAME="1.Preface|outline"></A>Preface</H1>
+<P>This short proposal doesn't claim to completely cover all aspects
+of the subject, even though I'm trying to propose the feature as
+complete as possible.</P>
+<H1><A NAME="2.Problem|outline"></A>Problem</H1>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">When
+working with StarOffice / OpenOffice.org (SO / OO.o) there are
+various situations where the program 'decides' to act in a certain
+way that might not have been expected by the user. Some examples for
+this are: </FONT>
+</P>
+<UL STYLE="margin-left: 0.5cm">
+	<LI><P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">the
+	'AutoCorrect' feature automatically completes a word the user has
+	just started to type</FONT></P>
+	<LI><P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">the
+	same feature automatically creates a bullet list from plain text
+	while typing (type '- test', press Enter)</FONT></P>
+	<LI><P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">the
+	'Print' dialog box is shown even though the user has clicked on the
+	'Print File Directly' symbol in the 'Function Bar' (because there
+	was a mismatch between the default system printer and the printer
+	stored in the document)</FONT></P>
+</UL>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">To
+simplify it: from a user's point of view in some situations a program
+behaves unpredictably. No matter how hard we try to avoid these
+cases, in certain situation the expectations of users simply are too
+different.</FONT></P>
+<H1><A NAME="3.Solution|outline"></A>Solution</H1>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">The
+first and very simple idea is to tell users what's happening, e.g.
+use some plain text explaining the current behavior. We tried that in
+SO 5.x, using the so called Help Agent. In the current SO / OO.o
+release (614) there is no such information any more. </FONT>
+</P>
+<P STYLE="margin-bottom: 0.2cm"><FONT FACE="Sunserif Regular">Due to
+the lack of this feature, we can now see the real benefit of this
+mechanism. It helps users in getting out of 'screen mysteries', it
+offers support when users actually need it. So this proposal is about
+the re-implementation of the Help Agent feature to be more elegant,
+more intelligent but also less annoying than formerly.</FONT></P>
+<H1><A NAME="4.Details|outline"></A>Details</H1>
+<H2><A NAME="4.1.WhenshouldtheHelpAgentbetriggered?|outline"></A>When
+should the Help Agent be triggered?</H2>
+<P>The most important feature of the Help Agent is to 'proactively'
+(I don't know any better word) offer support in certain situations.
+This distinguishes it from common help systems which offer help only
+if a user asks for it, e.g. by hitting the 'help' button. The Help
+Agent needs to detect if the user performs an action that may lead to
+confusion or that's generally difficult to understand in order to
+present helpful information to the user.</P>
+<P>The detection of these situations is a quite critical part of the
+Help Agent. The range of implementations for this goes from a static,
+pre-defined list (like in SO 5.x) to some artificial intelligence
+driven agent analyzing the user's behavior and thus detecting usage
+problems. The compromise between release driven reality and feature
+theory lies somewhere in-between. 
+</P>
+<P>I think it's best to start with the simple list implementation and
+advance to something more sophisticated later. A list of situations
+that require user assistance already exists in SO 5.x and can be
+maintained based upon the feedback from our users, e.g. by evaluating
+the FAQ lists that are regularly generated by Sun's Support. 
+</P>
+<H2><A NAME="4.2.Let'sgetvisual|outline"></A>Let's get visual</H2>
+<P>When designing the UI of the new Help Agent, we tried to follow
+the paradigm 'K.I.S.S.' (keep it short &amp; simple). SO 5.x users
+sometimes did complain about the old Help Agent. Very often the first
+thing that was done with it was to disable this feature completely,
+because it was rather irritating than helpful. That was caused by two
+aspects: The window showed up automatically but had to be closed
+again manually, and the content wasn't appropriate for the majority
+of our users - beginners.</P>
+<P>To change the content of the help system is one thing. It's safe
+to say that it will take some time to be accomplished and the whole
+process will probably span a couple of SO / OO.o releases. Fixing the
+usability issue should be possible soon, so let's have a look at a
+first UI design idea. 
+</P>
+<P>Here's a mock-up screen shot of a typical Help Agent situation:
+The user adjusts some settings that have 'invisible side effects' -
+in this case the spell check for the selected languages only
+functions if the appropriate language has been installed, something
+users very often aren't aware of, if they are just 'playing around'
+with some character formatting settings.</P>
+<P ALIGN=CENTER><IMG SRC="offering.gif" NAME="Graphic1" ALIGN=BOTTOM WIDTH=384 HEIGHT=303 BORDER=0></P>
+<P>Due to the 'SO 5.x help content issue', we decided to initially
+display as few text as possible. This leads to the idea of just
+showing up an image button indicating that help is available.  The
+Help Agent gets triggered and shows up in the lower right corner of
+the current document window. The design of the image above is just a
+placeholder for some artwork that would still have to be created.</P>
+<P>The Help Agent window or indicator should appear on top of the
+current document window but underneath a potentially open dialog box
+that has got the focus. It shouldn't be possible to raise the
+document window's z-order above the Help Agent's one. The current
+focus should remain unchanged so that the user can continue his work
+without being interrupted. (This is exactly the behavior of the Help
+Agent window in SO 5.x.)</P>
+<P>Behind the scenes, the help ID of the control that triggered the
+Help Agent gets forwarded to the Help Agent in order to be available
+for later processing.</P>
+<H2><A NAME="4.3.UsingtheHelpAgent|outline"></A>Using the Help Agent</H2>
+<P>To address the complains about the old Help Agent's stickiness,
+the new Help Agent should disappear after a time-out of 30 seconds.
+If the user doesn't do anything but continue his normal work and
+ignores the Help Agent, the pop-up window simply disappears after
+this time-out. If another item triggers the Help Agent within this
+time-out, the countdown timer should be reset and the new help ID
+should be stored instead of the old one.</P>
+<P>If the user clicks on the Help Agent indicator within the time-out
+timeframe, the help system will be opened and the help related to the
+temporarily stored help ID will be displayed. Starting with SO 6.0 /
+OO.0, the help system is an own operating system task. In case this
+task is already running at the time the Help Agent is used (clicked),
+it simply gets the focus and displays the respective help topic. That
+way, only one help task can be open at the same time.</P>
+<H2><A NAME="4.4.Advancedfeatures|outline"></A>Advanced features</H2>
+<P>Turning the static list of Help Agent relevant help IDs into a
+'semi-static' list could be achieved by dropping items dynamically.
+Whenever the Help Agent detects that his help offer didn't succeed,
+i.e. the user didn't make use of it a couple of times (3? 5? 10?)
+within a certain time (e.g. 90 days), an item can be dropped from the
+list. That way the occurrences of the Help Agent can be minimized
+down to what an individual user actually needs. 
+</P>
+<P>I'm not sure whether or not it is necessary to manually reset a
+list that has been modified this way to the factory default. But my
+guts tell me that there might be a number of people who want to have
+this feature. 
+</P>
+<P>So far this is not 'rocket science'. A far more advanced feature
+would be to add new items to the list based on an analysis of the
+program's usage. This could come pretty close to an interactive
+tutor, detecting certain 'inefficiencies' in usage patterns and
+offering the respective shortcuts to the user. This feature itself
+would need a much more extensive description than this proposal is
+supposed to deliver. Maybe someone else wants to pick this up and
+follow upon it?</P>
+<P>Regardless whether or not the typical geek likes it: animations
+are one of those neat features that particularly beginners do like.
+As there is a quite contradictory discussion about this detail, I'll
+leave it open and name it just for the purpose of completeness.</P>
+<P>Something maybe more important to think about is the position of
+the Help Agent indicator. On one hand it brings a certain calmness to
+the user interface, if this window always shows up at the same
+position, on the other hand if this position should ever be occupied
+by something else (like a toolbar or a docked float), it could be
+desirable to open the window somewhere else. SO 5.x had a mechanism
+that tried to position the Help Agent's floating window intelligently
+so that it doesn't cover the currently used dialog box. Of course
+such a feature would be helpful for the new Help Agent's window, too.
+But as the new window should be much smaller than the old one, it
+might be something that can be done later.</P>
+<H2><A NAME="4.5.ConfiguringtheHelpAgent|outline"></A>Configuring the
+Help Agent</H2>
+<P>Even though the new Help Agent tries to be both - as visible as
+necessary and as invisible as possible - there's probably the
+requirement to configure at least some basic settings. 
+</P>
+<UL STYLE="margin-left: 0.5cm">
+	<LI><P>Advanced users might want to switch the feature completely
+	off; so this option should be offered. This implies that the default
+	should be 'on' ;-)</P>
+	<LI><P>The suggested default time-out of 30 seconds might be
+	something that users want to adjust, too. We should offer a scale
+	from 0 to 60 seconds in 5 second steps, so this can be combined with
+	the above configuration setting ('0 seconds' means 'feature is
+	deactivated'). Or should the two settings be independent from each
+	other?</P>
+	<LI><P>As soon as the Help Agent is able to 'forget' or 'learn'
+	about situations it should show up, there's probably some
+	requirement to reset a modified list to the factory default. 
+	</P>
+	<LI><P>As mentioned above, the position of the Help Agent window
+	should later be configurable if it's not possible to make it evade
+	intelligently .</P>
+</UL>
+<H1><A NAME="5.ImplementationSteps|outline"></A>Implementation Steps</H1>
+<P>Driven by product release reality, I suggest the following three
+steps of implementation. However, if someone thinks this isn't
+appropriate, I would be happy to see an alternative.</P>
+<OL STYLE="margin-left: 0.5cm">
+	<LI><P>The first implementation basically should include anything
+	described in the chapters &quot;When should...&quot;, &quot;Let's
+	get...&quot; and &quot;Using&quot;, plus the basic configuration
+	option of enabling/disabling the feature and justifying the
+	time-out.</P>
+	<LI><P>The addition of the feature &quot;dropping items from the
+	list&quot; and the possibility to reset the list should be the main
+	parts of step 2. In addition to this, the window positioning issue
+	(if at all there is such an issue) should be finalized.</P>
+	<LI><P>The third step could be a mid-term to long-term project,
+	defining and implementing the feature &quot;add new items to the
+	list&quot;, as this would probably affect other projects as well.</P>
+</OL>
+<H1><A NAME="6.OpenIssues|outline"></A>Open Issues</H1>
+<P>These are just a few open issues that would need to be resolved in
+order to achieve step 1 and step 2 of the implementation. Probably
+there are many more if one starts digging into the details, but I
+think these are the most obvious ones.</P>
+<UL STYLE="margin-left: 0.5cm">
+	<LI><P>Artwork for the Help Agent indicator<BR>This should clearly
+	indicate 'click me' and 'there's something you might want to know'</P>
+	<LI><P>Further configuration details<BR>Are the configurable
+	settings sufficient or already too detailed? What are reasonable
+	default values to minimize the necessity of configuring this
+	feature?</P>
+	<LI><P>Window behavior<BR>What about stickiness, movability, focus
+	behavior? 
+	</P>
+</UL>
+<DIV TYPE=FOOTER>
+	<P STYLE="margin-top: 0.1cm; margin-bottom: 0.2cm"><FONT SIZE=1 STYLE="font-size: 8pt"><SDFIELD TYPE=DOCINFO SUBTYPE=CHANGE FORMAT=DATE SDNUM="1033;1033;MM/DD/YYYY">02/09/2001</SDFIELD>	<SDFIELD TYPE=DOCINFO SUBTYPE=TITLE>Proposal for a new Help Agent</SDFIELD>	Page
+	<SDFIELD TYPE=PAGE SUBTYPE=RANDOM FORMAT=PAGE>4</SDFIELD> of <SDFIELD TYPE=DOCSTAT SUBTYPE=PAGE FORMAT=PAGE>4</SDFIELD></FONT></P>
+</DIV>
+</BODY>
+</HTML>

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/helpagent/offering.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/helpagent/offering.gif?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/helpagent/offering.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,345 @@
+<!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="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="CREATED" CONTENT="20020128;9504400">
+	<META NAME="CHANGED" CONTENT="20020205;7150155">
+	<STYLE>
+	<!--
+		@page { margin: 2cm }
+	-->
+	</STYLE>
+</HEAD>
+<BODY LANG="en-US">
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><FONT SIZE=5><B>Proposal
+v0.2</B></FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><FONT SIZE=5><B>A new
+keyboard shortcut implementation</B></FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Due to our efforts making the office
+accessible we have to solve some problems regarding keyboard
+shortcuts. This is a chance to enhance our current implementation for
+a better user convenience. 
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The following list shows problems
+regarding our current keyboard shortcut implementation:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">The database and bibliography
+	components are not sfx based. So these components are not able to
+	use a component specific keyboard shortcut configuration. They are
+	only bound to the global keyboard shortcut configuration implemented
+	in the sfx project.<BR><BR>
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Currently we support keyboard
+	shortcut configuration files, but we have to present a better
+	integration for the user to easily adopt his office to other
+	systems/office (See proposal from FLO &ldquo;<B>Keyboard
+	Accessibility Concept</B>&rdquo; about MS Office compatible keyboard
+	shortcut configuration).<BR><BR>
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">We have two different keyboard
+	shortcut configuration file formats. One is based on our old
+	resource file format and supports different languages. If the user
+	changes the keyboard shortcut configuration through our UI dialogs
+	it is stored in our new XML format. Our xml based keyboard shortcut
+	configuration doesn't support more than one language. So we have to
+	find a way to create language specific XML files. We can write a
+	converter that creates XML files out of our old resource file format
+	automatically.<BR><BR>
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Our current implementation is not
+	fine grained enough. We have a global keyboard shortcut
+	configuration and a component based configuration (writer, calc,
+	...). We should introduce a new keyboard shortcut configuration that
+	can be temporary used . For example complex dialogs can use this
+	kind of keyboard shortcut configuration to improve their
+	accessibility.<BR><BR>
+	</P>
+</UL>
+<P STYLE="margin-bottom: 0cm">A new implementation should use our new
+XML configuration files. It should support sfx and non-sfx based
+components to enable a better integration of newly written
+components, like <SPAN LANG="en-US">OpenOffice</SPAN>-based ones. So
+the new implementation must be based on UNO-interfaces and should
+support querying, changing, extending and applying configuration data
+through this API. This proposal describes an architecture that can be
+used for all our UI configuration data.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The new implementation has three
+configuration levels:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">Office configuration level<BR>The
+	office configuration level stores data that is visible to all
+	components. This level assures that common functions are mapped to a
+	defined keyboard shortcut.</P>
+	<LI><P STYLE="margin-bottom: 0cm">Component configuration level<BR>The
+	component configuration level store data that is visible to one type
+	of a component (like writer, calc). This level assures that common
+	component functions are always the same for one component.</P>
+	<LI><P STYLE="margin-bottom: 0cm">Document configuration level<BR>This
+	configuration level stores data that is only visible to a document.
+	It is possible to map document specific functions to a keyboard
+	shortcut. For example a calc document can provide a private function
+	to make a time consuming calculation that be easily access by a
+	shortcut.</P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><IMG SRC="Proposal_Keyboard_shortcuts_html_6a183024.gif" ALIGN=LEFT><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The implementation should work with two
+different kinds of configurations:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">A one instance service that holds
+	the office configurations and can create settings objects for all
+	components (like writer, <SPAN LANG="en-US">calc</SPAN>, ... ) that
+	are available at runtime. So it works as a factory for component
+	settings objects. The implementation can support new components if
+	the &ldquo;configuration storage service&rdquo; is able to provide
+	streams to the configuration of the component.</P>
+	<LI><P STYLE="margin-bottom: 0cm">Model based configuration that has
+	all configuration data that was stored for a single document. 
+	</P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The one instance implementation gives
+access to the office configuration and can create all supported
+component based settings objects through a <SPAN LANG="en-US">XMultiServiceFactory</SPAN>
+interface. The controller has references to two different kinds of
+configurations:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">Component shortcut configuration
+	that is shared by all controller instances of a component.</P>
+	<LI><P STYLE="margin-bottom: 0cm">Document shortcut configuration
+	that is shared by all controllers of a model. They data is stored in
+	the model. The access between controller and model is a private
+	implementation detail.</P>
+	<P STYLE="margin-bottom: 0cm"></P>
+</UL>
+<P STYLE="margin-bottom: 0cm">The controller implements an interface
+to give access to the component and document settings objects. These
+setting objects support loading/saving a XML based configuration
+(through XInput- <SPAN LANG="en-US">XoutputStream</SPAN>) and to get,
+add, remove and replace keyboard shortcuts. These settings objects
+can be applied to the controller or the global configuration. So it
+is possible to have generic access to this data for example for an UI
+dialog that supports changing the configuration. As the access is
+granted through UNO interfaces an external developer is able to use
+this implementation, too.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Saving and loading a configuration
+would work in the following way. The controller knows its &ldquo;component&rdquo;
+and the current configuration type (for example keyboard ). It asks
+the &ldquo;global configuration storage service&rdquo; for a stream
+that stores data for a &ldquo;writer keyboard&rdquo; configuration.
+So the knowledge output the real storage is only known by this
+service, all other implementation uses XInputStream and XOutputStream
+to fulfill their work. This stream is  given to the concrete settings
+object that knows how to store its data as an XML stream and Save(
+stream ) is called.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The controller supports a function
+<I>MapKeyToFunction</I><SPAN STYLE="font-style: normal"> to get a
+mapping between a com.sun.star.awt.KeyEvent and a function. It should
+first make a lookup into the office configuration to find a valid
+mapping if this is not successful the controller has to ask the
+component settings object and last the document settings object. So
+the call hierachy would be:</SPAN></P>
+<P STYLE="margin-bottom: 0cm; font-style: normal">&ldquo;office cfg&rdquo;
+-&gt; 
+</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal">&ldquo;component
+cfg&rdquo; -&gt; 
+</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal">&ldquo;document
+cfg&rdquo;.</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal">The
+<I>MapKeyToFunction</I> function returns a string that is one of the
+following types:</P>
+<P STYLE="margin-bottom: 0cm; font-style: normal"><BR>
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm; font-style: normal">A slot command
+	URL that can be dispatched.</P>
+	<LI><P STYLE="margin-bottom: 0cm; font-style: normal">A command
+	string that must be executed in the component context, like
+	&ldquo;.uno:copy&rdquo;, &ldquo;.uno:cut&rdquo;, &ldquo;.uno:paste&rdquo;.
+	The command string must comply to the command URL specification
+	&ldquo;protocol:command&rdquo;. The command part can be any kind of
+	string. It would be even possible to have an encoded byte stream
+	that could be executed by a special implementation.</P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT FACE="Thorndale, serif"><FONT SIZE=3>The
+current sfx2 keyboard shortcut configuration implementation uses only
+a kind of merged &ldquo;component shortcut configuration&rdquo;. A
+closer look reveals that we can split this configuration into three
+different parts:</FONT></FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">Office configuration that is the
+	real base for all components.</P>
+	<LI><P STYLE="margin-bottom: 0cm">Generic sfx based component
+	configuration. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Component based configuration (
+	writer, calc, draw, ...).</P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The last two configurations should be
+loaded and merged into the &ldquo;component&rdquo; shortcut
+configuration&rdquo; to fit into our new architecture if we are
+running on a system with old configuration layout.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">This proposal just presents a new
+design for the keyboard shortcut configuration but it isn't
+restricted to this special type. There should be no problem to use
+the design to support also:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">Menus</P>
+	<LI><P STYLE="margin-bottom: 0cm">Toolbars</P>
+	<LI><P STYLE="margin-bottom: 0cm">Statusbars</P>
+	<LI><P STYLE="margin-bottom: 0cm">Events</P>
+	<LI><P STYLE="margin-bottom: 0cm">Images</P>
+</UL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts_html_6a183024.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts_html_6a183024.gif?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts_html_6a183024.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro/macrorecording.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/macro/macrorecording.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/proposals/macro/macrorecording.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/proposals/macro/macrorecording.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,207 @@
+<!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="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="CREATED" CONTENT="20020218;17044700">
+	<META NAME="CHANGED" CONTENT="20020219;16054255">
+	<STYLE>
+	<!--
+		@page { margin: 2cm }
+		H1 { margin-bottom: 0.21cm }
+		H1.western { font-family: "Albany", sans-serif; font-size: 16pt }
+		H1.cjk { font-size: 16pt }
+		H1.ctl { font-size: 16pt }
+	-->
+	</STYLE>
+</HEAD>
+<BODY LANG="de-DE">
+<H1 CLASS="western">Some thoughts about Macro Recording</H1>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">All StarOffice versions prior to the
+release of OpenOffice.org had a macro recorder. This tool was able to
+record actions of the user and translate them into StarBasic code. It
+was removed before the OO.o source code was released. To understand
+why it was removed and why it is so hard to create a replacement for
+it, it's necessary to learn something about the way it worked and
+about the internal command processing in OO.o applications.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The OO.o applications are based on the
+SFX application framework. This framework is not an UNO based one,
+it's pure C++. It's main operational area is the management of the
+user interface and the processing of commands created by user
+actions. Every functionality (functions, properties) provided by an
+SFX based application component is described by a structure called
+&bdquo;slot&ldquo;. It contains a number identifying the slot (the
+&bdquo;slot id&ldquo;), some additional information for internal
+processing inside SFX (some mostly boolean parameters describing the
+slot), a name (its &bdquo;API name&ldquo;) and the information wether
+this slot represents a function or a property. For functions it also
+contains a list of all parameters and their names and types and the
+type of the return value, for properties it contains the property
+type.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">All the slots and their properties are
+known at compile time to the application module they belong to.
+Inside the application modules the slots are grouped together into
+data structures called &bdquo;(slot) interface&ldquo;. Every module
+knows several interfaces, each of them representing a &bdquo;context&ldquo;
+of the user interface. Examples are the contexts &bdquo;text
+document&ldquo;, &bdquo;impress slide view&ldquo;, &bdquo;table
+selection&ldquo;, each of them is represented by a corresponding slot
+interface (or a group of them). The sum of all currently available
+contextes (slot interfaces) defines the available feature set of an
+SFX based application component.</P>
+<P STYLE="margin-bottom: 0cm"> 
+</P>
+<P STYLE="margin-bottom: 0cm">The SFX application framework learns
+about the slots by being dynamically bound to the modules and slot
+interfaces at runtime. So it is able to browse through the whole
+available feature set of the application component. All currently
+bound slot interfaces are pushed on a stack provided by the SFX
+framework, thus defining an ordering mechanism for them. Pushing
+interfaces on the stack or removing interfaces from there is the way
+context switches in the user interface are reflected in the SFX.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">All user interface elements written for
+the SFX (f.e. toolboxes, menus, keyboard shortcuts) don't call
+directly into the application code, they just call a very generic SFX
+based API to execute a slot. The slot is identified by its slot id
+and the SFX framework is able to find the right code that is able to
+process the slot by browsing through the bound slot interfaces in a
+well defined manner, using the stack of slot interfaces mentioned
+above. Many calls are executed without additional parameters, but
+many others also pass parameters while executing the slot. An example
+for the first case is a simple click on a menu entry. An example for
+the second case is when the user changes some values in a dialog and
+leaves the dialog by clicking its &bdquo;OK&ldquo; button. Here all
+changed values in the dialog are sent as parameters of the slot
+command.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The generic API assures that every
+command goes through the same code in the SFX framework, and so this
+framework is able to translate every slot execution into a single
+StarBasic statement or a group of them, just by finding the slot
+structure belonging to the slot being executed, the slot interface it
+is belonging to, getting the slots' API name and identifying the
+parameters. (In the user interface usually no return values are
+processed.) Here a slot interface or a group of slot interfaces
+represents an object, every slot is a method or a property of such
+object. Both together form a StarBasic statement like &bdquo;Object.Method(
+)&ldquo;.</P>
+<P STYLE="margin-bottom: 0cm">The Basic code generated this way used
+the so called &bdquo;old&ldquo; SO-Basic API, that is not supported
+anymore in OO.o and SO6, and it is not in any way related to the
+&bdquo;real&ldquo; API of the OO.o/SO applications. 
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The slot based API is still used for
+large parts of the internal command execution in OO.o (the
+communication between  the application component and its user
+interface), but it is not possible to translate it into any UNO based
+API. To be honest, only a few slot calls will ever end up in calling
+a UNO based API of the underlying application component.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">It is possible to transform every slot
+command into a call for the generic UNO based &bdquo;dispatch API&ldquo;,
+where every functionality is described by a command string (we call
+them &bdquo;command URLs&ldquo;, because they use the form
+&bdquo;scheme:scheme dependent part&ldquo;).</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">This API uses a chain of objects
+implementing the DispatchProvider service. If the first object in the
+chain is asked for a Dispatch object for an arbitrary command, it
+will check the command if it wants to handle it. If the check turns
+out to be positive, a Dispatch object is returned that is able to
+execute the command, otherwise the query is passed to the next chain
+object etc. If a Dispatch object was found anywhere in the chain, 
+the command is executed by calling the dispatch method of the
+Dispatch object, where all parameters are passed as PropertyValue
+structs.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The result of a transformation from SFX
+slot execution to dispatch call is a call dispatching the command
+&bdquo;<A HREF="slot:xxxx">slot:xxxx</A>&ldquo; (xxxx=slot id),
+passing all necessary parameters as PropertyValues. Newer UI
+components are using this API instead of the slot based SFX API, just
+to have a UNO based interface to the application componnent and not a
+C++ based one. The SFX framework provides some wrapper code to
+translate between the slot based API and the dispatch framework for
+all these newer UI components if they are used for a SFX based
+application component.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">But the dispatch API, though being UNO
+based, is only of limited practical use, because these calls are just
+textual representations of the binary slot data. If you want to write
+a program that uses OO.o API to work on OO.o documents, the dispatch
+API is definitely not the one you want to use (except in some special
+cases, where the functionality is not accessible by other APIs). The
+dispatch API is just thought as the generic programming interface for
+a mostly generic UI code.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">It is possible to record macros just
+for automation purposes using  the SFX or the dispatch API calls:
+take the internal binary representation of the slot commands (or the
+command URL and the parameters of the dispatch call), store it
+anywhere and execute it afterwards by using a &bdquo;slot machine&ldquo;
+(only evil thinking persons will misunderstood this name in this
+context here ;-) ) or a &bdquo;dispatch machine&ldquo;. But usually a
+macro macro recorder is wanted to offer more than only automation:
+most people want to have created source code they can browse and
+modify. And this is exactly what you can't get from the SFX. Many
+(most?) user interactions in the OO.o applications are processed
+without any single UNO call, so there is nothing you can &bdquo;record&ldquo;.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">So what do we need to have the &bdquo;macro
+recording&ldquo; feature back?</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">First, every slot execution (or
+dispatch call) must be mapped to one or several API calls of the
+objects they are working on. This is hard work enough, don't expect
+this to happen in the near future.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">But even if you have got this made, you
+will need something that translates the API calls made into source
+code of any (scripting) language supporting UNO. This can't be a
+built-in UNO feature, because you want only the &bdquo;top level&ldquo;
+UNO calls to be recorded, not the subsequent calls, because you will
+get them called anyway when executing the macro. Perhaps the &bdquo;top
+level&ldquo; calls could marked as recordable by the (AFAIK currently
+not accessible UNO context), but this looks &bdquo;hacky&ldquo; and
+ugly to me.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">I'd prefer an explicit solution, where
+every dispatch provider object that returns a dispatch object will be
+asked to record this call into one or several API statements, but I
+don't have any clever ideas for that. 
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">So I'd appreciate any ideas from
+anybody who wants to contribute to that. May be it turns out that the
+&bdquo;UNO built in&ldquo; solution is not that hacky as it seems,
+may be that there is something completely different that puts a new
+light on the problem. 
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro/macrorecording.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements.html Fri Nov 25 20:00:55 2011
@@ -0,0 +1,233 @@
+<!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="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="CREATED" CONTENT="20011123;18135200">
+	<META NAME="CHANGED" CONTENT="20011128;10004660">
+
+</HEAD>
+<BODY LANG="de-DE">
+<H1 CLASS="western"><SPAN LANG="en-US">Security Enhancements in
+StarOffice 6.0 / OpenOffice.org according to IssueZilla Bug
+#1120 
+</span></H1>
+<SPAN LANG="en-US"> 
+<H1 CLASS="western"> Problem to Solve</H1>
+<OL>
+  <P LANG="en-US" STYLE="margin-bottom: 0cm">Macros in all documents, executed 
+    via file:// url; will be executed without warning.</P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<OL>
+  <H2 CLASS="western">Solution</H2>
+</OL>
+<OL>
+  <P STYLE="margin-bottom: 0cm"><SPAN LANG="en-US">A solution to solve this problem 
+    is to give users the possibility to set all macro related security settings 
+    in <I>Tools-Option-Security </I><SPAN STYLE="font-style: normal">tab.</SPAN></SPAN></P>
+</OL>
+<OL>
+  <P LANG="en-US" STYLE="margin-bottom: 0cm; font-style: normal">The following 
+    steps should solve the problem.</P>
+</OL>
+<P LANG="en-US" STYLE="margin-bottom: 0cm; font-style: normal"><BR>
+</P>
+<OL>
+  <H3 CLASS="western"><B>Path Settings</B></H3>
+  <P CLASS="western">The path list (<I>Tools-Options-Security</I>) contains all 
+    trusted path given by users. The default<BR>
+    'file://' entry in the path list should be replace by more precise paths listed 
+    below:</P>
+</OL>
+<P LANG="en-US" STYLE="margin-bottom: 0cm; font-style: normal"><BR>
+</P>
+<UL>
+  <LI> 
+    <P LANG="en-US" STYLE="margin-bottom: 0cm">$instURL</P>
+  <LI> 
+    <P STYLE="margin-bottom: 0cm">$userURL</P>
+  <LI> 
+    <P LANG="en-US" STYLE="margin-bottom: 0cm">$workDIR</P>
+</UL>
+<P LANG="en-US" STYLE="margin-left: 0.53cm; margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-left: 0.53cm; margin-bottom: 0cm"><SPAN LANG="en-US">All path 
+  has to point to standard folders. Changing the old file URL to the three new 
+  once provides more security due to the fact that users do not have the possibility 
+  to run macros from directories like <I>Temp for </I><SPAN STYLE="font-style: normal">example.</SPAN></SPAN></P>
+<P STYLE="margin-left: 0.53cm; margin-bottom: 0cm"><BR>
+</P>
+<OL START=2>
+  <H3 CLASS="western"><B>Run Macro Settings</B></H3>
+  <P STYLE="margin-bottom: 0cm">The three radio buttons (From list, Never execute, 
+    Always execute) located on the Tools-Options-Security page will be replace 
+    by a dropdown list box (labeled <I>Run macros</I>) which contains the three 
+    options</P>
+  <P LANG="en-US" STYLE="margin-bottom: 0cm; font-style: normal">
+  <SPAN ID="Frame1" STYLE="float: left; width: 15.88cm; height: 0.53cm; padding: 0cm; background: #ffffff"> 
+  <TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
+    <COL WIDTH=128*> <COL WIDTH=128*> <THEAD> 
+    <TR VALIGN=TOP> 
+      <TH WIDTH=50%> 
+        <P CLASS="western">Old Term</P>
+      </TH>
+      <TH WIDTH=50%> 
+        <P CLASS="western">New Term</P>
+      </TH>
+    </TR>
+    </THEAD> <TBODY> 
+    <TR VALIGN=TOP> 
+      <TD WIDTH=50%> 
+        <P CLASS="western">From list</P>
+      </TD>
+      <TD WIDTH=50%> 
+        <P CLASS="western">According to path list</P>
+      </TD>
+    </TR>
+    <TR VALIGN=TOP> 
+      <TD WIDTH=50%> 
+        <P LANG="en-US" CLASS="western">Never execute</P>
+      </TD>
+      <TD WIDTH=50%> 
+        <P CLASS="western">Never</P>
+      </TD>
+    </TR>
+    <TR VALIGN=TOP> 
+      <TD WIDTH=50%> 
+        <P LANG="en-US" CLASS="western">Always execute</P>
+      </TD>
+      <TD WIDTH=50%> 
+        <P CLASS="western">Always</P>
+      </TD>
+    </TR>
+    </TBODY> 
+  </TABLE>
+  <P CLASS="frame-contents-western"><BR>
+    <BR>
+  </P>
+  </SPAN><BR CLEAR=LEFT>
+  The options will be renamed as listed below:<BR>
+  In addition beneath to the <I>Run</I> <I>macros</I> dropdown list box are located 
+  two check boxes. The first one is labeled <I>Confirm in the case of other document 
+  sources</I> the other is labeled <I>Show warning before running macros. </I>The<I> 
+  Show warning before running </I>feature is the renamed and removed feature of 
+  Tools-Configure-Events / Security settings (Figure <A HREF="#Graphic1|graphic">1</A> 
+  &amp; <A HREF="#Graphic2|graphic">2</A>)<BR>
+  <BR>
+  The<I> Confirm in the case of other document sources</I> option will be enabled 
+  if users chose the <I>According to path list</I> option in the dropdown list, 
+  otherwise the Confirm ..... item remains disabled (grayed out).<BR>
+  <BR>
+  <p></P>
+  <P STYLE="margin-bottom: 0cm"><SPAN LANG="en-US"><SPAN STYLE="font-style: normal">The 
+    </SPAN><I>Show warning before running macros </I><SPAN STYLE="font-style: normal">option 
+    will be disabled if the option </SPAN><I>Never</I><SPAN STYLE="font-style: normal"> 
+    was chosen in the </SPAN><I>Run Macros</I><SPAN STYLE="font-style: normal"> 
+    dropdown list box. The states are illustrated in Figure <A HREF="#Graphic3|graphic">3</A>,<A HREF="#Graphic4|graphic">4</A>,<A HREF="#Graphic4|graphic">5</A> 
+    &amp; </SPAN></SPAN><A HREF="#Graphic6|graphic">6</A>.<BR>
+    <BR>
+  </P>
+  <H3 CLASS="western" STYLE="font-style: normal"><B>Warning Message</B></H3>
+  <P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="font-style: normal">The 
+    warning message which appears, if a macro will be run from a </SPAN>location 
+    which is not trusted, should be expanded by a more detailed information. The 
+    renewed warning dialogue needs much space for text than the old one.</P>
+  <P STYLE="margin-bottom: 0cm"><SPAN LANG="en-US"><BR>
+    <B>Current Text</B><BR>
+    <I>An event to which a macro is configured has been started. Do you want to 
+    execute the macro?</I><BR>
+    <BR>
+    <SPAN STYLE="font-style: normal">CheckBox</SPAN><I> Do not warn again for 
+    this document</I>.<BR>
+    OKButton <I>Run</I><BR>
+    CancelButton <I>Don't</I> <I>run</I></SPAN></P>
+  <P STYLE="margin-bottom: 0cm"><SPAN LANG="en-US"><BR>
+    <B>New Text (macro title is an example):</B><BR>
+    <I>An event to which a macro, called &quot;soffice.Gimmicks..GetTexts. GetCalcGraphicNames&quot;, 
+    is configured has been started. Do you want to run the macro?<BR>
+    <BR>
+    </I><SPAN STYLE="font-style: normal">CheckBox</SPAN><I> Do not warn again 
+    for this document</I></SPAN>.<BR>
+    OKButton <I>Run</I><BR>
+    CancelButton <I>Don't</I> <I>run</I></P>
+  <H3 CLASS="western"><BR>
+    Illustrations</H3>
+</OL>
+<P CLASS="western">
+<SPAN ID="Frame2" STYLE="background: #ffffff"
+	> 
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic1|graphic"></A></P>
+</SPAN><span lang="en-US"><span id="Frame2" style="background: #ffffff"
+	><img src="security_enhancements_html_m2dbadf08.gif" name="Graphic1" align=LEFT width=572 border=0 height="422"></span></span><SPAN ID="Frame2" STYLE="background: #ffffff"
+	> 
+<P STYLE="margin-top: 0.21cm"><BR CLEAR=LEFT>
+  <FONT SIZE=2><I>Illustration 1 current Configuration/Events tab</I></FONT></P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western"><BR>
+  <BR>
+</P>
+<P CLASS="western"><BR>
+  <BR>
+</P>
+<P CLASS="western"><BR>
+  <BR>
+</P>
+<P CLASS="western">
+<SPAN ID="Frame3" STYLE="background: #ffffff"
+	> 
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic2|graphic"></A><IMG SRC="security_enhancements_html_51f79ff8.gif" NAME="Graphic2" ALIGN=LEFT WIDTH=572 BORDER=0 height="422"><BR CLEAR=LEFT>
+  <FONT SIZE=2><I> Illustration 2 Configuration/Events dialogue after removing 
+  the &quot;Show warning&quot; option.</I></FONT></P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western">
+<SPAN ID="Frame4" STYLE="background: #ffffff"
+	> 
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic3|graphic"></A><IMG SRC="security_enhancements_html_70928bb3.gif" NAME="Graphic3" ALIGN=LEFT WIDTH=536 BORDER=0 height="371"><BR CLEAR=LEFT>
+  <FONT SIZE=2><I>Illustration 3 Renewed Tool Options Security dialogue </I></FONT> 
+</P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western">
+<SPAN ID="Frame5" STYLE="background: #ffffff"
+	> 
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic4|graphic"></A><IMG SRC="security_enhancements_html_m4000e9d0.gif" NAME="Graphic4" ALIGN=LEFT WIDTH=536 BORDER=0><BR CLEAR=LEFT>
+  <FONT SIZE=2><I>Illustration 4 The security dialogue with &quot;Run macro Never&quot; 
+  option</I></FONT></P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western"><BR>
+  <BR>
+</P>
+<P CLASS="western">
+<SPAN ID="Frame6" STYLE="background: #ffffff"
+	> 
+<P STYLE="margin-top: 0.21cm"><IMG SRC="security_enhancements_html_m4acea22c.gif" NAME="Graphic5" ALIGN=LEFT WIDTH=536 BORDER=0><BR CLEAR=LEFT>
+  <FONT SIZE=2><I>Illustration 5 The security dialogue with &quot;Run macro Alway&quot; 
+  option</I></FONT></P>
+</SPAN><BR CLEAR=LEFT>
+<BR>
+<BR>
+<p></P>
+<P CLASS="western">
+<SPAN ID="Frame7" STYLE="background: #ffffff"> 
+<P STYLE="margin-top: 0.21cm"><A NAME="Graphic6|graphic"></A><IMG SRC="security_enhancements_html_md0eecca.gif" NAME="Graphic6" ALIGN=LEFT WIDTH=536 BORDER=0><BR CLEAR=LEFT>
+  <FONT SIZE=2><I>Illustration 6 German Version of the new features</I></FONT></P>
+</SPAN><BR>
+<BR>
+<p></P>
+</span> 
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_51f79ff8.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_51f79ff8.gif?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_51f79ff8.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_70928bb3.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_70928bb3.gif?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_70928bb3.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_m2dbadf08.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_m2dbadf08.gif?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_m2dbadf08.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_m4000e9d0.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_m4000e9d0.gif?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_m4000e9d0.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_m4acea22c.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_m4acea22c.gif?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_m4acea22c.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_md0eecca.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_md0eecca.gif?rev=1206297&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/framework/proposals/macro_security/security_enhancements_html_md0eecca.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/printing/Standard_Printer.htm
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/printing/Standard_Printer.htm?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/proposals/printing/Standard_Printer.htm (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/proposals/printing/Standard_Printer.htm Fri Nov 25 20:00:55 2011
@@ -0,0 +1,154 @@
+<!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="Frank Loehmann">
+	<META NAME="CREATED" CONTENT="20001107;9561921">
+	<META NAME="CHANGEDBY" CONTENT="Frank Loehmann">
+	<META NAME="CHANGED" CONTENT="20010219;17473391">
+	<STYLE>
+	<!--
+		P { font-family: "Arial", sans-serif }
+		H2 { font-family: "Arial", sans-serif }
+		TD P { font-family: "Arial", sans-serif }
+		TH P { font-family: "Arial", sans-serif }
+	-->
+	</STYLE>
+</HEAD>
+<BODY>
+<P STYLE="margin-bottom: 0cm"><FONT FACE="Arial, sans-serif">Autor:
+Frank Loehmann; </FONT><A HREF="mailto:frank.loehmann@germany.sun.com"><FONT FACE="Arial, sans-serif">frank.loehmann@germany.sun.c</FONT></A></P>
+<P STYLE="margin-bottom: 0cm"><FONT FACE="Arial, sans-serif">Date: 16
+January 2001; final</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT FACE="Arial, sans-serif">Use
+Standard Printer as Default Document Printer</FONT></P>
+<H2><FONT FACE="Arial, sans-serif">Problem</FONT></H2>
+<P><FONT FACE="Arial, sans-serif">OpenOffice stores the printer, used
+for the formatting and printing of the current document, in the
+document file itself.</FONT></P>
+<P STYLE="page-break-before: always"><FONT FACE="Arial, sans-serif">The
+restoring of this document printer after loading a document can be a
+problem, if OpenOffice will be used in a global network environment
+(e.g. a WAN or especially in Sun's flexible Office concept using
+SunRay's) or on a system (e.g. a notebook) where different
+environments (printer queue's) are present at the same time. (e.g. a
+notebook used at home and in the company). In such an environment
+documents will often be printed on the false printer when the print
+direct function (offered in the standard object bar) will be used.</FONT></P>
+<P><FONT FACE="Arial, sans-serif">Maybe this problem occurs as well
+if OpenOffice will be used in the new Sun Webtop environment. (not
+evaluated at this point)</FONT></P>
+<H2><FONT FACE="Arial, sans-serif">Solution</FONT></H2>
+<P><FONT FACE="Arial, sans-serif">We have analysed different
+possibilities to solve this problem. Due to our main concern, not to
+confuse the user with a new UI, we decided to look for an easy way to
+solve the problem without big UI changes and without loosing
+features. Always keep in mind that printing is a very key critical
+feature and will be used by nearly every user!</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">The
+direct printing button in the objectbar of OpenOffice does not call
+the print dialog in the current version. For our solution we want to
+show the print dialog in some cases which will cause the problem
+described above.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">We want
+to call the print dialog on condition that the document printer
+differs from the system standard printer and the printer is available
+on the system too. Just not to loose the information which printer
+was set on the document (important for document templates used in
+companies), we should preselect this printer in the print dialog.
+Additionally we should implement a new option in the tools-options
+section to suppress this print dialog at any time and to force the
+printout on the system or document printer.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">If a
+document printer is not available on the current system, the printout
+will be done on the system default printer without any print dialog.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Furthermore
+a bubble help on the direct printout button should show the printer
+which will be used for the printout. Also a new section to the help
+should be added. The help should contain a tip how to set a system
+default printer &#147;hard&#148; to the document without the standard
+printer flag. (maybe important for template design) (-&gt; In this
+case the current standard printer should be changed to a temporary
+one)</FONT></P>
+<P><FONT FACE="Arial, sans-serif"><B>Dialog</B></FONT></P>
+<TABLE WIDTH=753 BORDER=1 CELLPADDING=4 CELLSPACING=0>
+	<COL WIDTH=367>
+	<COL WIDTH=368>
+	<THEAD>
+		<TR VALIGN=TOP>
+			<TH WIDTH=367>
+				<P ALIGN=CENTER><FONT FACE="Arial, sans-serif"><FONT SIZE=3><I>Local
+				System Configuration</I></FONT></FONT></P>
+			</TH>
+			<TH WIDTH=368>
+				<P ALIGN=CENTER><FONT SIZE=3><I><FONT FACE="Arial, sans-serif">
+				Action</FONT></I></FONT></P>
+			</TH>
+		</TR>
+	</THEAD>
+	<TBODY>
+		<TR VALIGN=TOP>
+			<TD WIDTH=367>
+				<P><SPAN STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Document
+				printer is equal to default system printer</FONT></SPAN></P>
+			</TD>
+			<TD WIDTH=368>
+				<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Printout
+				on default system printer without dialog</FONT></P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=367>
+				<P><SPAN STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Printer
+				available but not set as system default</FONT></SPAN></P>
+			</TD>
+			<TD WIDTH=368>
+				<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Show
+				print dialog with document printer  preselected</FONT></P>
+			</TD>
+		</TR>
+		<TR VALIGN=TOP>
+			<TD WIDTH=367>
+				<P><SPAN STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Document
+				printer is not available</FONT></SPAN></P>
+			</TD>
+			<TD WIDTH=368>
+				<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Printout
+				on default system printer without dialog</FONT></P>
+			</TD>
+		</TR>
+	</TBODY>
+</TABLE>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Arial, sans-serif"><B>Option in the tools-option
+section for print direct</B></FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">We
+should add the following option on tools-options-common-printing:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">Print
+direct &nbsp;(group box)</FONT></P>
+<TABLE WIDTH=361 BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0>
+	<COL WIDTH=351>
+	<THEAD>
+		<TR>
+			<TD WIDTH=351 VALIGN=TOP>
+				<P><FONT FACE="Arial, sans-serif"><B>[ &nbsp;] Suppress print
+				dialog if document printer does not match system default printer</B></FONT></P>
+				<P><FONT FACE="Arial, sans-serif">(X) always print on system
+				default printer (defaulted)</FONT></P>
+				<P><FONT FACE="Arial, sans-serif">( &nbsp;) always print on
+				document printer (if available)</FONT></P>
+			</TD>
+		</TR>
+	</THEAD>
+</TABLE>
+<P><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Arial, sans-serif">The two
+options are disabled as long as the main option (suppressing the
+dialog) is not checked (and this is the default). The option &#147;always
+use system default print&#148; will be defaulted too.</FONT></P>
+</BODY>
+</HTML>
\ No newline at end of file

Added: incubator/ooo/ooo-site/trunk/content/framework/proposals/setup_feature/setup_features60_proposal.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/framework/proposals/setup_feature/setup_features60_proposal.html?rev=1206297&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/framework/proposals/setup_feature/setup_features60_proposal.html (added)
+++ incubator/ooo/ooo-site/trunk/content/framework/proposals/setup_feature/setup_features60_proposal.html Fri Nov 25 20:00:55 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 &#150; Must</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">2 &#150; 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 (=&gt;
+				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 =&gt; 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 &quot;Office60&quot; 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. (=&gt; 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 &quot;Complete&quot; to &quot;Install&quot;/&quot;Uninstall&quot;</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 &quot;Change installation&quot;, 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 &quot;setup -net&quot;)</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>=&gt; 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 &quot;Standard
+				Workstation Installation&quot; and Standard Installation local&quot;.
+								</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/framework/proposals/setup_feature/setup_features60_proposal.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message