Meeting Minutes	OpenOffice.org

Weekly Meeting Virtual User Interface Team

Date	January 24th 2002
Time	10:00h, MEST
Location	Cupertino, eham-02
Attendees	DR, FS, CJ, PB, CL,GT, OS
Minute Taker	Oliver Specht (OS)
Distribution List	ui.openoffice.org

1. Action Items

Item	Responsible	Status
Create a concept of Common UI factory design(1)	FS	stalled
Determine what to do for Accessibility (2.)	OS	in progress
Requirement / specification for a generic Navigator (3.)	PB	done
Determine whether base classes for the Accessibility API will be provided	OS	new

Comments to the Action items:

1. To be continued in April 2002

2. Partly discussed in this meeting and to be continued.

3. Published on http://ui.openoffice.org/FunctionalDescription/status_quo_navigator.html

2. Misc

It has been agreed that a generic Navigator implementation that uses UNO APIs doesn't make sense due to the high effort to create and implement the APIs in connection with the resulting code size. See http://ui.openoffice.org/FunctionalDescription/status_quo_navigator.html for details about the requirements.

3. Accessibility requirements

To support high contrast mode the transparency color of the toolbox bitmaps (which is now grey) has to be switched to magenta. Therefor a conversion of the source-bitmaps is needed and and a redesign of some bitmaps is necessary. CJ, Stella Schulze and Ilko Hoepping are working on an document that summarizes the menu entries of the Office in reference to steady use of icons.

The toolbox configuration is currently unusable without a mouse. A new design is needed.

The requirement of multiple keyboard configuration sets may require a redesign of the keyboard configuration dialog.

All this will be done when the Accessibilty task list (which is now in progress in the Accessiblity team) is completed.

Up to now the following controls have been identified as task of our team's accessibility

• SvTreeListBox and derivatives (SvTabListBox, SvCheckListBox) -> task of PB

• SvxCtrDial (text orientation control in format/cells/alignment/text direction) -> task of GT

• SvxRectCtl (i.e. in format/position and size/position for drawing objects) -> task of GT

• SvxFrameSelector (i.e. in format/frame/border for writer text frames) -> task of OS

• SvtIconChoiceCtrl (used i.e. in the Hyperlink dialog)

• SvxIMapDlg (ImageMap dialog) - our responsibility is not clear but probable.

For these controls the Accessiblity API, keyboard control has to be implemented. The painting has to use VCL conforming colors to support high contrast mode.

The question about providing base classes for Accessiblity API implementations came up (see Action Items).

CJ asked to inform him or Frank Loehmann about further Accessiblity issues.

4. Next meeting minutes

FS, PB, DR, GT, CL, OS