OpenOffice.org |
週刊誌 会合 ありふれた 使用者 Interface (CUI)
Date |
July 11th 2002 |
---|---|
Time |
10:00h, MEST |
場所 |
Cupertino, eham-02 |
Attendees |
Daniel Rentz (DR) |
Minute Taker |
FS (next: PB, GT, MMP, CL, OS, DR) |
配当 名簿(に載せる)/表(にあげる) |
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 (予定 July 2002) |
提案 for Accessibility (焦点(を合わせる), keyboard) of (a)自動的な/(n)自動拳銃 Help スパイ/執行官 (the window with the bulb) |
CJ |
立ち往生させるd |
取って代わる 黒人/ボイコット color in 国境 判型 支配(する)/統制する in HC 黒人/ボイコット 方式 |
FS |
open |
調整する with GSL team for support of PNG images in toolboxes |
CJ/MMP |
in 進歩 |
new items |
||
break 負かす/撃墜する the PDF 輸出(する) spec to 選び出す/独身 問題/発行するs, 割り当てる to responsible developers (2.1) |
MMP/FS |
|
令状 bug to 調和させる the different "don't mind me again" texts |
DR |
|
collect 必要物/必要条件s for 資源-level support of HC images/bitmaps |
CL |
|
collect (警察などへの)密告,告訴(状) about behaviour when scrolling over 非,不,無-焦点(を合わせる)d windows |
CJ |
|
2 円卓会議の
2.1 PDF 輸出(する)
2.1.1 Specification
The 提案 for the PDF expoert feature is in a final 明言する/公表する, and has been published on openoffice.org (発表するd in the mailing 名簿(に載せる)/表(にあげる)s of the UI 構成要素). The next step is to break 負かす/撃墜する the spec into 選び出す/独身 問題/発行するs, which can be 割り当てるd to developers to 器具/実施する.
2.1.2 PDF Quick Print
MMP 報告(する)/憶測d that there is an open 問題/発行する whether or not we want to have a icon to "quick-print" a 文書 to PDF. 普通は, we would like to have an icon in the 機能(する)/行事 妨げる/法廷,弁護士業. The problem is that Adobe owns the 権利s for the 井戸/弁護士席-known PDF icon, so we would be 軍隊d to use an icon which in no way can be associated with PDF, which 明白に would not make any sense then. 調査s about how to solve this are 進行中で, but an 結果 like "we don't want to have this functionality in the toolbar at all" is やめる likely.
2.2 "Mensch und Computer"
MMP again reminded the attendees that in beginning of September, there is a 会議/協議会 called "Mensch und Computer" (hmm – "human and computer"?) in Hamburg, and whoever is 利益/興味d in this should consider …に出席するing.
2.3 Notifications 経由で Message Boxes
2.3.1 suppressable 警告s
DR told that 現在/一般に, there are at least 3 different texts in 状況/情勢s where the 使用者 is 警告するd for some 推論する/理由, and the 警告 box 含む/封じ込めるs a text like "don't remind me again". DR will care that a bug for this is beeing とじ込み/提出するd, and 延長する the interface of the 各々の VCL classes so that (弁護士の)依頼人s can use a ありふれた text for this.
2.3.2 Escalation of Notifications
によれば MMP and CJ, there are 4 escalation levels for 通知するing the 使用者:
- Hint/Info: This is just a simple message box with a text and an 承認する button. No 決定/判定勝ち(する) is 要求するd from the 使用者, this is only an info
- Question: A question, which 要求するs to chose between at least 2 代案/選択肢s (mostly "yes" and "no")
- 警告: A 警告 that a 過程 could result in some maybe 予期しない behaviour. Here, the 使用者 also has the chance to make a 決定/判定勝ち(する) (usually 確認する that the consequenses are really ーするつもりであるd or at least 受託するd)
- Error: Such a notification 報告(する)/憶測s a serious error to the 使用者 – here something already went wrong
All 4 levels are 現在/一般に 反映するd in 各々の classes in VCL (InfoBox, QueryBox, WarningBox, and ErrorBox), and every developer should carefully decide what is the appropriate escalation level for his/her special シナリオ.
2.3 High Contrast Images in VCL classes
CL 勧めるd to その上の 追求する the idea of 延長するing our 資源 判型 to support high contrast (HC) images and bitmaps. によれば CL, the 成果/努力 to 追加する HC support to 存在するing UI elements 純粋に on the code level is やめる high. An example for this are toolbars which do not use one large image 名簿(に載せる)/表(にあげる) as source, but 選び出す/独身 icons for every item (for instance because the toolboxes are composed from already existent images, which, for さまざまな 推論する/理由s, have different 指名するing 計画/陰謀s such as "sc*", "sx*", "<whatever>*"). 現在/一般に, making such toolboxes HC-有能な is expensive. CL 示唆するd to 再考する the idea to 追加する 資源-level support for this, which would 緩和する the whole 過程 a lot.
CL will collect the 必要物/必要条件s for this, so that we can discuss them with the VCL team (すなわち Stefan Schaefer), who would have to 器具/実施する the 資源-level support.
2.4 Scroll Mouse support
There was a discussion about the 推定する/予想するd behaviour of windows which are not 焦点(を合わせる)d, but scrolled using a scroll mouse. There are at least three possible behaviours when the 使用者 uses the scroll wheel, while the mouse points to a window which is not 焦点(を合わせる)d:
- 焦点(を合わせる) the window, then scroll it
- don't 焦点(を合わせる) the window, but scroll it
- scroll the window which is 現在/一般に 焦点(を合わせる)d, no 事柄 where the mouse points to
Looking at some real world programs, at least 1. and 3. can be 遭遇(する)d. The attendees agreed that 2. would be the best behaviour.
OOo itself 現在/一般に relies on what the system 供給するs - it is not (疑いを)晴らす whether we should 演説(する)/住所 this, and if there is a reasonable 需要・要求する.
CJ will try to collect some more info about the behaviour of other programs.
Page