Project tools

• Project home
• Membership

• Announcements
• Mailing lists

• Documents & files
• CVS

• Issue tracker

Search

This project All projects

Advanced search

Google search

How do I...

• Sitemap
• FAQ
• Get help?

start:

Meeting Minutes	OpenOffice.org

Weekly Meeting Virtual User Interface (VUI) Team

Date	March 14th 2002
Time	10:00h, MEST
Location	Cupertino, eham-02
Attendees	Hans-Peter Burow (PB) Gunnar Timm (GT) Daniel Rentz (DR) Oliver Specht (OS) Frank Schönheit (FS)
Minute Taker	FS (next: PB, DR,GT, CL, OS, FS)
Distribution List	http://ui.openoffice.org/protocols

Table of Contents

1 Action Items

2 Round table

1 Action Items

Item	Responsible	Status
Create a concept of Common UI factory design	FS	stalled
Add a SetModeBitmap method to all controls in VCL that have a bitmap	SSA	done
Toolboxes in dialogs must get the correct image list set (standard/high contrast)	All ui developers	open1
High Contrast mode (HC mode) for Listboxes, Treelistboxes and Browseboxes must be handled where used with bitmaps	All ui developers	open 1
Calling SetModeBitmap for all dialog controls with bitmaps	All ui developers	open 1
Add a method to the color class to see if the colors luminance is below a fixed value	SSA	done
Check context menu handling	CJ	open 2

1: These items are waiting for the implementation of the interfaces to set bitmaps/image list for high contrast mode and the creation of high contrast ready bitmaps

2: CJ is on vacation currently

2 Round table

Accessibility

• To be compatible with the Java API, our UNO Accessibility implementations for check boxes and radio buttons have to support the XAccessibleValue interface, exposing a value depending on the current check state. In our team, this affects the SvxRectCtrl, where the options to choose are represented as RADIOBUTTONs in the UNO-API.

• UNO-API implementations for the ComboBox are ongoing, and will probably be finished next week

• UNO-API implementations for the BrowseBox will be started this week

• BugFixing regarding various other Accessibility issues is ongoing

• OS reminded that we have an own Accessibility test tool in the toolkit project, which should be used to check own API implementations. It offers more comfort and functionality than the JavaMonkey, is extendible by ourself, and works directly on the UNO-API, instead of involving the Java-UNO-Bridge, thus evading any possible problems within the bridge.