|
OpenOffice.org |
Weekly Meeting Virtual User Interface Team
|
Date |
January 31th 2002 |
|---|---|
|
Time |
10:00h, MEST |
|
Location |
Cupertino, eham-02 |
|
Attendees |
Christian Lippka (CL) |
|
Minute Taker |
Frank Schönheit (next: PB, DR, GT, CL, OS, FS) |
|
Distribution List |
http://ui.openoffice.org/protocols |
Inhaltsverzeichnis
1 Action Items
1.1 Comments on Action Items
2 Status
3 Misc
3.1 Description for Gallery Items
3.2 Keyboard Access to the Gallery
3.3 Resize of Dialogs
4 Bottom Line
4.1 Abbreaviations
1 Action Items
|
Item |
Responsible |
Status |
|---|---|---|
|
Create a concept of Common UI factory design |
FS |
stalled |
|
Determine what to do for Accessibility |
OS |
in progress |
|
Determine whether base classes for the Accessibility API will be provided (1) |
OS |
done |
|
Determine whether a description for gallery elements is necessary |
CJ |
new |
1.1 Comments on Action Items
As it rose during another meeting regarding accessibility base classes, these do not make sense at all - the requirements are too different. At least this holds for application-spanning accessibility implementations.
2 Status
GT finished making the Text Orientation control accessible. As this control is always tied to a numeric input field next to it, it was decided to not represent it with an own accessibility object at all (instead an AT tool will see the numeric field without loss of information) , but just ensure that visual issues (high contrast mode and such) are solved.
OS told us that the Border control (for e.g. table cell borders) is nearly accessible, some API implementations are still missing
PB is collecting information about the SvTreeListBox/SvListBox class hierarchy, to prepare designing the accessibility API for these classes.
FS raised the concern that the BrowseBox may become a resource problem. We currently have nobody who knows this class (and derivees) well enough, and at the same time has time to take care for it - the UNO developer manual is tying much ressources at the moment.
The accessibility of the gallery component has been given over to Kai Ahrens (OpenOffice.org Draw Team)
3 Misc
3.1 Description for Gallery Items
There was a discussion whether it would make sense for the gallery component to provide a description (as XAccessibleContext::getAccessibleDescription) for every entry (question was raised by CJ). There were different opinions about this, most attendees agreed that it may be a requirement to provide at least the possibility to do so. This would mean additional implementation effort: As the gallery content is currently stored in a database (Berkely DB), this needs to be extended; in addition maybe a user interface for changing these descriptions must be provided.
CJ will clarify the necessity for this feature.
3.2 Keyboard Access to the Gallery
CJ asked whether there are concrete ideas how to use the gallery
without a mouse. The most issues (like local navigation) can be
solved using the usual VCL mechanisms, but what about the DnD of an
element into the document?
OS told us that this should work using
the clipboard - the functionallity is already there.
3.3 Resizing of Dialogs
CJ started a poll about the resize of dialog fonts. Currently, when the user changes the system settings for the font size, this applies to the whole OOo application: Not only the window titles etc., but also complete dialogs (including content) are resized. This is inconsistent with the system behaviour (at least on windows), where this settings affects only window titles, but not window (especially dialog) content. In particular, Windows does not offer a setting for the dialog content - it is always sized according to the system wide font size ("large fonts" vs. "small fonts") settings.
The attendees agreed that due to this inconsistency, it would make sense to change the behaviour of OOo so that the system setting affects window titles only, not content.
If, somewhere in the future, the system(s) provide(s) a possibility to change the window content font size independent on the window title font size, this needs to be re-integrated in OOo then.
4 Bottom Line
4.1 Abbreaviations
AT - Assistive Technologie
VCL - visual component library - base library used for visualizing OOo to the user
DnD - Drag and Drop
OOo - OpenOffice.org
Page
