incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1175552 - in /incubator/ooo/ooo-site/trunk/content/ui: ./ index.html introduction.html robots.txt
Date Sun, 25 Sep 2011 19:43:35 GMT
Author: kschenk
Date: Sun Sep 25 19:43:35 2011
New Revision: 1175552

KLS - added ui repository

    incubator/ooo/ooo-site/trunk/content/ui/index.html   (with props)
    incubator/ooo/ooo-site/trunk/content/ui/introduction.html   (with props)
    incubator/ooo/ooo-site/trunk/content/ui/robots.txt   (with props)

Added: incubator/ooo/ooo-site/trunk/content/ui/index.html
--- incubator/ooo/ooo-site/trunk/content/ui/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/ui/index.html Sun Sep 25 19:43:35 2011
@@ -0,0 +1,34 @@
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html;charset=iso-8859-1">
+  <title>UI Project</title>
+ </head>
+<body lang="en-US">
+  <div id="guts" align="right">
+   <p><i>Last modified <csobj w="86" h="16" t="DateTime" locale="00000809"
format="LongDate" region="0">05 June 2007</csobj></i></p>
+  </div>
+  <div id="guts">
+   <h1> User Interface Design Project</h1>
+   <p>This project focusses on technical user interface design of <a
href="accessibility/index.html">Accessibility</a> and <a href="VisualDesign/index.html">visual
design</a> are covered as well.</p>
+   <h5>Participation</h5>
+   <p>Much of our work takes place in our mailing lists page, which can viewed by clicking
on the &quot;<a href="">Mailing
Lists</a>&quot; link in the navbar top left. From there, you can subscribe to our
lists and view archives. Please familiarize yourself with the discussions that have taken
place. Once you have done so, don't hesitate to join in! A convention is that new members
introduce themselves briefly before they present ideas and opinions to the community.</p>
+   <h3>Sections</h3>
+  </div>
+  <ul>
+   <div id="guts">
+    <li><a href="VisualDesign/index.html">Visual design</a> stuff of
+    <li><a href="accessibility/index.html">Accessibility</a>
+    <li><a href="proposals/index.html">Spec Proposals</a> for the user
interface of OOo 1.1.x (find the latest specifications at <a href="">Specification
Project</a>)    <li><a href="knowledge/index.html">Knowledge base</a>:
information which we do not want to get lost
+    <li><a href="protocols/index.html">Meeting Minutes</a> of the User
Interface Team
+   </div>
+  </ul>
+  <h3>Related Projects</h3>
+  <ul>
+   <li><a href=""> Specification Project</a>
(all specifications for OOo 2.x and later)
+   <li><a href=""> User Experience Project</a>
+  </ul>
+ </body>

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

Added: incubator/ooo/ooo-site/trunk/content/ui/introduction.html
--- incubator/ooo/ooo-site/trunk/content/ui/introduction.html (added)
+++ incubator/ooo/ooo-site/trunk/content/ui/introduction.html Sun Sep 25 19:43:35 2011
@@ -0,0 +1,54 @@
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+	<META NAME="AUTHOR" CONTENT="Oliver Specht">
+	<META NAME="CREATED" CONTENT="20010919;12003175">
+	<META NAME="CHANGED" CONTENT="20010919;12045708">
+<H2>What do we want to achieve with the user interface project?</H2>
+<P>We want to focus all UI related issues in one project.
+Development, discussions, proposals - everything should be at the
+same place. It is currently typical that the developers of the UI are
+spread in different projects. Most of them are not only dealing with
+UI, but also with other responsibilities. 
+<P>This UI project will be the home for all the UI related stuff.</P>
+<P>On the technical side, the current situation has the drawback,
+that large libraries are getting loaded at startup time.  The code of
+course doesn't get loaded, but the loading time of libraries has a
+relation to the amount of functions that are exposed by this library.
+While moving the UI code itself to the UI project over the time, one
+important goal will be a solution for this problem, probably by
+moving the code to some smaller libraries and loading them on demand.</P>
+<P>I think that we should not simply move the code from one place to
+another. There is some code that is old and maybe more code that is
+very old; and other code that is very very old :-). The developers
+listening here will understand that some of the code has already
+reached a kind of  &quot;end of life&quot; in the sense of
+maintainability. If one wants to know what I mean, he might want to
+dig in code like from the Stylist, the Ruler or the Tools/Configure
+<P>Another important feature, which we might want to implement is at
+a first step a replaceable UI. This could mean that one is able to
+replace i.e. dialogs, accelerators, pop up menus and such.
+Replaceable means that one can easier integrate one of the
+applications into his own environment/application as a component. In
+the longer term a second step might be a customizable UI.
+Customizable means that one would be able to customize the UI to his
+own needs for himself, his deployment of or his
+integration of, by i.e. reduce the functionality of
+certain dialogs without the need of providing an own one.</P>
+<P>Your contribution is welcome. 
+<P><A HREF="">Oliver Specht</A></P>
\ No newline at end of file

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

Added: incubator/ooo/ooo-site/trunk/content/ui/robots.txt
--- incubator/ooo/ooo-site/trunk/content/ui/robots.txt (added)
+++ incubator/ooo/ooo-site/trunk/content/ui/robots.txt Sun Sep 25 19:43:35 2011
@@ -0,0 +1,7 @@
+User-Agent: *
+Disallow: /source/
+Disallow: /issues/
+Disallow: /search/
+Disallow: /servlets/
+Disallow: /project/
+Disallow: /nonav/

Propchange: incubator/ooo/ooo-site/trunk/content/ui/robots.txt
    svn:eol-style = native

View raw message