OpenOffice.org |
週刊誌 会合 事実上の 使用者 Interface (VUI) Team
Date |
March 21th 2002 |
---|---|
Time |
10:00h, MEST |
場所 |
Cupertino, eham-02 |
Attendees |
Christian Lippka (CL) |
Minute Taker |
FS (next: PB, DR,GT, CL, OS, FS) |
配当 名簿(に載せる)/表(にあげる) |
http://ui.openoffice.org/議定書s |
(米)棚上げする/(英)提議する of Contents
1 活動/戦闘 Items
2 一連の会議、交渉/完成する (米)棚上げする/(英)提議する
1 活動/戦闘 Items
Item |
Responsible |
Status |
---|---|---|
previous items |
||
Create a 概念 of ありふれた UI factory design |
FS |
立ち往生させるd |
Toolboxes in dialogs must get the 訂正する image 名簿(に載せる)/表(にあげる) 始める,決める (基準/high contrast) |
All ui developers |
open1 |
High Contrast 方式 (HC 方式) for Listboxes, Treelistboxes and Browseboxes must be 扱うd where used with bitmaps |
All ui developers |
open 1 |
Calling SetModeBitmap for all dialog 支配(する)/統制するs with bitmaps |
All ui developers |
open 1 |
Check 状況 menu 扱うing |
CJ |
done 2 |
new items |
||
check 指名するing 条約 for high contrast bitmaps, check build 過程 for high contrast image 名簿(に載せる)/表(にあげる)s |
OS |
new |
create Bug for UNO-Accessibility of BrowseBox |
FS |
new |
create design 文書 for Accessibility API of the BrowseBox |
DR |
new |
Comments on 活動/戦闘 Items
These items are waiting for the 実施 of the interfaces to 始める,決める bitmaps/image 名簿(に載せる)/表(にあげる) for high contrast 方式 and the 創造 of high contrast ready bitmaps
Regharding the 選択 upon 開始 a 状況 menu, there are different 条約s in different 製品s. The ありふれた denominator is that when 開始 a 状況 menu 経由で mouse, on an 反対する which does not belong to the 現在の 選択, the 選択 is changed to this 反対する. Differences are whether or not the 初めの 選択 is 回復するd after the menu is の近くにd.
We think that as a general 支配する, we should change the OOo behaviour so that the 選択 follows the mouse click (which 現在/一般に is not the 事例/患者), but is not 回復するd afterwards (予定 to the 成果/努力s this would 暗示する 特に for more コンビナート/複合体 scenes than a tree 名簿(に載せる)/表(にあげる) box).
2 一連の会議、交渉/完成する (米)棚上げする/(英)提議する
CJ told us that Stella nearly finished 創造 of the high contrast 見解/翻訳/版s of all our office bitmaps.
It arose that it is yet 不明瞭な how these new bitmaps are to be use to 生成する image 名簿(に載せる)/表(にあげる)s. 現在/一般に, the bitmap 道具 decides from the first two letters of the 生産(高) 指名する of a image 名簿(に載せる)/表(にあげる) which input bitmaps to use - this would 要求する new 指名するing 条約s for the high contrast images (現在/一般に they have a suffix "_h").
OS is to 明らかにする this.DR told there there still does not 存在する a formal bug for the UNO Accessibility of the BrowseBox. FS is to 令状 one.
Given that there is the 可能性 that DR can't finish the Accessibility 実施s for the BrowseBox, FS asked DR to create some specification 文書 for the to-be-器具/実施するd API, to 緩和する a possible later handoff.There was a discussion about the cursor 支配(する)/統制する in the BrowseBox (おもに in the database 構成要素s). 現在/一般に, there are some inconsistencies between the BrowseBox, Calc Sheets and (米)棚上げする/(英)提議するs in Writer. Some of the different behaviour does make sense, some perhaps doesn't.
The attendees agreed that a 包括的な 解答 would 要求する 広範囲にわたる specification 成果/努力, and that it would not be 価値(がある) it, as there are no real problems with the 現在の behaviour.PB told us of a 業績/成果 problem in the Accessibility API of the ComboBox. As it was decided that a combo and 名簿(に載せる)/表(にあげる) boxes expose all their 入ること/参加(者)s (even the not 明白な ones) as children, we may have a problem with AT 道具s. For example, 接近ing the ComboBox in the Help 構成要素 (with about 4000 入ること/参加(者)s) with the JavaMonkey takes a very long time which 妨げるs reasonably working with it.
As soon as a 製品 build is 利用できる with the API 実施s in the combo box, PB will do some profiling to 調査/捜査する the 推論する/理由 of the 業績/成果 problem. It may be possible that the 概念 as such (expose all 入ること/参加(者)s as 反対するs) is the problem itself. Together with the さまざまな 橋(渡しをする)s 伴う/関わるd, the problem may be inherent ....FS asked whether or not the 現在の toolbox design is final. He (人命などを)奪う,主張するd that 特に the visualization of "checked" toolbox slots is suboptimal. CJ told us that Stephan Schaefer is still not finished with the 実施s, and 特に the checked slots are to be 改善するd.
Page