blob: 6e3670f9f4bbd3cf008bb4c5c8772c1793999b2e [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<head>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
<TITLE>meeting minutes</TITLE>
<META NAME="GENERATOR" CONTENT="StarOffice 6.0 (Win32)">
<META NAME="CREATED" CONTENT="20011203;10465450">
<META NAME="CHANGEDBY" CONTENT="Gunnar Timm">
<META NAME="CHANGED" CONTENT="20020116;8454299">
<STYLE>
<!--
@page { margin: 2cm }
TD P { margin-bottom: 0.21cm; font-family: "Frutiger-Roman", "Arial", "Helvetica"; font-size: 12pt; widows: 2; orphans: 2; page-break-before: auto; page-break-after: auto }
H1 { margin-top: 0.63cm; margin-bottom: 0.21cm; font-family: "Frutiger-Roman", "Arial", "Helvetica"; font-size: 14pt; widows: 2; orphans: 2; page-break-before: auto; page-break-after: auto }
P { margin-bottom: 0.21cm; font-family: "Frutiger-Roman", "Arial", "Helvetica"; font-size: 12pt; widows: 2; orphans: 2; page-break-before: auto; page-break-after: auto }
P.documenttype { font-family: "Frutiger-Roman", "Arial", "Helvetica"; font-size: 24pt; font-weight: bold }
P.companyname { margin-bottom: 0cm; color: #00a6ff; font-family: "Frutiger-Bold", "Arial", "Helvetica"; font-size: 36pt; font-weight: bold; text-align: right }
TH P { margin-bottom: 0.21cm; font-family: "Frutiger-Roman", "Arial", "Helvetica"; font-size: 12pt; font-weight: medium; text-align: left; widows: 2; orphans: 2; page-break-before: auto; page-break-after: auto }
A:link { text-decoration: none }
-->
</STYLE>
</head>
<body LANG="de-DE">
<TABLE WIDTH=100% BORDER=0 CELLPADDING=0 CELLSPACING=0 STYLE="page-break-before: always; page-break-inside: avoid">
<COL WIDTH=114*>
<COL WIDTH=142*>
<THEAD>
<TR VALIGN=TOP>
<TD WIDTH=45%>
<P CLASS="documenttype"><a href="index.html">Meeting Minutes</a></P>
</TD>
<TD WIDTH=55%>
<P CLASS="companyname">OpenOffice.org</P>
</TD>
</TR>
</THEAD>
</TABLE>
<P ALIGN=LEFT STYLE="margin-top: 0.63cm; margin-bottom: 0.42cm; page-break-after: avoid"><B>Weekly Meeting Virtual User Interface Team</B></P>
<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0 FRAME=HSIDES RULES=ROWS STYLE="page-break-inside: avoid">
<COL WIDTH=57*>
<COL WIDTH=199*>
<THEAD>
<TR VALIGN=TOP>
<TH WIDTH=22% BGCOLOR="#e6e6e6">
<P ALIGN=LEFT>Date</P>
</TH>
<TD WIDTH=78% SDVAL="35665" SDNUM="1031;0;@">
<P ALIGN=LEFT>January 10<SUP>th</SUP> 2002</P>
</TD>
</TR>
</THEAD>
<TBODY>
<TR VALIGN=TOP>
<TH WIDTH=22% BGCOLOR="#e6e6e6">
<P ALIGN=LEFT>Time</P>
</TH>
<TD WIDTH=78%>
<P>10:00h, MEST</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TH WIDTH=22% BGCOLOR="#e6e6e6">
<P ALIGN=LEFT>Location</P>
</TH>
<TD WIDTH=78%>
<P>Cupertino, eham-02</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TH WIDTH=22% BGCOLOR="#e6e6e6">
<P ALIGN=LEFT>Attendees</P>
</TH>
<TD WIDTH=78%>
<P>OS, FS, DR, CJ, PB, CL,GT</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TH WIDTH=22% BGCOLOR="#e6e6e6">
<P ALIGN=LEFT>Minute Taker</P>
</TH>
<TD WIDTH=78%>
<P ALIGN=LEFT>Gunnar Timm (GT)</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TH WIDTH=22% BGCOLOR="#e6e6e6">
<P ALIGN=LEFT>Distribution List</P>
</TH>
<TD WIDTH=78%>
<P>ui.openoffice.org</P>
</TD>
</TR>
</TBODY>
</TABLE>
<P><BR><BR>
</P>
<DIV ID="Inhaltsverzeichnis1">
<P STYLE="margin-bottom: 0cm; widows: 0; orphans: 0; page-break-before: auto; page-break-after: auto">
<A HREF="#1.1. Action Items|outline">1. Action Items</A></P>
<P STYLE="margin-bottom: 0cm; widows: 0; orphans: 0; page-break-before: auto; page-break-after: auto">
<A HREF="#s">2. Misc</A></P>
<P STYLE="margin-bottom: 0cm; widows: 0; orphans: 0; page-break-before: auto; page-break-after: auto">
<A HREF="#3.3. Current situation|outline">3. Next meeting minutes</A></P>
</DIV>
<H1><A NAME="1.1. Action Items|outline"></A>1. Action Items</H1>
<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0 FRAME=BELOW RULES=ROWS STYLE="page-break-inside: avoid">
<COL WIDTH=164*>
<COL WIDTH=40*>
<COL WIDTH=52*>
<THEAD>
<TR VALIGN=TOP>
<TH WIDTH=64% BGCOLOR="#cccccc">
<P ALIGN=LEFT>Item</P>
</TH>
<TH WIDTH=16% BGCOLOR="#cccccc">
<P ALIGN=LEFT>Responsible</P>
</TH>
<TH WIDTH=20% BGCOLOR="#cccccc">
<P ALIGN=LEFT>Status</P>
</TH>
</TR>
</THEAD>
<TBODY>
<TR VALIGN=TOP>
<TD WIDTH=64%>
<P>Create a concept of Common UI factory design</P>
</TD>
<TD WIDTH=16%>
<P>FS</P>
</TD>
<TD WIDTH=20%>
<P>stalled</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TD WIDTH=64%>
<P>Update and publish dialog design guidelines</P>
</TD>
<TD WIDTH=16%>
<P>CJ</P>
</TD>
<TD WIDTH=20%>
<P>In progress</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TD WIDTH=64%>
<P>Check, wether &quot;Connecting lines&quot; are useful in
Treelistboxes or not <SUP>(1.)</SUP></P>
</TD>
<TD WIDTH=16%>
<P>CJ</P>
</TD>
<TD WIDTH=20%>
<P>new</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TD WIDTH=64%>
<P>Determine what to do for Accessibility <SUP>(2.)</SUP></P>
</TD>
<TD WIDTH=16%>
<P>OS</P>
</TD>
<TD WIDTH=20%>
<P>new</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TD WIDTH=64%>
<P>Requirement / specification for a generic Navigator <SUP>(3.)</SUP></P>
</TD>
<TD WIDTH=16%>
<P>PB</P>
</TD>
<TD WIDTH=20%>
<P>new</P>
</TD>
</TR>
<TR VALIGN=TOP>
<TD WIDTH=64%>
<P>Requirement / specification for a generic Stylist <SUP>(4.)</SUP></P>
</TD>
<TD WIDTH=16%>
<P>GT</P>
</TD>
<TD WIDTH=20%>
<P>new</P>
</TD>
</TR>
</TBODY>
</TABLE>
<P STYLE="margin-bottom: 0cm; widows: 0; orphans: 0; page-break-before: auto; page-break-after: auto">
<BR>
</P>
<P STYLE="margin-bottom: 0cm; widows: 0; orphans: 0; page-break-after: auto">
Comments to the new Todos:</P>
<OL>
<LI><P STYLE="margin-bottom: 0cm; widows: 0; orphans: 0; page-break-after: auto">
While discussing, the question came up, wether the connecting lines
in a Treelistbox are confusing or helpful to get an overview of the
structure. Since we weren't able to come to a solution for all
usecases, Christian will check this.</P>
<LI><P STYLE="margin-bottom: 0cm; widows: 0; orphans: 0; page-break-after: auto">
In view of the importance of Accessibility and the work which is
done in the Applications, Frank worried about a lag in the progress
on this item in the UI-team. So Oliver will look for tasks, which
could be done in this stage of the development.</P>
<LI><P STYLE="margin-bottom: 0cm; widows: 0; orphans: 0; page-break-after: auto">
Since every Application implements its &quot;own&quot; (in the
meaning of most functionality) Navigator, the idea came up, to make
the Navigator generic. Peter is collecting informations of the
requirements from the Applications.</P>
<LI><P STYLE="margin-bottom: 0cm; widows: 0; orphans: 0; page-break-after: auto">
Analogical as for Navigator, but the differences between the
Applications are not so large.</P>
</OL>
<H1><A NAME="s"></A>2. Misc</H1>
<P>Everybody in the UI team is busy with issues for the upcoming
product release or API documentation.</P>
<P>First thoughts on generic Navigator / Stylist (move toward UNO):
Huge effort for implementation, Benefit (less code, faster, more
functionality) not clear at all. In addition, the demands from the
applications are particular very different for the Navigator.</P>
<H1><A NAME="3.3. Current situation|outline"></A>3. Next meeting
minutes</H1>
<P>CL, OS, FS, PB, GT, DR</P>
<DIV TYPE=FOOTER>
<P ALIGN=RIGHT STYLE="margin-top: 0.5cm; margin-bottom: 0cm; widows: 0; orphans: 0; page-break-before: auto; page-break-after: auto">
Page <SDFIELD TYPE=PAGE SUBTYPE=RANDOM FORMAT=PAGE>1</SDFIELD> of <SDFIELD TYPE=DOCSTAT SUBTYPE=PAGE FORMAT=PAGE>1</SDFIELD></P>
</DIV>
</body>
</HTML>