incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1206944 [2/2] - in /incubator/ooo/ooo-site/trunk/content/ui/proposals: ./ Spacing_and_Positioning/ inherited_windows/ toollbars/
Date Mon, 28 Nov 2011 00:43:40 GMT
Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/index.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/index.html?rev=1206944&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/ui/proposals/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/ui/proposals/index.html Mon Nov 28 00:43:32 2011
@@ -0,0 +1,224 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+
+<html>
+
+ <head>
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
+  <title>spec proposals</title>
+  <meta name="GENERATOR" content="StarOffice 6.1 Beta 1 (Win32)">
+  <meta name="AUTHOR" content="Oliver Specht">
+  <meta name="CREATED" content="20010919;10333008">
+  <meta name="CHANGED" content="20030313;11350734">
+ </head>
+
+ <body lang="en-US" dir="LTR">
+  <div align="right">
+   <i>Last modified <csobj w="86" h="16" t="DateTime" locale="00000809" format="LongDate" region="0">05 June 2007</csobj></i></div>
+  <h1>Spec Proposals for OOo 1.1.x</h1>
+  <table border="0" cellpadding="2" cellspacing="1" bgcolor="#dddddd">
+   <tbody>
+    <tr>
+     <th align="left" bgcolor="#dddddd"><b>Date</b></th>
+     <th align="left" bgcolor="#dddddd"><b>Title</b></th>
+    </tr>
+    <tr>
+     <td bgcolor="white">Sep 21, 2001</td>
+     <td bgcolor="white"><a href="print-modified-proposal.html">Printing and the &quot;document modified&quot; status</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Oct 09, 2001</td>
+     <td bgcolor="white"><a href="toollbars/Toolbars_And_Menue_Proposal_final.html">Redesign of Toolbars, Menus and Icons</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Nov 6, 2001</td>
+     <td bgcolor="white"><a href="New-Office-UI.html">Re-Arranging the common Office UI code</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Nov 7, 2001</td>
+     <td bgcolor="white"><a href="inherited_windows/inherited_windows.html">Early Draft of Inherited Window Behavior</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Jan 15, 2002</td>
+     <td bgcolor="white"><a href="Spacing_and_Positioning/metrics.htm">Draft Dialogue Specification and Guidelines - Spacing and Positioning</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Jan 15, 2002</td>
+     <td bgcolor="white">
+      <p><a href="../FunctionalDescription/status_quo_stylist.html">Status quo of the Stylist</a></p>
+     </td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Jan 15, 2002</td>
+     <td bgcolor="white">
+      <p><a href="../FunctionalDescription/status_quo_navigator.html">Status quo of the Navigator</a></p>
+     </td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Feb 4, 2002</td>
+     <td bgcolor="white"><a href="CustomColors1_5.sxw">Custom Colors: Configuration of user interface items in OOo</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Feb 21, 2002</td>
+     <td bgcolor="white"><a
+ href="../specification/product_registration.html">Product Registration<br>
+      </a>OpenOffice.org features a
+mechanism for online product registration. Thus, any vendor which
+creates an own branded version out of OpenOffice.org can allow its
+users .....</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Feb 28, 2002</td>
+     <td bgcolor="white"><a href="Floating_Windows_Proposal.htm">Proposal how to handle floating windows (i.e. Stylist, Navigator, Toolbars)</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">
+      <p>Mar 4, 2002</p>
+     </td>
+     <td bgcolor="white">
+      <p><a href="../FunctionalDescription/file_picker.html">rudimentary functional description for OOo's file picker implementation</a></p>
+     </td>
+    </tr>
+    <tr>
+     <td bgcolor="white">July 17, 2002</td>
+     <td bgcolor="white"><a href="Macro_Recorder_UI_Specification.sxw">Macro recorder UI Specification</a> (sxw)</td>
+    </tr>
+    <tr valign="TOP">
+     <td bgcolor="white">Apr 10, 2003</td>
+     <td bgcolor="white"><a href="PDFExport.sxw">PDF Export - UI specification v.1.1</a> (sxw)<br>
+      <a href="PDF_export_UI_specification.sxw">PDF Export - UI specification v.1.0</a> (sxw, 11/29/02)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Jan 13, 2003</td>
+     <td bgcolor="white"><a href="File_close_behavior.sxw">File Close Behavior- UI specification</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Mar 10, 2003</td>
+     <td bgcolor="white"><a href="Drag_and_Drop.sxw">Drag &amp; Drop Specification</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Mar 13, 2003</td>
+     <td bgcolor="white"><a href="Printer_Independent_Layout.sxw">Printer Independent Layout</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Mar 13, 2002</td>
+     <td bgcolor="white"><a
+ href="../specification/ContextMenuHandlingSvTreeListBox.html">Context menu handling
+SvTreeListBox<br>
+      </a>Changed behaviour of handling
+context menu in SvTreeListBox and all derived classes thus the
+behaviour is similar to common cases in other non-OpenOffice.org
+applications.</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Sep 19, 2003</td>
+     <td bgcolor="white"><a href="XMLFilterSpec.sxw">XML Filter Configuration</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Apr 16, 2003</td>
+     <td bgcolor="white"><a href="StartingStarOffice.sxw">Starting Office</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Apr 24, 2003</td>
+     <td bgcolor="white"><a href="Automated_I18N_Settings_0.sxw">Automated I18N Settings</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">May 2, 2003</td>
+     <td bgcolor="white"><a href="Paste_special_for_unformatted_text_in_Calc.sxw">New &quot;Paste Special&quot; for unformatted text in Calc</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Jun 24, 2003</td>
+     <td bgcolor="white"><a href="GallerynDataSourcePanels.sxw">Gallery and DataSource Panels Layout</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Sep 12, 2003</td>
+     <td bgcolor="white"><a href="../specification/FileDialog_RestrictedPaths.sxw">File Dialog - Path Restrictions</a> (sxw)<br>
+      OpenOffice.org features a
+mechanism for online product registration. Thus, any vendor which
+creates an own branded version out of OpenOffice.org can allow its
+users .....</td>
+    </tr>
+    <tr>
+     <td bgcolor="white" colspan="2">
+      <h4>Accessibility (General)</h4>
+     </td>
+    </tr>
+<tr>
+     <td bgcolor="white">Mar 4, 2002</td>
+     <td bgcolor="white"><a href="Accessible_Setup.sxw">Proposal for an accessible setup</a> (sxw)</td>
+    </tr>
+     <tr>
+     <td bgcolor="white"><nobr>Mar 22, 2002</nobr></td>
+     <td bgcolor="white"><a href="Options_Dialog.sxw">Options Dialog for Accessibility</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Feb 13, 2003</td>
+     <td bgcolor="white"><a
+ href="../specification/options_accessibility.html">Accessibility Options Dialog<br>
+      </a>specifies the user interface for
+Accessibility Options</td>
+    </tr>
+    <tr>
+     <td bgcolor="white" colspan="2">
+      <h4>Accessibility (Keyboard Input)</h4>
+     </td>
+    </tr>
+<tr>
+     <td bgcolor="white">Feb 6, 2002</td>
+     <td bgcolor="white"><a href="Accessibility_Draw_Impress_Keyboard_Shortcuts.htm">Keyboard shortcuts for Impress and Draw</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Feb 7, 2002</td>
+     <td bgcolor="white"><a href="Gallery_Keyboard_Accessibility.htm">Gallery Keyboard Accessibility</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Feb 18, 2002</td>
+     <td bgcolor="white"><a href="Accessiblity_Chart_Keyboard_Concept.htm">Keyboard Concept for Chart</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Feb 22, 2002</td>
+     <td bgcolor="white"><a href="Data_Pilot_Accessibility.sxw">Keyboard accessibility for DataPilot layout dialog</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Feb 22, 2002</td>
+     <td bgcolor="white"><a href="Ref_Input_Control_Accessibility.sxw">Keyboard accessibility of the reference input control</a> (sxw)</td>
+    </tr>
+<tr>
+     <td bgcolor="white">Apr 7, 2002</td>
+     <td bgcolor="white"><a href="Readonly_mode.htm">Proposal how to enable text selection in read only documents via keyboard</a></td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Jun 13, 2002</td>
+     <td bgcolor="white"><a href="CSV_Import_Accessibility.sxw">Accessibility of the CSV Import Dialog</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td colspan="2" bgcolor="white">
+      <h4><b>Accessibility (High Contrast Mode)</b></h4>
+     </td>
+    </tr>
+<tr>
+     <td bgcolor="white">Mar 5, 2002</td>
+     <td bgcolor="white"><a href="Renewed_Document_Preview.sxw">Concept of an Accessible Document Preview</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Jan 25, 2002</td>
+     <td bgcolor="white"><a href="Accessible_Notes.sxw">Proposal of notes which are high contrast ready</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Feb 27, 2002</td>
+     <td bgcolor="white"><a href="Renewed_Rulers.sxw">Proposal of high contrast ready ruler</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">Mar 1, 2002</td>
+     <td bgcolor="white"><a href="Icons_in_high_contrast_mode.sxw">Accessibility: Proposal of Icons in High Contrast Mode</a> (sxw)</td>
+    </tr>
+    <tr>
+     <td bgcolor="white">July 7, 2002</td>
+     <td bgcolor="white"><a href="Automatic_textcolor.htm">Proposal to change textcolor to automatic</a></td>
+    </tr>
+   </tbody>
+  </table>
+  <h3>Related Pages</h3>
+  <p><a href="http://specs.openoffice.org/">OpenOffice.org Specification Project</a> (all specifications for OOo2)</p>
+ </body>
+
+</html>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/index.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/inherited_windows/inherited_windows.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/inherited_windows/inherited_windows.html?rev=1206944&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/ui/proposals/inherited_windows/inherited_windows.html (added)
+++ incubator/ooo/ooo-site/trunk/content/ui/proposals/inherited_windows/inherited_windows.html Mon Nov 28 00:43:32 2011
@@ -0,0 +1,267 @@
+<!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="20011015;17113300">
+	<META NAME="CHANGED" CONTENT="20011107;9183500">
+	<STYLE>
+	<!--
+		@page { margin: 2cm }
+		H1 { margin-bottom: 0.21cm; page-break-before: auto }
+		H1.western { font-family: "Arial", sans-serif; font-size: 16pt; so-language: en-US }
+		H1.cjk { font-family: "HG Mincho Light J"; font-size: 16pt; font-weight: bold }
+		H1.ctl { font-family: "Arial Unicode MS"; font-size: 16pt; font-weight: bold }
+		H2 { margin-bottom: 0.21cm; page-break-before: auto }
+		H2.western { font-family: "Arial", sans-serif; font-size: 14pt; so-language: en-US; font-style: italic }
+		H2.cjk { font-family: "HG Mincho Light J"; font-size: 14pt; font-style: italic; font-weight: bold }
+		H2.ctl { font-family: "Arial Unicode MS"; font-size: 14pt; font-style: italic; font-weight: bold }
+	-->
+	</STYLE>
+</HEAD>
+<BODY LANG="de-DE">
+<DIV ID="Inhaltsverzeichnis1">
+	<DIV ID="Inhaltsverzeichnis1_Head">
+		<P LANG="en-US" STYLE="margin-top: 2.02cm; margin-bottom: 0.21cm; page-break-after: avoid">
+		<FONT FACE="Arial, sans-serif"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Behavior
+		of Inherited Windows</B></FONT></FONT></P>
+		<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><B>Author</B>	Christian
+		Jansen<BR>	<A HREF="mailto:Christian.Jansen@sun.com">Christian.Jansen@sun.com</A></P>
+		<P LANG="en-US" STYLE="margin-bottom: 0cm">		</P>
+		<P LANG="en-US" STYLE="margin-top: 2.02cm; margin-bottom: 0.21cm; page-break-before: always; page-break-after: avoid">
+		<FONT FACE="Arial, sans-serif"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Table
+		of Content</B></FONT></FONT></P>
+	</DIV>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>General	2</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>Issues
+	to solve	2</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>From
+	Application to Application	2</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>View
+	Menu	3</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>Toolbars	3</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>Rulers	3</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>Status
+	bar	3</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>Zoom
+	Level	4</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>Beamer	4</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>Floaters	4</B></P>
+	<P LANG="en-US" STYLE="margin-left: 0.5cm; margin-bottom: 0cm"><B>States	4</B></P>
+</DIV>
+<H1 LANG="en-US" CLASS="western"><BR><BR>
+</H1>
+<H1 LANG="en-US" CLASS="western" STYLE="page-break-before: always">Window
+relations</H1>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">General</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">One of the most important
+issues enhancing the user interface of StarOffice / OpenOffice.org is
+to create a more polished window view handling.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">E.G: If in StarOffice
+Writer a toolbar is disabled or moved to an other location than the
+default one, a new created StarOffice Calc spreadsheet will appear
+with the same disabled or moved toolbar. This could be very nice, but
+Calc is a totally different working environment. With its special
+needs.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">Issues to solve</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">In my opinion it is very
+important that we are getting more expatiation conform user
+interface.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">The following situations
+should be taken into account:</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">New (STRG + N)</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">New Other Module</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">New from start menu</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Quit and restart</P>
+</UL>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">The enumeration below
+lists the functionality we should focus on:</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">General from
+	Application to Application</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">View menu</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Toolbars</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Toolbar configuration</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Visible Toolbars</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Toolbars undocked</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Rulers</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Status bar</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Zoom</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Beamer / Floater</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">States</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Shortcuts</P>
+</UL>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">From Application to Application</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">Due to the fact that every
+module of StarOffice (which seems to be an own Application for the
+user)</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">has its own working
+environment. We should try to keep a this message as clear as
+possible, and should not blur this due states set by the user which
+takes effect in Calc also. Of coarse the exception proves the rule.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">View Menu</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">The View menu should
+provide mostly items which are mostly important for the document the
+user is working on. This could be for example <SPAN STYLE="font-weight: medium"><I>Rulers
+ON/OFF </I></SPAN>or <SPAN STYLE="font-weight: medium"><I>Text
+Boundaries ON/OFF</I></SPAN>. 
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">Permanent settings should
+be only set in Tools/Options.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: #e6e6ff">Liste
+muss definiert werden (cj)</SPAN></P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">Toolbars</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">The
+configuration of toolbars should be absolutely module independent.
+The configuration includes the following items.</SPAN></P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Docked
+	/ Undocked</SPAN></P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Vertical or
+	horizontal aligned</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Position</SPAN></P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Item
+	Order</SPAN></P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Items
+	visible/hidden</SPAN></P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Large
+	items/Small items</SPAN></P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Text
+	View</SPAN></P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Icon
+	View</SPAN></P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Text
+	&amp; Icon View</SPAN></P>
+</UL>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">
+</SPAN><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">Rulers</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Rulers
+are currently (StarOffice 6.0/ OpenOffice.org) module independent.</SPAN>
+This means if the user switches <SPAN STYLE="background: transparent">the
+ruler in Impress on or off, they will appear in Draw or vice versa.
+To refine this feature all modules should provide in Tools Option an
+option to set the metric the user wants to work with permanently. And
+the current defaults should be checked, for usefulness e. g. (HTML
+Document with cm measuring, instead of pixel).</SPAN></P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: #e6e6ff">Liste
+muss definiert werden (cj)</SPAN></P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">Status bar</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">Currently
+StarOffice heritability</SPAN> of status bar states is absolutely OK.
+If a status bar is  switched off, in a document the next opened
+document will start initially with the status bar enabled. But the
+states listed below should be checked, on usefulness of passing on
+its states.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<UL>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Zoom</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Insert/Over</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Add/Ext/Std</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">Hyperlink/Selection</P>
+</UL>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<H2 LANG="en-US" CLASS="western"><BR><BR>
+</H2>
+<H2 LANG="en-US" CLASS="western" STYLE="page-break-before: always">Zoom
+Level</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">The default Zoom
+<SPAN STYLE="background: transparent">heritability</SPAN> should be
+reassess, due to the fact that's not very useful to start with a new
+document in a absolutely unusable zoom level.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">For Example the user take
+a look at his document at a zoom of 50%. He saves the document and
+closes StarOffice / OpenOffice.org. The next day he starts with an
+empty text document which appears by default with a 50% view level.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">My proposal is to start a
+new document or spreadsheet every time with 100% zoom.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">If users want to start the
+module with a zoom level whatever, they shell have the possibility to
+set these settings in Tools-Options.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">Possible setting could be:</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><I>New zoom level</I></P>
+<P LANG="en-US" STYLE="margin-left: 0.93cm; margin-bottom: 0cm"><I>&lt;Radio&gt;
+Optimal</I></P>
+<P LANG="en-US" STYLE="margin-left: 0.93cm; margin-bottom: 0cm"><I>&lt;Radio&gt;
+Like last document</I></P>
+<P LANG="en-US" STYLE="margin-left: 0.93cm; margin-bottom: 0cm"><I>&lt;Radio&gt;
+Custom</I>  &lt;Spin control&gt;</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">Beamer</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">The Beamer should be
+replaced by own windows. To draw the content of the Beamer has
+several advantages:</P>
+<UL>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">The content looks
+	more like a real tool.</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">The window could
+	easily positioned on the desktop wherever the user wants to.</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">A own window does not
+	destroy the users current view on his document.</P>
+	<LI><P LANG="en-US" STYLE="margin-bottom: 0cm">The own window
+	solution solves the problem of passing on its states via different
+	docs, modules and after restart</P>
+</UL>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">Floaters</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">The floater configuration
+( toggle ON/OFF, position, size, docked/undocked) should be set in
+every module of StarOffice / OpenOffice.org independently. In
+addition the floaters must be positionable  on the desktop, where
+ever the user wants to.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<H2 LANG="en-US" CLASS="western">States</H2>
+<P LANG="en-US" STYLE="margin-bottom: 0cm">States toggled via
+toolbar, menus etc. shell only be set for one StarOffice /
+OpenOffice.org session and only per module. Permanent settings should
+take place only in Tools/Options.</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><SPAN STYLE="background: #e6e6ff">Liste
+muss definiert werden (cj)</SPAN></P>
+<DIV TYPE=FOOTER>
+	<P LANG="en-US" ALIGN=CENTER STYLE="margin-top: 0.5cm; margin-bottom: 0cm; border-top: 1px solid #000000; border-bottom: none; border-left: none; border-right: none; padding-top: 0.05cm; padding-bottom: 0cm; padding-left: 0cm; padding-right: 0cm">
+	 Page <SDFIELD TYPE=PAGE SUBTYPE=RANDOM FORMAT=PAGE>5</SDFIELD></P>
+</DIV>
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/inherited_windows/inherited_windows.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/print-modified-proposal.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/print-modified-proposal.html?rev=1206944&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/ui/proposals/print-modified-proposal.html (added)
+++ incubator/ooo/ooo-site/trunk/content/ui/proposals/print-modified-proposal.html Mon Nov 28 00:43:32 2011
@@ -0,0 +1,178 @@
+<!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="AUTHOR" CONTENT="Lutz H&ouml;ger">
+	<META NAME="CREATED" CONTENT="20010921;13214600">
+	<META NAME="CHANGEDBY" CONTENT="Oliver Specht">
+	<META NAME="CHANGED" CONTENT="20010921;13422999">
+	<STYLE>
+	<!--
+		@page { size: 21cm 29.7cm; margin: 2cm }
+		P { margin-bottom: 0.21cm; font-family: "SunSerif-Regular" }
+		H1 { margin-bottom: 0.21cm; font-family: "SunSans-Heavy"; font-size: 16pt; font-weight: medium }
+		H2 { margin-bottom: 0.21cm; font-family: "SunSans-Heavy"; font-size: 14pt; font-style: normal; font-weight: medium }
+	-->
+	</STYLE>
+</HEAD>
+<BODY>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; font-weight: medium; page-break-after: avoid">
+<FONT FACE="SunSans-Heavy"><FONT SIZE=5>Printing and The &quot;document
+modified&quot; Status</FONT></FONT></P>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; font-style: normal; page-break-after: avoid">
+<FONT FACE="SunSans-Demi"><FONT SIZE=4>Specification Proposal<BR>Lutz
+H&ouml;ger, Matthias Breuer, 09/21/2001</FONT></FONT></P>
+<H1>Problem</H1>
+<P>When a document gets opened, printed and closed, StarOffice asks
+whether the changes should be saved. Many users don't understand this
+and &#150; depending on the current work situation &#150; sometimes
+even feel uncertain about which decision they should make (Have I
+changed anything erroneously? Didn't I save my latest changes? ...)</P>
+<H1>Background</H1>
+<P>When a StarOffice application, like Writer, receives the &#147;print&#148;
+command, it performs a couple of actions before it actually prints
+the document:</P>
+<UL>
+	<LI><P>Updating the document info (File &#150; Properties) and set
+	the &#147;last printed&#148; date.</P>
+	<LI><P>Updating the fields in the document</P>
+	<LI><P>Possibly reformatting the whole document because the printer
+	driver used for printing is different from the printer driver the
+	document was created for originally.</P>
+</UL>
+<P>As it takes quite some engineering effort to find out whether or
+not these preparations actually change the document, the &#147;modified&#148;
+flag is set by default, as soon as an application starts the print
+preparations.</P>
+<P>Of course it would be a better solution, if the applications knew
+whether changes were triggered by printing or by other actions. This
+would also give us the chance to change the warning message that's
+displayed when an unsaved, modified document gets closed. But the
+engineering cost to distinguish between the source of the changes is
+very high (first incomplete estimate: 1 week planning, at least 2
+weeks of implementation, additional time for testing), and we don't
+feel like solving this problem is worth the cost.</P>
+<H1>Solution</H1>
+<P>As an alternative,more simple approach, we should offer an option
+that suppresses the modification of the &#147;document modified&#148;
+flag by the print process. This option would not be active by
+default, but if a user feels confused by the current behavior, he can
+choose to activate it. 
+</P>
+<P>Behind the scenes, the status of the &#147;document modified&#148;
+flag would be saved as soon as the printing process gets triggered
+and it would be reset to the saved value after printing has finished.
+Of course the changes mentioned above would still be made, it would
+be just the status of the document that's &#147;locked&#148; against
+changes. If the document has been modified before it was printed, the
+status after printing would be &#147;modified&#148;. If it has just
+been opened with no automatic changes (like triggered by macros or
+updated links), it would show the status &#147;unmodified&#148; after
+printing. If the user subsequently changes the document, the status
+would change accordingly, i.e. Switch to &#147;modified&#148;.</P>
+<H2>There are some disadvantages to this solution:</H2>
+<UL>
+	<LI><P>If the user doesn't save the document after printing, the
+	changes will be lost, so the printed document is &#147;newer&#148;
+	than the saved document<BR>(This would also be the case if the user
+	decides not to save the document when asked about this)</P>
+	<LI><P>The &#147;last printed&#148; document info field would not
+	contain the correct value<BR>(same as above; today the field also
+	doesn't get updated if a document is printed from the system shell
+	(like from the context menu in Windows Explorer))</P>
+</UL>
+<P>I consider these disadvantages to be a moderate price that the
+user pays for his convenience. And anyway, we would not make this
+setting the default, so the user himself would be responsible for
+changing this behavior.</P>
+<H2>How does the user learn about the new feature? 
+</H2>
+<P>As described in the background section, we do not want to
+distinguish between general changes and changes triggered by the
+printing process. So we can't modify the warning message box that
+asks the user if his changes should be saved, because we don't know
+which changes caused this box to appear. 
+</P>
+<P>An alternative way to inform the user is to display the Help Agent
+together with the message box. The Help Agent leads the user to a
+description of this feature in our help system. 
+</P>
+<H2>Further specification details</H2>
+<UL>
+	<LI><P>Add an option to Tools &#150; Options &#150; General<BR>This
+	is maybe not the most natural option page for this setting, but due
+	to other dialogs being already &#147;full&#148;, this is the best
+	compromise for this setting.</P>
+	<LI><P>The option should be called: Printing sets &#147;document
+	modified&#148; status. It should be preceded by a separator line
+	labeled &#147;Document status&#148;<BR>In German: Drucken setzt
+	&#147;Dokument ge&auml;ndert&#148; Status (separator label:
+	Dokumentstatus)</P>
+</UL>
+<H1>Action Items</H1>
+<TABLE WIDTH=803 BORDER=0 CELLPADDING=5 CELLSPACING=0>
+	<COL WIDTH=535>
+	<COL WIDTH=248>
+	<TR VALIGN=TOP>
+		<TD WIDTH=535>
+			<P>Propose specification</P>
+		</TD>
+		<TD WIDTH=248>
+			<P>Lutz H&ouml;ger</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=535>
+			<P>Describe the feature and maybe the technical background</P>
+		</TD>
+		<TD WIDTH=248>
+			<P>Frank Peters</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=535>
+			<P>Optionally save and restore the document status when printing</P>
+		</TD>
+		<TD WIDTH=248>
+			<P>Mathias Bauer</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=535>
+			<P>Implement Tools &#150; Options UI</P>
+		</TD>
+		<TD WIDTH=248>
+			<P>Oliver Specht</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=535>
+			<P>Implement trigger for Help Agent</P>
+		</TD>
+		<TD WIDTH=248>
+			<P>Oliver Specht</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=535>
+			<P>Write feature e-mail</P>
+		</TD>
+		<TD WIDTH=248>
+			<P>Oliver Specht</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=535>
+			<P>Translate UI and documentation</P>
+		</TD>
+		<TD WIDTH=248>
+			<P>Rafaella Braconi</P>
+		</TD>
+	</TR>
+</TABLE>
+<P><BR><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/print-modified-proposal.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_final.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_final.html?rev=1206944&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_final.html (added)
+++ incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_final.html Mon Nov 28 00:43:32 2011
@@ -0,0 +1,393 @@
+<html>
+<head>
+<title>Untitled Document</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body bgcolor="#FFFFFF" text="#000000">
+<h2 style="page-break-before: always"><font size="3" style="font-size: 16pt" face="Arial, Helvetica, sans-serif">Proposal 
+  of StarOffice Toolbar &amp; Menu redesign.</font></h2>
+<p><font face="Arial, Helvetica, sans-serif" size="3"><br>
+  </font></p>
+<p><font size="2" face="Arial, Helvetica, sans-serif">Christian Jansen</font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2"><a href="mailto:Christian.Jansen@sun.com">Christian.Jansen@sun.com</a></font></p>
+<p><font size="2" face="Arial, Helvetica, sans-serif">OpenOffice.org</font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="3"><br>
+  </font></p>
+<p>&nbsp;</p>
+<p>&nbsp;</p>
+<p>&nbsp;</p>
+<p>&nbsp;</p>
+<p>&nbsp;</p>
+<p>&nbsp;</p>
+<div id="Inhaltsverzeichnis1"> 
+  <div id="Inhaltsverzeichnis1_Head"> 
+    <p style="margin-left: 0cm; margin-top: 0.42cm; margin-bottom: 0.21cm; page-break-before: always; page-break-after: avoid"> 
+      <font size="3" style="font-size: 16pt" face="Arial, Helvetica, sans-serif"><b>Table 
+      of Content</b></font></p>
+  </div>
+  <p style="page-break-before: auto">&nbsp;</p>
+  <p style="page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2"><a href="#Introduction"><b>Introduction</b></a>	
+    </font></p>
+  <p style="page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2"><b><a href="#Toolbars">Toolbars</a></b>	
+    </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Toolbars 
+    Elements </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Dock 
+    / Undock functionality </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Undocked 
+    Toolbars </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Customizing 
+    Toolbars </font></p>
+  <p style="page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2"><b><a href="#ToolbarIcons">Toolbar 
+    Icons</a></b> </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">General	
+    </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Cultural 
+    Impact </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Icon 
+    Size </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Icon 
+    Feedback </font></p>
+  <p style="page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2"><b><a href="#CommonToolbarButtons">Common 
+    Toolbar Buttons</a></b> </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">General 
+    Toolbar Icons </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">16 
+    Color Toolbar Icons </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">256 
+    Color Toolbar Icons </font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">32 
+    bit Toolbar Icons</font></p>
+  <p style="page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2"><b><a href="#Menues">Menues</a></b></font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Menu 
+    Titles</font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Menu 
+    Parts</font></p>
+  <p style="margin-left: 1cm; page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2">Item 
+    Groups in Menues</font></p>
+  <p style="page-break-before: auto"><font face="Arial, Helvetica, sans-serif" size="2"><b><a href="#PossibleStarOfficeOpenOfficeredesign">Possible 
+    StarOffice / OpenOffice redesign</a></b> </font></p>
+</div>
+<h2><font face="Arial, Helvetica, sans-serif"><br>
+  <br>
+  </font></h2>
+<h3 style="page-break-before: always"><font face="Arial, Helvetica, sans-serif"><a name="Introduction"></a>Introduction</font></h3>
+<p><font face="Arial, Helvetica, sans-serif" size="2">This proposal describes 
+  a possible user interface redesign for OpenOffice.org / StarOffice 6.X and above. 
+  The following enumeration lists the proposed items:</font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2"><br>
+  </font></p>
+<ul>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Menus</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Toolbars</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Icons</font></p>
+</ul>
+<p><font face="Arial, Helvetica, sans-serif" size="2"><br>
+  </font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">All of the proposed topics 
+  have to be get more in detail, but this document is more like a first step how 
+  we could move on. This proposal has to be completed by an accessibility and 
+  controls chapter to each topic.The screen shot will replace by English ones, 
+  but I think it is not so important for understanding the context.</font></p>
+<h2 style="page-break-before: always">&nbsp;</h2>
+<h2 style="page-break-before: always">&nbsp;</h2>
+<h2 style="page-break-before: always">&nbsp;</h2>
+<h2 style="page-break-before: always">&nbsp;</h2>
+<h2 style="page-break-before: always">&nbsp;</h2>
+<h2 style="page-break-before: always">&nbsp;</h2>
+<h2 style="page-break-before: always">&nbsp;</h2>
+<h2 style="page-break-before: always">&nbsp;</h2>
+<h2 style="page-break-before: always"><font face="Arial, Helvetica, sans-serif">Toolbars<a name="Toolbars"></a></font></h2>
+<p><font face="Arial, Helvetica, sans-serif" size="2">The intended purpose of 
+  toolbars is that they provide a strong visual access to items like things on 
+  a desk.The toolbars should provide a easy to use and self explaining user interface 
+  and item.Toolbar items are accessible via mouse, in addition they should provide 
+  access via keyboard shortcuts.Toolbar items must always provide a ToolTip. Toolbars 
+  should provide a flexible and configurable or customizable interface. If this 
+  is given the user could create his own world to solve his tasks.</font></p>
+<p><img src="Toolbars_And_Menue_Proposal_sxw_m3004d4b9.gif" width="426" height="201"></p>
+<p><font face="Arial, Helvetica, sans-serif"><font size=2 style="font-size: 9pt"><b>Figure 
+  1 StarOffice 6.0 Toolbars</b></font></font></p>
+<h3>&nbsp;</h3>
+<h3><font face="Arial, Helvetica, sans-serif">Toolbars Elements</font></h3>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Each toolbar includes a 
+  grip handle to arrange the toolbar. A toolbar could contain the following items<br>
+  listed below (Figure 2).</font></p>
+<ul>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Icons</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Text</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Icons &amp; Text combinations</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Icons with drop down 
+      function</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Buttons</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Controls like Combo 
+      Boxes</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Grip Handles</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Separators</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Drop downs for toolbar 
+      configuration</font></p>
+</ul>
+<p><img src="Toolbars_And_Menue_Proposal_sxw_4dc81e47.gif" width="427" height="202"></p>
+<p><font face="Arial, Helvetica, sans-serif"><font size=2 style="font-size: 9pt"><b>Figure 
+  2 Toolsbars with toolbar grip handle</b></font></font></p>
+<p>&nbsp;</p>
+<h3><font face="Arial, Helvetica, sans-serif">Dock / Undock Functionality</font></h3>
+<p><font face="Arial, Helvetica, sans-serif" size="2">To enable an easy to use 
+  undock functionality for toolbars, a toolbar grip handle on the left end of 
+  the toolbar. If the use wants to move the toolbar he could drag it easily by 
+  pressing the left mouse button and drag over the grip handle of the toolbar.</font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">If the new location is within 
+  the hot zone of an other toolbar edge, the toolbar should be docked at the edge 
+  when the user releases the mouse button. Otherwise if the new location is not 
+  within the hot zone of a edge the toolbar should be displayed as palette window. 
+  <br>
+  While moving the toolbar a visual feedback should be given (Figure 3). If the 
+  user moves the toolbar into a hot zone of a docking location only the outline 
+  of the bar should be visualized. While moving over non docking are like the 
+  document area for example change the outline into a bolder dotted line to visualize 
+  a modification.</font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Providing support for toolbar 
+  location change makes it necessary to preserve the current position and size. 
+  </font></p>
+<p><font face="Arial, Helvetica, sans-serif"><img src="Toolbars_And_Menue_Proposal_sxw_7f0a8893.gif" name="Grafik17" align=middle width=426 height=283 border=0></font></p>
+<p><font face="Arial, Helvetica, sans-serif"><font size=2 style="font-size: 9pt"><b>Figure 
+  3</b> Toolbar move by a pointer</font> </font></p>
+<h3 style="page-break-before: always">&nbsp;</h3>
+<h3 style="page-break-before: always"><font face="Arial, Helvetica, sans-serif">Undocked 
+  Toolbars</font></h3>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Undocked toolbars are needed 
+  to provide context sensitive tools.E.G: The user inserts a picture into a text 
+  document. After inserting the picture an undocked toolbar appears with an optimal 
+  set of items (Figure 4 &amp; 5).</font></p>
+<p><font face="Arial, Helvetica, sans-serif"><img src="Toolbars_And_Menue_Proposal_sxw_13b95450.gif" name="Grafik24" align=absmiddle width=80 height=259 border=0></font></p>
+<p><font face="Arial, Helvetica, sans-serif"><img src="Toolbars_And_Menue_Proposal_sxw_m73a1e904.gif" name="Grafik23" align=absmiddle width=588 border=0></font></p>
+<p><font face="Arial, Helvetica, sans-serif"><font size=2 style="font-size: 9pt"><b>Figure 
+  4 &amp; 5</b> Same toolbar vertical and horizontal</font> </font></p>
+<p><font face="Arial, Helvetica, sans-serif"> </font></p>
+<h3><font face="Arial, Helvetica, sans-serif">Customizing Toolbars</font></h3>
+<p><font face="Arial, Helvetica, sans-serif" size="2">A toolbar band (Figure 5)could 
+  be collapsed or expanded by clicking with the mouse pointer on the triangle 
+  located on the right end of the toolbar group. Clicking on the triangle provides 
+  a collapse of the toolbar group by one group of items (a group is defined by 
+  items between two separators). </font></p>
+<p><font face="Arial, Helvetica, sans-serif"><img src="Toolbars_And_Menue_Proposal_sxw_7bca9a68.gif" name="Grafik20" align=middle width=410 border=0></font></p>
+<p><font face="Arial, Helvetica, sans-serif"><font size=2 style="font-size: 9pt"><b>Figure 
+  5</b> A toolbar band with three toolbar groups.</font></font></p>
+<p>&nbsp;</p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">After a part of the toolbar 
+  is hidden the separators between two groups changes to a control which enables 
+  the user to collapse the left group or expand the currently hidden group (Figure 
+  6).</font></p>
+<p><font face="Arial, Helvetica, sans-serif"><img src="Toolbars_And_Menue_Proposal_sxw_m199fc29d.gif" name="Grafik21" align=absmiddle width=410 border=0></font></p>
+<p><font face="Arial, Helvetica, sans-serif"><font size=2 style="font-size: 9pt"><b>Figure 
+  6</b> Toolbar with a hidden group.</font></font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">To expand or collapse groups 
+  it is even possible to go via context menu provided by the toolbar bands. This 
+  menu is stays visible the hole time of editing the state of the items. The menu 
+  will be closed after clicking out side the menu location.</font></p>
+<p><font face="Arial, Helvetica, sans-serif"><img src="Toolbars_And_Menue_Proposal_sxw_50d7332c.gif" name="Grafik22" align=absmiddle width=410 border=0></font></p>
+<p><font face="Arial, Helvetica, sans-serif"><font size=2 style="font-size: 9pt"><b>Figure 
+  7</b> Toolbar with context menu</font></font></p>
+<h2><font face="Arial, Helvetica, sans-serif">Toolbar Icons<a name="ToolbarIcons"></a></font></h2>
+<h3><font face="Arial, Helvetica, sans-serif">General</font></h3>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Icons should provide people 
+  easily access to items. Like tools on a desk, for example pens, rules a rubber 
+  gum and so on. One of the most important things is consistency in design of 
+  these images. They should be in scale, orientation and color consistent. The 
+  icons must fit homogeny into its environment.</font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Each icon should be easily 
+  and quickly distinguishable from the other item in the toolbar. </font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">In addition they have to 
+  provide a sufficient contrast in the image to ensure that different parts could 
+  easily identify the elements. In this context icons should not match in similarity 
+  with common controls.</font></p>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<h3><font face="Arial, Helvetica, sans-serif">Cultural Impact</font></h3>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Cultural impacts should 
+  always considered in icon design. Critical icons should reviewed as early as 
+  possible in the development cycle of StarOffice. The problem is that metaphors, 
+  symbols or simple image may not have the same meaning around the world. Also 
+  the use of letters and words should be avoid whenever possible.</font></p>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<h3><font face="Arial, Helvetica, sans-serif">Icon Size</font></h3>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Currently StarOffice uses 
+  the size 16 pixels by 15 pixels (width by height) and 26 px by 25 px, for the 
+  large ones. These formats should changed to a new format. I would recommend 
+  16 by 16 for the small ones and 32 by 32 for the large. The the large ones should 
+  provide a transparent border, with a minimum of 3 pixels to each side.</font></p>
+<p><font face="Arial, Helvetica, sans-serif"><img src="Toolbars_And_Menue_Proposal_sxw_m37e4d406.gif" name="Grafik10" align=absmiddle width=445 border=0></font></p>
+<p><font style="font-size: 9pt" face="Arial, Helvetica, sans-serif" size="2"><b>Figure 
+  8</b> StarOffice icon size</font></p>
+<p><font face="Arial, Helvetica, sans-serif"> </font></p>
+<h3><font face="Arial, Helvetica, sans-serif">Icon Feedback</font></h3>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Currently the enabled items 
+  in the toolbars are sometimes hard to identify (Figure 9). A flat rectangular 
+  in prominent color and a filled area (same color like the border only with 90% 
+  transparency) helps a lot to identify the enabled items (Figure 11). To support 
+  a better tracking feedback when the mouse pointer is over the toolbar item a 
+  highlight area with a border and a drop shadow for the image. Provides a great 
+  feedback. Compare Figure 10 &amp; 12 for this. In addition the hot (mouse over) 
+  state should have a slightly increased saturation.</font></p>
+<div align="left"> </div>
+<p>&nbsp;</p>
+<table width="696" border="0" cellspacing="2" cellpadding="2">
+  <tr>
+    <td><img src="Toolbars_And_Menue_Proposal_sxw_2986e9ef.gif" name="Grafik11" align=LEFT width=238 height=44 border=0></td>
+    <td><img src="Toolbars_And_Menue_Proposal_sxw_m59760bec.gif" name="Grafik13" align=LEFT width=238 height=44 border=0></td>
+  </tr>
+  <tr>
+    <td><font size="2" face="Arial, Helvetica, sans-serif"><b>Figure 9</b> StarOffice 
+      6.0 Toolbar with a enabled item.</font> </td>
+    <td><font style="font-size: 9pt" size="2" face="Arial, Helvetica, sans-serif"><b>Figure 
+      10</b> StarOffice 6.0 Toolbar with hot (mouse over) item.</font></td>
+  </tr>
+  <tr>
+    <td><img src="Toolbars_And_Menue_Proposal_sxw_5814edd2.gif" name="Grafik12" align=LEFT width=238 height=44 border=0></td>
+    <td><img src="Toolbars_And_Menue_Proposal_sxw_33d81b2e.gif" name="Grafik14" align=LEFT width=238 height=44 border=0></td>
+  </tr>
+  <tr>
+    <td><font style="font-size: 9pt" size="2" face="Arial, Helvetica, sans-serif"><b>Figure 
+      11 </b>Proposal of an enabled toolbar item.</font></td>
+    <td><font style="font-size: 9pt" size="2"><b><font face="Arial, Helvetica, sans-serif">Figure 
+      12</font></b><font face="Arial, Helvetica, sans-serif"> Proposal of a new 
+      mouse over feedback.</font></font></td>
+  </tr>
+</table>
+<h2>&nbsp;</h2>
+<h2>&nbsp;</h2>
+<h2><font face="Arial, Helvetica, sans-serif">Common Toolbar Buttons<a name="CommonToolbarButtons"></a></font></h2>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Consistent use of common 
+  tool images allows the user a better transfer of learning and skills from product 
+  to product. These images may only be used like in the table below.</font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2"><br>
+  </font></p>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<h3 style="page-break-before: always"><font face="Arial, Helvetica, sans-serif">General 
+  Toolbar Icons</font></h3>
+<ul>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Use as many common toolbar 
+      images as possible</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Use the same hue and 
+      color saturation.</font></p>
+</ul>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<h3><font face="Arial, Helvetica, sans-serif">16 Color Toolbar Icons</font></h3>
+<ul>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">The Windows 16 color 
+      palette must be used .</font></p>
+</ul>
+<ul>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">The images shell flat 
+      in appearance may be with little dimension or shading.</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">The images must support 
+      1-bit transparency. The recommended color is Magenta (R: 255 G:0 B: 255, 
+      Hex: FF00FF)</font></p>
+    <p></p>
+</ul>
+<h3><font face="Arial, Helvetica, sans-serif">256 Color Toolbar Icons</font></h3>
+<ul>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">The Windows halftone 
+      palette must be used.</font></p>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Image should be more 
+      dimensional. The light source should be placed in the upper left. Shade 
+      if needed and/or appropriate.</font></p>
+</ul>
+<ul>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">The images must support 
+      1-bit transparency. The recommended color is Magenta (R: 255 G:0 B: 255, 
+      Hex: FF00FF)</font></p>
+</ul>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<h3><font face="Arial, Helvetica, sans-serif">32 Bit Toolbar Icons</font></h3>
+<ul>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">The images are 24bit 
+      in color depth with an 8bit alpha channel. This allows images with smoothed 
+      edges which could blend to every kind of background. (BMP/DIB and 24-bit 
+      with Alpha or PNG )</font></p>
+</ul>
+<ul>
+  <li> 
+    <p><font face="Arial, Helvetica, sans-serif" size="2">Image should be more 
+      dimensional. The light source should be placed in the upper left. Shade 
+      if needed and/or appropriate.</font></p>
+</ul>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<h2><font face="Arial, Helvetica, sans-serif"><br>
+  <br>
+  </font></h2>
+<h2 style="page-break-before: always"><font face="Arial, Helvetica, sans-serif">Menues<a name="Menues"></a></font></h2>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Menus are lists of items, 
+  commands, attributes or states from which the user could choose from. Menus 
+  are based on the interface principle of &#147;see and point&#148;. The most 
+  important advantage of menus is that: People do not have to remember command 
+  or visual items, because they could choose from a list of available option at 
+  any time they want.</font></p>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<h3><font face="Arial, Helvetica, sans-serif">Menu Titles</font></h3>
+<p><font face="Arial, Helvetica, sans-serif" size="2">Menu titles should be one 
+  word that describes easily the expected items.</font></p>
+<p><font face="Arial, Helvetica, sans-serif"><img src="Toolbars_And_Menue_Proposal_sxw_m6c290b05.gif" name="Grafik18" align=absmiddle width=461 height=60 border=0></font></p>
+<p><font face="Arial, Helvetica, sans-serif"><font size=2 style="font-size: 9pt"><span style="font-style: normal"><b>Figure 
+  13 </b>The menu bar</span></font></font></p>
+<h3><font face="Arial, Helvetica, sans-serif">Menu Parts</font></h3>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">The parts of a menu are 
+  a title, items, separators, submenu indicators, keyboard accelerators and if 
+  needed a icon in front of the item.</font></p>
+<p><font face="Arial, Helvetica, sans-serif"><img src="Toolbars_And_Menue_Proposal_sxw_48239db1.gif" name="Grafik19" align=absmiddle width=400 height=349 border=0></font></p>
+<p><font face="Arial, Helvetica, sans-serif"> </font></p>
+<h3><font face="Arial, Helvetica, sans-serif">Item Groups in Menues</font></h3>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2">On of the most important 
+  aspect of adding items into menus is to group the items logically.In general 
+  the most important or frequently used item should be the first item of a group 
+  or the menu.How many separators are used in a menu is a aesthetic and only partly 
+  a usability decision.But in general too many separators are confusing and make 
+  reading more difficult.</font></p>
+<p><font face="Arial, Helvetica, sans-serif" size="2"><br>
+  </font></p>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<p><font face="Arial, Helvetica, sans-serif"><br>
+  </font></p>
+<h2 style="page-break-before: always"><font face="Arial, Helvetica, sans-serif">Possible 
+  StarOffice / OpenOffice redesign<a name="PossibleStarOfficeOpenOfficeredesign"></a></font></h2>
+<h2 style="page-break-before: always"><font face="Arial, Helvetica, sans-serif"><img src="ui.gif" name="Grafik1" align=absmiddle border=0></font></h2>
+<p>&nbsp;</p>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_final.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_13b95450.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_13b95450.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_13b95450.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_2986e9ef.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_2986e9ef.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_2986e9ef.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_33d81b2e.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_33d81b2e.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_33d81b2e.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_48239db1.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_48239db1.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_48239db1.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_4dc81e47.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_4dc81e47.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_4dc81e47.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_50d7332c.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_50d7332c.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_50d7332c.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_5814edd2.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_5814edd2.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_5814edd2.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_7bca9a68.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_7bca9a68.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_7bca9a68.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_7f0a8893.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_7f0a8893.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_7f0a8893.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m199fc29d.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m199fc29d.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m199fc29d.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m3004d4b9.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m3004d4b9.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m3004d4b9.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m37e4d406.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m37e4d406.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m37e4d406.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m59760bec.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m59760bec.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m59760bec.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m6c290b05.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m6c290b05.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m6c290b05.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m73a1e904.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m73a1e904.gif?rev=1206944&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/Toolbars_And_Menue_Proposal_sxw_m73a1e904.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

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

Propchange: incubator/ooo/ooo-site/trunk/content/ui/proposals/toollbars/ui.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif



Mime
View raw message