The Free and Open Productivity Suite
Apache OpenOffice 4.1.3 released

Meeting Minutes


Weekly Meeting Virtual User Interface (VUI) Team


February 28st 2002


10:00h, MEST


Cupertino, eham-02


Hans-Peter Burow (PB)
Gunnar Timm (GT)
Christian Jansen (CJ)
Daniel Rentz (DR)
Oliver Specht (OS)
Frank Schönheit (FS)
Stephan Schäfer(SSA)
Mathias Bauer(MBA)
Kai Ahrens(KA)
Malte Timmerman(MT)
Christian Lippka(CL)

Minute Taker

CL (next:OS, FS, PB, DR,GT, CL)

Distribution List


Table of Contents

1 Action Items

2 Accessibility: Handling UI bitmaps in high contrast (HC) mode

1 Action Items




Create a concept of Common UI factory design



Collect all bitmaps which have to have new colors for high contrast mode



Contact responsible person (MBA aka Mathias Bauer) to clarify the status quo and future of "In-Run-Time-Exchangeable Bitmaps"



Collect and pack all bitmaps from projects offmgr, sw, starmath and basctl



Collect and pack all bitmaps from project svx



Collect and pack all bitmaps from project sc



Collect and pack all bitmaps from projects sd and sch



Add a SetModeBitmap method to all controls in VCL that have a bitmap



Toolboxes in dialogs must get the correct image list set (standard/high contrast)

All ui developers


HC mode for Listboxes, Treelistboxes and Browseboxes must be handled where used with bitmaps

All ui developers


Calling SetModeBitmap for all dialog controls with bitmaps

All ui developers


Impelement a method for images that do color replacement for images and image lists



Add a new paintflag for painting images with color replacement



Add a method to the color class to see if the colors luminance is below a fixed value



2 Accessibility: Handling UI bitmaps in high contrast mode

CJ: Confirmed that Stella Schulze will draw a high contrast version of all of our used bitmaps.

We discussed if VCL can handle this extra bitmapsfor us.

MBA stated that toolboxes will handles this inside VCL, but we needed a solution for other controls and handmade ui elements.

We agreed that it should be no resource problem if we have both the standard and high contrast bitmap available in memory at the same time for dialogs.

CL raised the question if we can add references to the high contrast bitmaps next to the definitions of the standard bitmaps in the resource files. We mostly agree that this would be a good design but all the work, including changing the resource manager, had to be done by SSA who is already on tight schedule.

MBA started with the idea that the ui developer should overload the StateChange method at theire ui classes and set the correct bitmaps themself after a change to/from high contrast mode. We found out that it is not sufficient to do this in the StateChange method only since we have to test on dialog construction if where already in high contrast mode. FS suggested a virtual method for tabpages to switch between the modes to have a common interface and to share the StateChange implementation.
We encountered a difficulty in getting original bitmaps when doing a switch from high contrast mode to non high contrast mode. If the bitmap resource is embeded in another resource (f.e. a button ) there is no easy way to get it besides creating a temporary button and ask it for its bitmap.

Our solution was to have the VCL controls store two bitmaps, one standard and an optional bitmap for high contrast mode. If that is set, the control handles the state changes to/from high contrast mode themself. For not having another special interface for just the high contrast mode, we agreed on having a SetModeBitmap method which takes a bitmap and an enum that definine for which mode this bitmap will be used. So this can be used for future additions like a true color mode f.e . So the dialogs must set the bitmaps for high contrast mode only once after creation.

CJ informed us about a special handling in the white high contrast mode. There we will use the default bitmaps but do a special painting for pressed images where we have to replace some colors using a table provided by CJ. KA will add a function to do this replacement for images and image lists. The replacement will be handled in the paint method, so we need a new paintflag for this. VCL will detect itself which paintmode has to be used.

MT informed us that high contrast bitmaps should also be used if the luminance of the background color falls below a fixed value. SSA will add a method at our color class where we can verify this.

For handmade ui controls, we have to use our background color and check it against that method to see if we need to use the high contrast bitmap.This raised an issue that MBA needs two different image lists for toolboxes and menus, since they can have different background colors.

Page 1 of 1

Apache Feather

Copyright & License | Privacy | Website Feedback | Contact Us | Donate | Thanks

Apache and the Apache feather logo are trademarks of The Apache Software Foundation. OpenOffice, OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation. Other names appearing on the site may be trademarks of their respective owners.