|
Date |
September 13th 2001 |
|---|
週刊誌 使用者 Interface 会合
TODOs
|
Previous week's TODOs |
Responsible |
Status |
|---|---|---|
|
Create a team section on staroffice-doc and on OOo |
OS |
In 進歩 |
|
決定する and publish 責任／義務s |
OS |
In 進歩 |
|
New TODOs |
|
|
|
組み立てる／集結する 名簿（に載せる）／表（にあげる） of UI 構成要素s/classes/dependencies |
OS |
|
|
check if ありふれた UI code can/should be moved from SfxApplication to OfficeApplication |
FS |
|
場所 of the new UI 事業／計画（する）(s)
A lot of the ありふれた UI classes uses 専攻するd SfxPoolItems which are 位置を示すd in SVX. This means that the new UI 事業／計画（する）(s) need to be 位置を示すd above SVX. On the long 称する，呼ぶ／期間／用語, this dependency should be 除去するd, but at the moment having it would 緩和する the 移住.
OTOH, the 事業／計画（する）s should be below OFFMGR, which would be a main （弁護士の）依頼人 of the functionallity.
Configuration
It seems 望ましい to have a 分離 of configuration data, to distinguish between 枠組み UI data and 使用／適用 UI data. At the moment, this is no 最初の／主要な goal for 実現可能 推論する／理由s.
Customizeable UI
On the long 称する，呼ぶ／期間／用語, SO should have customizeable UI in a sense (at least) that vendors can 取って代わる dialogs, menus, toolboxes etc. with their own 実施s. For this, the question rose where the line between exchangeable and not-exchangeable 構成要素s should be draw. For instance, it seems difficult to 許す to 交流 選び出す／独身 tab-pages in ありふれた dialoges. This would make the interface of such 構成要素s very コンビナート／複合体 (and probably expensive).
Instead, it seems reasonable to （人命などを）奪う，主張する that (only) dialogs as a whole are exchangeable. For this, such a dialog 構成要素 would 簡単に work on an 反対する which can be passed (e.g. the 形態／調整 which's 所有物／資産／財産s are to be changed), this way keeping the interface rather simple. Our “default 実施s” then would have the 十分な 力／強力にする of all the ありふれた helpers (SfxItemSet etc.), without the need to model this in UNO.
Taking an 在庫
As not everybody has a （疑いを）晴らす perception about the 量 of classes/helpers which are now in the 責任／義務s of the UI team (特に FS complained), OS is to 組み立てる／集結する of 名簿（に載せる）／表（にあげる） of them, 含むing dependencies to the different 事業／計画（する）s which at the moment 含む／封じ込める ありふれた UI (TODO).
After this, the splitting/再編成するing of all this code can be discussed, 含むing questions about which 構成要素s should be 負担d on 需要・要求する etc.
Preferred 使用／適用 class
In the course of the 近づいている changes, we should have a （疑いを）晴らす 責任／義務 for the 使用／適用 UI. At the moment, the SfxApplication (sfx2) 同様に as the OfficeApplication (offmgr) both take a part of them. To have a （疑いを）晴らす distinction between 枠組み and office UI, it seems 願望（する）d to move the latter to the OfficeApplication. FS will discuss this idea with MBA and see if there are any 反対s from the 枠組み 味方する.
発言／述べる: All 初期のs for 指名するs should be 解釈する／通訳するd as <初期の>@openoffice.org
