incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r799253 [2/16] - in /websites/staging/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:05:43 GMT
Added: websites/staging/ooo-site/trunk/content/framework/drafts/documents.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/drafts/documents.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/drafts/documents.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,251 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+  <title>Documents</title>
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<center>
+<table bgcolor="#f0f0f0" border="0" cellpadding="10" cellspacing="0" width="100%">
+
+  <col width="88*"> <col width="107*"> <col width="61*"> <tbody>
+
+    <tr>
+
+      <td colspan="3" bgcolor="#00315a" width="100%">
+      <p align="center"><font color="#ffffff"><comment title=" 1. row: &quot;Documentation&quot; 100% with " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 1. row: "Documentation" 100% with --></comment><font face="Arial, Helvetica"><font size="2"><b>Documents<comment title=" 2. row: &quot;Title&quot; &amp; &quot;Description&quot; &amp; &quot;Author&quot; 40/40/20% for every column " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 2. row: "Title" & "Description" & "Author" 40/40/20% for every column --></comment></b></font></font></font></p>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td bgcolor="#99ccff" width="34%">
+      <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Title
+      </b></font></font></font> </p>
+
+      </td>
+
+      <td bgcolor="#99ccff" width="42%">
+      <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Description
+      </b></font></font></font> </p>
+
+      </td>
+
+      <td bgcolor="#99ccff" width="24%">
+      <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Author<comment title=" 3. row: first content line dialog proposal " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 3. row: first content line dialog proposal --></comment></b></font></font></font></p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0" width="34%">
+      <p align="left"><a href="../documentation/filters/index.html"><font size="2"><font face="Arial, Helvetica">Implementation and registrations of
+filtes</font></font></a> </p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="42%">
+      <p align="left"><font face="Arial, Helvetica"><font size="2">How to implement import or export filters and
+document loaders for OpenOffice.org</font></font></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Andreas Schl&uuml;ns <br>
+
+      <a href="mailto:andreas.schluens@sun.com">andreas.schluens@sun.com
+      </a></font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="34%">
+      <p><font size="2"><font face="Arial, Helvetica"><a href="../documentation/mimetypes/mimetypes.html">Mime Content
+Types used in OpenOffice</a> </font></font> </p>
+
+      </td>
+
+      <td width="42%">
+      <p><font face="Arial, Helvetica"><font size="2">Description of the Mime Content Types used in
+OpenOffice and in StarOffice 4.x/5.x</font></font></p>
+
+      </td>
+
+      <td width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Mikhail Voitenko<br>
+
+      <a href="mailto:mikhail.voitenko@sun.com">mikhail.voitenko@sun.com</a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="34%">
+      <p><font size="2"><font face="Arial, Helvetica"><a href="../documentation/filterui/index.html">Java application
+"FilterUI"</a> </font></font> </p>
+
+      </td>
+
+      <td width="42%">
+      <p><font face="Arial, Helvetica"><font size="2">Application to administrate filter configuration
+data of office and demonstrate using of filter api</font></font></p>
+
+      </td>
+
+      <td width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Andreas Schl&uuml;ns<br>
+
+      <a href="mailto:andreas.schluens@sun.com">andreas.schluens@sun.com</a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="34%">
+      <p><a href="../documentation/devmanual/draft.sxw"><font size="2"><font face="Arial, Helvetica">Preliminary
+developer documention for the framework module</font></font></a></p>
+
+      </td>
+
+      <td width="42%">
+      <p><font size="2"><font face="Arial, Helvetica">Some chapters of the upcoming
+developers manual in draft state. Some chapters are still not finished
+and will be added later.<br>
+
+Currently no diagrams and no source code snippets are provided. Java
+example code that illustrates the outlined concepts can be found in the
+      <a href="http://api.openoffice.org/source/browse/api/devmanual/OfficeDev/samples/DesktopEnvironment/">api
+project.</a></font></font></p>
+
+      <p><font size="2"><font face="Arial, Helvetica">You must reckon on this
+documentation being changed a little bit until the final release.<br>
+
+The current office builds still behave a little bit different than
+outlined in the documentation. These differences and also some known
+bugs are documented in <a href="../documentation/devmanual/bugs.sxw">a
+separated file</a>.</font></font></p>
+
+      </td>
+
+      <td width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Mathias Bauer<br>
+
+      <a href="mailto:mathias.bauer@sun.com">mathias.bauer@sun.com</a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="34%">
+      <p><a href="../documentation/others/index.html"><font size="2"><font face="Arial, Helvetica">Documentation
+collection for the framework module</font></font></a></p>
+
+      </td>
+
+      <td width="42%">
+      <p><font face="Arial, Helvetica"><font size="2">Its the first draft of some documentations for the
+framework module which describes the supported features and some
+internal mechanism of it. </font></font> </p>
+
+      </td>
+
+      <td width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Andreas Schl&uuml;ns<br>
+
+      <a href="mailto:andreas.schluens@sun.com">andreas.schluens@sun.com</a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="34%">
+      <p><a href="../scripting/index.html"> <font size="2"><font face="Arial, Helvetica">Scripting
+Framework </font></font> </a></p>
+
+      </td>
+
+      <td width="42%">
+      <p> <font face="Arial, Helvetica"><font size="2"> This is the home page of the Scripting Framework
+for OpenOffice.org. </font></font> </p>
+
+      </td>
+
+      <td width="24%">
+      <p align="right"> <font size="2"><font face="Arial, Helvetica">Andreas Bregas<br>
+
+      <a href="mailto:andreas.bregas@sun.com">andreas.bregas@sun.com</a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+  </tbody>
+</table>
+
+</center>
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/drafts/modules.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/drafts/modules.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/drafts/modules.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,235 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+
+  <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
+  <title>Modules</title>
+
+
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+
+<table style="width: 100%;" border="0" cellpadding="4" cellspacing="0">
+
+  <tbody>
+
+    <tr>
+
+      <td style="width: 1%; vertical-align: top;" rowspan="9">
+      <p></p>
+
+      <p><br>
+
+      </p>
+
+      </td>
+
+      <td style="background-color: rgb(0, 49, 90);" colspan="2">
+      <p align="center"><font color="#ffffff"><font face="Arial, Helvetica"><font size="2"><b>Modules
+in Application Framework Project </b></font></font></font>
+      </p>
+
+      </td>
+
+      <td rowspan="9" style="width: 1%; vertical-align: top;">
+      <p><br>
+
+      </p>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <th style="background-color: rgb(153, 204, 255); width: 15%;">
+      <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Module
+      </b></font></font></font> </p>
+
+      </th>
+
+      <th style="background-color: rgb(153, 204, 255); width: 85%;">
+      <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Function
+      </b></font></font></font> </p>
+
+      </th>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td style="background-color: rgb(240, 240, 240);">
+      <p><tt><tt>sfx2</tt></tt></p>
+
+      </td>
+
+      <td style="background-color: rgb(240, 240, 240);">
+      <p><tt>The SFX is the core of the framework. It is
+built on the "Template" pattern and so it is comparable to the
+Microsoft Foundation Classes (MFC) library. This means that it uses
+base classes for documents and views to build up the common behaviour (
+the "framework" ) of all components. This covers state and interaction
+of the components. The specialized behaviour of the individual
+components like Writer, Calc etc. is customized through classes derived
+from the base classes. <br>
+
+There are other helper classes also. For example, helper classes are
+used to execute commands, for example commands from a toolbar button.
+These helper classes also communicate state information. There are also
+other helper classes for building the user interface and the object
+persistance.</tt></p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0">
+      <p><tt><tt>res</tt></tt></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="61%">
+      <p><tt>Contains typical resource files such as
+bitmaps, icons, and cursor files. </tt> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0">
+      <p><tt><tt>idl</tt></tt></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="61%">
+      <p><tt>All SFX based components contain Interface
+definition Language (IDL) files. These files are compiled with the IDL
+compiler for the SFX framework. It does not generate code, but
+generates definition ( header ) files used in the components code.</tt></p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0">
+      <p><tt><tt>framework</tt></tt></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="61%">
+      <p><tt>Integrates the application components in
+different environments like a desktop or a browser plugin etc. It
+integrates SFX based components as well as other components not based
+on SFX. The integration base is the frame package of the OpenOffice
+API. <br>
+
+The framework module is also responsible for the content detection and
+content activation.</tt></p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0">
+      <p><tt><tt>desktop</tt></tt></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="61%">
+      <p><tt>The code for the office executable, based on
+the offmgr module.</tt></p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0">
+      <p><tt><tt>DocumentProperties</tt></tt></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="61%">
+      <p><tt>Makes properties of the documents available
+through OpenOffice API.<comment title=" Page End " xmlns="http://disruptive-innovations.com/zoo/nvu"><!-- Page End --></comment><comment title=" footer " xmlns="http://disruptive-innovations.com/zoo/nvu"><!-- footer --></comment></tt></p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0">
+      <p><tt><tt>scripting</tt></tt></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="61%">
+      <p><tt><tt>Scripting Framework which allows
+OpenOffice.org to be scripted in multiple languages. You can view the
+source code <a href="../source/browse/framework/scripting">here</a>,
+and the module home page <a href="../scripting/index.html">here</a>.
+      </tt></tt></p>
+
+      </td>
+
+    </tr>
+
+  </tbody>
+</table>
+
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/drafts/proposals.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/drafts/proposals.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/drafts/proposals.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,275 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+  <title>Proposals</title>
+
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+<h3>Proposals</h3>
+
+<center>
+<table style="background-color: rgb(255, 255, 255); width: 100%;" border="0" cellpadding="10" cellspacing="0">
+
+  <col width="97*"> <col width="98*"> <col width="61*"> <tbody>
+
+    <tr>
+
+      <td colspan="3" bgcolor="#00315a" width="100%">
+      <p align="center"><font color="#ffffff"><comment title=" 1. row: &quot;Documentation&quot; 100% with " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 1. row: "Documentation" 100% with --></comment><font face="Arial, Helvetica"><font size="2"><b>Proposals<comment title=" 2. row: &quot;Title&quot; &amp; &quot;Description&quot; &amp; &quot;Author&quot; 40/40/20% for every column " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 2. row: "Title" & "Description" & "Author" 40/40/20% for every column --></comment></b></font></font></font></p>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="background-color: rgb(153, 204, 255); width: 30%;">
+      <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Title
+      </b></font></font></font> </p>
+
+      </td>
+
+      <td style="background-color: rgb(153, 204, 255); width: 50%;">
+      <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Description
+      </b></font></font></font> </p>
+
+      </td>
+
+      <td style="background-color: rgb(153, 204, 255); width: 20%;">
+      <p align="center"><font color="#00315a"><font face="Arial, Helvetica"><font size="2"><b>Author<comment title=" 3. row: first content line dialog proposal " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 3. row: first content line dialog proposal --></comment></b></font></font></font></p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/keyboard_configuration/Proposal_Keyboard_shortcuts.html"><font size="2"><font face="Arial, Helvetica">New keyboard shortcut configuration. </font></font></a>
+      </p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><font face="Arial, Helvetica"><font size="2">The current keyboard shortcut configuration is
+based on a sfx implementation that doesn't support our new components
+that are not sfx based. We need for accessibility a new implementation
+to support a better keyboard shortcut configuration, too.l </font></font>
+      </p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Carsten Driesner <br>
+
+      <a href="mailto:carsten.driesner@sun.com">carsten.driesner@sun.com<comment title=" 4. row: second content line system integration " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 4. row: second content line system integration --></comment></a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/dialogs/index.html"><font size="2"><font face="Arial, Helvetica">New dialog size and
+a modified tab page handling. </font></font></a> </p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><font face="Arial, Helvetica"><font size="2">The current standard size of the tabbed dialogues
+is not large enough. Due to this fact we are running into trouble
+especially for the CJK&ndash;version of OpenOffice / StarOffice ...
+      </font></font> </p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Christian Jansen <br>
+
+      <a href="mailto:christian.jansen@sun.com">christian.jansen@sun.com<comment title=" 4. row: second content line system integration " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- 4. row: second content line system integration --></comment></a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><a href="file:///D:/prj/framework/framework/www/framework/www/proposals/printing/Standard_Printer.htm"><font size="2"><font face="Arial, Helvetica">Standard
+printer definition</font></font></a> </p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><font face="Arial, Helvetica"><font size="2">New definition of which printer will be used if a
+document will be printed via the direct print button in the objectbar
+of OO</font> (<font size="2">Realized as a HTML
+document)</font></font></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Frank Loehmann <br>
+
+      <a href="mailto:frank.loehmann@sun.com">frank.loehmann@sun.com<comment title=" HelpAgent " xmlns="http://disruptive-innovations.com/zoo/nvu"><img src="chrome://editor/content/images/tag-comment.gif"><!-- HelpAgent --></comment></a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/apply/new_preview_concept.html"><font size="2"><font face="Arial, Helvetica">Preview feature in dialogs</font></font></a> </p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><font face="Arial, Helvetica"><font size="2">This proposal is about a Preview feature to be used
+in dialogs. It presents an alternative to the formerly proposed Apply
+button concept.</font> ( <font size="2">Realized as
+a HTML document)</font></font></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="24%">
+      <p align="right"><font face="Arial, Helvetica"><font size="2">Frank Loehmann</font></font></p>
+      <p align="right"><font size="2"><font face="Arial, Helvetica"><a href="mailto:frank.loehmann@sun.com">frank.loehmann@sun.com</a></font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/filterfactory/proposal_filterfactory.html"><font size="2"><font face="Arial, Helvetica">Change mechanism for searching and creating filters </font></font></a>
+      </p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><font face="Arial, Helvetica"><font size="2">Our current mechanism to search and create filters
+which are registered for types is not really understandable for api
+user. This proposal describes a better but incompatible way to make it
+easier ... </font></font> </p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Andreas Schl&uuml;ns<br>
+
+      <a href="mailto:andreas.schluens@sun.com">andreas.schluens@sun.com</a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/macro/macrorecording.html"><font size="2"><font face="Arial, Helvetica">Problems with and proposals for
+macro recording</font></font></a></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><font face="Arial, Helvetica"><font size="2">OpenOffice.org does not contain a macro recorder.
+The problems are described and some possible solutions are discussed</font></font></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Mathias Bauer<br>
+
+      <a href="mailto:mathias.bauer@sun.com">mathias.bauer@sun.com</a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><a href="file:///D:/prj/framework/framework/www/proposals/filters/exportfilters.html"><font size="2"><font face="Arial, Helvetica">Unifying the filter API for storing
+and exporting documents</font></font></a></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="38%">
+      <p align="left"><font face="Arial, Helvetica"><font size="2">The OpenOffice.org filter API is used for loading
+and storing documents, but some special export functionality is not
+usable through this API (f.e. Impress export filters). This proposal
+tries to unify all filters and their API.</font></font></p>
+
+      </td>
+
+      <td bgcolor="#f0f0f0" width="24%">
+      <p align="right"><font size="2"><font face="Arial, Helvetica">Mathias Bauer<br>
+
+      <a href="mailto:mathias.bauer@sun.com">mathias.bauer@sun.com</a>
+      </font></font> </p>
+
+      </td>
+
+    </tr>
+
+  </tbody>
+</table>
+
+</center>
+
+<h3><br>
+</h3>
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/apply_alert.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/apply_alert.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/apply_button_spec.htm
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/proposals/apply/apply_button_spec.htm (added)
+++ websites/staging/ooo-site/trunk/content/framework/proposals/apply/apply_button_spec.htm Fri Nov 25 20:05:15 2011
@@ -0,0 +1,266 @@
+<!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="20010105;8322800">
+	<META NAME="CHANGEDBY" CONTENT=" ">
+	<META NAME="CHANGED" CONTENT="20010216;14322466">
+</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 the Use of an Apply Button in Dialogs</FONT></FONT></P>
+<P ALIGN=CENTER><FONT FACE="SunSans-Heavy"><FONT SIZE=4>Version 1</FONT></FONT></P>
+<P ALIGN=CENTER><FONT FACE="Times New Roman, serif">Date: February
+14<SUP>th</SUP>, 2001</FONT></P>
+<P ALIGN=CENTER>David Engen, Andrea Mankoski, Leyla Schroeder</P>
+<H1><B>Introduction</B></H1>
+<H2><B>User Problem Being Addressed</B></H2>
+<P STYLE="font-style: normal; text-decoration: none">These guidelines
+for the placement and functionality of a standard &quot;apply button
+set&quot; in dialog boxes have been developed to facilitate the
+process of finely adjusting objects within StarOffice /
+OpenOffice.org documents. The benefit is that users will be able to
+see their changes immediately reflected in the context of the
+document while the dialog box is still open. Users frequently want to
+make iterative changes to the selection, and if the dialog closes as
+each change is made, it is inefficient to re-open the dialog multiple
+times.</P>
+<P STYLE="font-style: normal; text-decoration: none">The &quot;Apply
+button&quot; functionality was deemed as a necessary tool for the
+medium-skill to advanced-skill user to avoid tedious command
+repetitions and for efficiency. Because this functionality will
+replace several other button sets, it is important that while it
+helps with efficiency to the advanced user, it does not hinder novice
+or cross-over users.</P>
+<H2><B>Project Definition</B></H2>
+<P>The proposed guidelines set standards for the placement of a
+&quot;standard set of Apply buttons&quot; as well as the behavior of
+each of the buttons in the set. Inclusion and exclusion principles
+have been established to more clearly state when and when not to use
+this functionality. It clearly states what buttons should be included
+in the &quot;standard set of Apply buttons&quot;, what types of
+dialog boxes they should be used with, and their location and
+arrangement in those appropriate dialog boxes.</P>
+<P>In addition to guidelines for the use of the standard set of apply
+buttons, a non-exhaustive list of dialog boxes to which it might be
+useful to add the standard set of apply buttons has been included -
+these can be found in the Appendix. Dialog boxes in four modules of
+StarOffice / Openoffice.org (Writer, Calc, Impress, Draw) were
+examined to see whether they warranted the Apply functionality.
+Because of the variation in conditions under which these buttons can
+be used, some dialog boxes were verified individually. All of those
+mentioned in this specification were found under the Format menus on
+the main menu bar of StarOffice v5.2. There is some overlap from
+module to module, but there are also dialog boxes that are
+module-specific.</P>
+<P>In summary, this report provides inclusion and exclusion
+guidelines, button configuration and behavior guidelines, scenario
+descriptions, and screen-shots of some of the dialog boxes that may
+be affected by the implementation of this functionality.</P>
+<H2><B>Related and Competitive Products</B></H2>
+<P>StarOffice v5.2 used several variations of an Apply button without
+any apparent standardization measures, and this functionality is not
+new. Some examples of programs that have already implemented similar
+functionality are: for Windows Display and Desktop Themes (Start -
+Settings - Control Panel - Display/Desktop Themes); and for GNOME the
+Panel Properties dialog. This dialog shows a button set with <SPAN STYLE="background: transparent">&quot;OK&quot;,
+&quot;Apply&quot;, &quot;Close&quot;, &quot;Help&quot;, t</SPAN>hough
+in the desktop's Control Center <SPAN STYLE="background: transparent">(Main
+Menu Button - Programs - Settings - Desktop - Panel) </SPAN>you can
+find a set with <SPAN STYLE="background: transparent">&quot;Try&quot;,
+&quot;Revert&quot;, &quot;OK&quot;, and &quot;Cancel&quot;.</SPAN></P>
+<P STYLE="margin-bottom: 0cm"><B>Note:</B></P>
+<P STYLE="margin-bottom: 0cm">The Assign button that can be found in
+several dialog boxes in StarOffice / OpenOffice.org Draw (i.e. Format
+- 3D Graphics) is not dealt with in this HCI Specification. It is
+suggested that when the behavior of those Assign buttons is identical
+to that of the Apply button, the mouse-over tip for the assign button
+be changed from &quot;Assign&quot; to &quot;Apply&quot; to avoid
+confusion. Otherwise, the name of this command should be changed to
+something less ambiguous.</P>
+<H1><A NAME="Main"></A>Basic Functionality</H1>
+<P>It is recommended that dialog boxes employ the standard set of
+apply buttons: &quot;OK&quot;, &quot;Apply&quot;, &quot;Reset&quot;,
+and &quot;Close&quot;. Because it is also useful to be able to find
+contextual help from each of those dialog boxes, the standard button
+set will also include a &quot;Help&quot; button. The buttons order
+and layout can be seen in Figure 1.</P>
+<P ALIGN=CENTER><IMG SRC="oarch.gif" NAME="Graphic3" ALIGN=BOTTOM WIDTH=517 HEIGHT=25 BORDER=0>
+<BR><B>Figure 1:</B> This is what the button layout and order should
+be for dialog boxes that require the standard set of apply buttons. 
+</P>
+<P>The buttons should be aligned along the bottom of the dialog boxes
+in question and should be referred to as &quot;the standard set of
+apply buttons&quot;. Their behavior is as follows:</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">When a user clicks the OK button,
+	the settings should be saved and the commands specified in the
+	dialog box should be carried out. The dialog box should then be
+	closed.</P>
+	<LI><P STYLE="margin-bottom: 0cm">When a user clicks the Apply
+	button from the main dialog box, changes are applied to the selected
+	object within the document, but the dialog box is not closed.</P>
+	<LI><P STYLE="margin-bottom: 0cm">When a user clicks the Reset
+	button from the main dialog box, the settings in the dialog box are
+	returned to their values as per the last Apply command. If the user
+	has opened the dialog and has made changes but has not yet clicked
+	the Apply button, the settings are returned to the values
+	corresponding to when they first opened the dialog box. The Reset
+	button does not close the dialog box. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">When a user makes changes to the
+	values in the dialog box and clicks the Close button from the main
+	dialog box without first clicking Apply, an alertbox like the one
+	shown below should be displayed to allow them to continue without
+	losing any information.</P>
+	<LI><P>The Help button invokes the standard Help Tool window
+	contextualized to the dialog box in question.</P>
+</UL>
+<P ALIGN=CENTER><IMG SRC="apply_alert.gif" NAME="Graphic2" ALIGN=BOTTOM WIDTH=280 HEIGHT=105 BORDER=0></P>
+<P ALIGN=CENTER><FONT SIZE=2 STYLE="font-size: 9pt"><B>Figure 2:</B>
+This is the alert-box that is displayed if a user clicks the Close
+button and there are changed settings that have not yet been applied
+to the document. </FONT>
+</P>
+<P>The wording of the text within the alert-box is modeled after
+phrasing that is already used throughout StarOffice 5.2. It should
+read: &quot;Settings have been modified. Do you want to apply your
+changes?&quot; The alert-box is similar to that which appears when a
+user attempts to close a document without saving its contents first.
+The behavior of each button in this alert-box is as follows:</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">When a user clicks the Apply
+	button in the alert-box, the changes they made to the values within
+	the main dialog box will be applied to the selection in the
+	document, and the dialog box is closed.</P>
+	<LI><P STYLE="margin-bottom: 0cm">When a user clicks the Discard
+	button in the alert-box, the changes they made to the values within
+	the main dialog box should <I>not</I><SPAN STYLE="font-style: normal">
+	be applied, and the dialog box should be closed.</SPAN></P>
+	<LI><P>When a user clicks the Cancel button in the alert-box, the
+	alert-box should be closed but the changes should <I>not</I> be
+	applied and the user should be returned to the main dialog box. 
+	</P>
+</UL>
+<H2><B>Mouseless navigation</B></H2>
+<P STYLE="margin-bottom: 0cm">Mouseless navigation and keyboard
+traversal should work as in other StarOffice / OpenOffice.org dialog
+boxes employing default buttons, mnemonics, and full keyboard access.</P>
+<H2>Mnemonics</H2>
+<P STYLE="margin-bottom: 0cm">For accessibility reasons, mnemonics
+have been added to the Apply and Reset buttons. The Close button does
+not require one because the Escape key defaults to Close in a dialog
+box. The letters &quot;a&quot; and &quot;r&quot; have been chosen as
+the mnemonics for Apply and Reset respectively. The letter &quot;h&quot;
+will remain as the default for Help as is standard.</P>
+<H2>&quot;Undo&quot; Command Protection</H2>
+<P STYLE="margin-bottom: 0cm">To ensure that users have a safety net,
+they should always be allowed to undo commands that were invoked
+through an Apply button in a dialog box. The current behavior in one
+of the few modeless dialog box that currently (v5.2) contains an
+Apply button (Insert - Hyperlink) is to undo each of the apply
+commands individually, even if the selection has been changed. It is
+suggested that modal dialog boxes follow this behavior as closely as
+possible for the sake of consistency. This means that for both modal
+and modeless dialog boxes the Undo command should only go as far back
+as one Apply command, and not as far as all the Apply commands
+invoked in the last instance of the dialog box.</P>
+<H1>Guidelines</H1>
+<H2>Inclusion Guidelines</H2>
+<P>The &quot;standard set of apply buttons&quot; should be used ... :
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">When it might be helpful to users
+	to make iterative changes to a selection within a document without
+	closing and re-opening the dialog box.</P>
+	<LI><P STYLE="margin-bottom: 0cm">Even in instances where the dialog
+	box presents the user with a preview of the changes in question.
+	This allows the user to view the object's properties in the context
+	of the document.</P>
+</UL>
+<H2>Exclusion Guidelines</H2>
+<P>The &quot;standard set of apply buttons&quot; should <I>not</I><SPAN STYLE="font-style: normal">
+be used ... :</SPAN></P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">If the changes applied to the
+	user's selection are not visibly noticeable. Dialog boxes that
+	contain visibly confirmable changes <I>and</I> non-visibly
+	confirmable changes may still use the apply button set, and should
+	apply both sets of changes.</P>
+	<LI><P STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">If
+	the changed settings will not immediately be reflected in the user's
+	document.</SPAN></P>
+	<LI><P STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">If
+	the Apply command is in reference to an action that will occur
+	within that specific dialog box. It should only be used when setting
+	are transferred from a dialog box directly to a document.</SPAN></P>
+	<LI><P STYLE="margin-bottom: 0cm">In any dialog box that is accessed
+	from within another dialog box (i.e. secondary, terciary, ... ).</P>
+	<LI><P STYLE="margin-bottom: 0cm">When the changes made in the
+	dialog box are immediately reflected in the document, as in an
+	inspector window.</P>
+</UL>
+<H2>Behavior Guidelines</H2>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">The Apply and Reset buttons should
+	be inactive(graye<SPAN STYLE="background: transparent">d out) when
+	the user first opens a dialog box that contains the standard set of
+	apply buttons. They should become active as soon as any of the
+	values are changed in that dialog box. As soon as the Apply or Reset
+	buttons are clicked, they should again revert to their greyed out
+	condition.</SPAN></P>
+	<LI><P STYLE="margin-bottom: 0cm"><SPAN STYLE="background: transparent">When
+	a user clicks the Apply button in a dialog box containing multiple
+	tabs, the settings in all tabs within that dialog box should be
+	applied, not only those in the active window. To be consistent, when
+	the Reset command is clicked, the settings in all tabs within that
+	dialog box should be reset.</SPAN></P>
+	<LI><P STYLE="margin-bottom: 0cm">The Reset button (that returns
+	settings to previously applied values) should not be confused for a
+	defaults button (that returns settings to program defaults). Dialog
+	boxes that need a Defaults button should present it separately from
+	the standard set of apply buttons.</P>
+</UL>
+<H1>Open Issues</H1>
+<H2>Button set</H2>
+<P>The account of buttons should be reduced to a minimum as too much
+buttons could be confusing for a user. Because of this two questions
+came up:</P>
+<UL>
+	<LI><P>It is not clear if the Reset button should be an optional
+	part of the button set. As there might be situations where an Apply
+	button would be useful, but a Reset button would not make so much
+	sense. An example are dialogs, where just some simple values are
+	entered, e.g. for adjusting the row height of a table (see Format &#150;
+	Row &#150; Height). The more complex the possible dialog settings
+	are, the more useful a Reset button would be. Should the Apply
+	button set always contain a Reset button?</P>
+	<LI><P>Can we find another solution for the Help button, for example
+	by replacing it with an icon? (As this also affects other dialogs,
+	that won't have an Apply button, this will probably be an open issue
+	for the future.)</P>
+</UL>
+<H2>Reset Button Behavior</H2>
+<P>The Reset button's current behavior allows users to revert the
+settings in the dialog box to their values as of the last Apply
+command. As we see it, there are several options here:</P>
+<OL>
+	<LI><P>Change the behavior of the Reset button to more of an Undo so
+	that it reverts the settings back to the values at the invocation of
+	the dialog box</P>
+	<LI><P>Eliminate the Reset button altogether to eliminate clutter,
+	still allowing the user to &quot;cancel&quot; their Apply commands
+	using the Undo function</P>
+	<LI><P>Leave the Reset button like it is.</P>
+</OL>
+<P>Again, there are other options that are listed here, but what is
+the best solution?</P>
+<HR>
+<P STYLE="margin-top: 0.42cm; page-break-after: avoid"><A HREF="apply_button_spec_appendix.html"><FONT SIZE=4><FONT FACE="Times New Roman, serif">Appendix 
+  1: Proposed Additions</FONT></FONT></A></P>
+<HR>
+</BODY>
+</HTML>
\ No newline at end of file

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/apply_button_spec_appendix.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/proposals/apply/apply_button_spec_appendix.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/proposals/apply/apply_button_spec_appendix.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_area.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_area.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_bullets.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_bullets.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_cell.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_cell.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_conditions.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_conditions.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_dimensions.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_dimensions.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_page.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_page.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_paragraph.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_paragraph.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_styles.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_styles.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_text.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/format_text.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/new_preview_concept.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/proposals/apply/new_preview_concept.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/proposals/apply/new_preview_concept.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/proposals/apply/oarch.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/apply/oarch.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/b1.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/b1.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/b2.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/b2.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/b3.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/b3.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/b4.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/b4.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/index.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/index.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/index.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/staroffice_60_desk_env_int.sdc
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/dialogs/staroffice_60_desk_env_int.sdc
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/filterfactory/filterfactory.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/filterfactory/filterfactory.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/filterfactory/proposal_filterfactory.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/proposals/filterfactory/proposal_filterfactory.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/proposals/filterfactory/proposal_filterfactory.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/proposals/filterfactory/seq_create_filter.gif
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/framework/proposals/filterfactory/seq_create_filter.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/framework/proposals/filters/exportfilters.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/proposals/filters/exportfilters.html (added)
+++ websites/staging/ooo-site/trunk/content/framework/proposals/filters/exportfilters.html Fri Nov 25 20:05:15 2011
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+</head>
+
+<body>
+  <div id="banner">
+    <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+      <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+    <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+   <div id="bannercenter"><br/>(incubating)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  
+  <div id="content">
+  
+    
+    
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/contact.html">Contact Us</a> |
+	<a href="/terms.html">Terms of Use</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	<br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	<br />Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/framework/proposals/helpagent/HelpAgentProposal_01.htm
==============================================================================
--- websites/staging/ooo-site/trunk/content/framework/proposals/helpagent/HelpAgentProposal_01.htm (added)
+++ websites/staging/ooo-site/trunk/content/framework/proposals/helpagent/HelpAgentProposal_01.htm Fri Nov 25 20:05:15 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>



Mime
View raw message