開発 Sections: Developer 事業／計画（する）s | 事業／計画（する） Structure
Developer 事業／計画（する）s
Below is a 名簿（に載せる）／表（にあげる） of 事業／計画（する）s which could be 器具／実施するd by 利益／興味d developers. Most of these 事業／計画（する）s are 比較して self-含む／封じ込めるd, and do not 要求する too much knowledge about OOo's code 組織／基盤／下部構造.
公式文書，認める that this 名簿（に載せる）／表（にあげる） doesn't （人命などを）奪う，主張する to be a 完全にする repository of what will be done in the 近づく/medium 未来. There may be items on the 名簿（に載せる）／表（にあげる） which will never be realized, and there definitely are items which are not on the 名簿（に載せる）／表（にあげる）, but will be 器具／実施するd.
If you are 利益／興味d in anything from the 名簿（に載せる）／表（にあげる）, please speak at dev@dba.openoffice.org. We'll 喜んで help you to get started on this.
Also, make sure you don't 行方不明になる OpenOffice.org's 全世界の TODO 名簿（に載せる）／表（にあげる）, which also 含む／封じ込めるs 利益／興味ing 事業／計画（する）s for developers.
Here is what you'll find below:
- Joins in dBase queries
- SDBC driver for LDAP directories
- New/高めるd Form 支配（する）／統制するs
- Dialogs with Form Functionality
- Database driver UI modularization
- HSQLDB: 選び出す／独身-とじ込み／提出する backend
- Embed Derby into OpenOffice.org databases
- native, cross-壇・綱領・公約 接近 to MS 接近 databases
- SDBC driver for vCards
- New Filter Dialog
General 公式文書，認めるs
Whenever we talk about 使用者 interface work, this 暗示するs working with VCL, the
Visual Class Library in OpenOffice.org. If you are not familiar with it, you
will 悪口を言う／悪態 it, since 特に some of the older parts never heard the word
"documentation". On the other 手渡す: In opposite to the native 壇・綱領・公約
支配（する）／統制するs, everything is there as source code, so if you like "learning by
debugging", you will love VCL
.
Additionally, be aware of the fact that feature 実施s in OpenOffice.org 要求する a specification (you may visit the specifications 事業／計画（する） for more （警察などへの）密告，告訴（状）). There's a 支配する that nothing is checked into the master 支店 which doesn't have a specification which all stakeholders agreed upon - so unlike other open source 事業／計画（する）s you may know, the specification really is an important part. Stakeholders are: the documentation team, the 使用者 experience team, the 質 保証／確信 team, and 開発. Usually, one 代表者／国会議員 from every team needs to 受託する your specification.
井戸／弁護士席, don't let this 妨げる you in starting. Just be aware that there will be a time when a specification is finally needed. Most developers don't like 令状ing such 文書s (and some people even （人命などを）奪う，主張する that they shouldn't). Thus, you need to 明らかにする who will take this for you, if you can't/don't want.
A 公式文書，認める about the 成果／努力: This is a rather rough guess at the moment. In general, it may be a good idea to 追加する two or more weeks or so 簡単に for becoming familiar with the code and some 概念s, so if it is "2 weeks", don't 推定する／予想する to start today and finish it in 14 days ...
Joins in dBase queries
The descirption of this 事業／計画（する） has been moved to our Wiki.
SDBC driver for LDAP directories
The description of this 事業／計画（する） has been moved to our Wiki.
New/高めるd Form 支配（する）／統制するs
The description of this 事業／計画（する） has been moved to our Wiki.
Dialogs with Form Functionality
description
When creating a form, the 使用者 always needs to bother with a Writer (or Calc or Draw) 文書. Very often, this is much too oversized. It would be 十分な to have a simple dialog which 含む／封じ込めるs all the data 接近 支配（する）／統制するs. Now that we have UNO-based dialogs (in the Basic IDE), this is possible in general, as there already are some basics for doing this. There still would be a lot of work to be done (not について言及するing the 固める／コンクリート design), but since some months, it's at least possible.
The advantage would be to not 殺す the 使用者 with things she does not bother – a writer 文書 申し込む／申し出s a lot of 可能性s which are not 関連した for a form. In some 事例／患者s, a 十分な writer 文書 does even 否定する to what 使用者s 推定する／予想する from a form – one thing to について言及する here is that 文書s are always 自由に sizable (and even do autosizing によれば the previous instance of the same 文書 type, the 審査する 決意／決議, whatever), which is nothing you 推定する／予想する from a carefully designed form, where 支配（する）／統制するs are placed at 固める／コンクリート positions and have a 直す／買収する，八百長をするd size.
| 要求するd 技術s |
|
| useful 技術s |
|
| 概算の 成果／努力 | 3 months |
| difficulty | high |
Database driver UI modularization
description
OpenOffice.org Base follows a 構成要素-oriented approach for enabling database 接近. For this, database drivers are 任命する／導入するd in OpenOffice.org which 供給する 接近 to a 確かな (class of) database(s).
While at the driver level, the 実施 is pretty good modularized, the UI 実施 can be 改善するd. 現在／一般に, there are a lot of places in the code with hard-coded （警察などへの）密告，告訴（状）, such as "database X 要求するs UI 選択 Y".
The goal of this 事業／計画（する） is to design and 器具／実施する a reasonable architecture for bringing a driver to the UI. The 存在するing 実施 needs to be migrated to this new architecture. As a proof of 概念, an 存在するing 現在／一般に-外部の driver (e.g. the native PostgreSQL driver) should be 修正するd so that it can be （軍隊を）展開する，配備するd into an OOo 取り付け・設備 and makes use of the features of the new architecture.
| 要求するd 技術s |
|
| useful 技術s |
|
| 概算の 成果／努力 | 2 months |
| difficulty | high |
HSQLDB: 選び出す／独身-とじ込み／提出する backend
description
HSQLDB is the default database engine used by OpenOffice.org Base.
HSQLDB 現在／一般に creates a number of 隣接する とじ込み／提出するs to 蓄える／店 its data, where all とじ込み／提出するs together 構成する the whole database. To 許す the 使用者 of OpenOffice.org Base to have a "all-in-one-とじ込み／提出する" database experience, those HSQL とじ込み／提出するs are 現在／一般に embedded in some OOo-明確な／細部 コンテナ-とじ込み／提出する (the .odb とじ込み／提出する).
To 打ち勝つ さまざまな disadvantages of this approach, it is 望ましい that HSQL 蓄える／店s its data in a 選び出す／独身, large とじ込み／提出する. 予選 code and 概念s 存在する for this, but no final 実施.
The に引き続いて 事業／計画（する） description was 供給するd by Fred Toussi, HSQLDB 事業／計画（する） owner:
現在／一般に, HSQLDB 蓄える／店s the database （警察などへの）密告，告訴（状） in four separate とじ込み／提出するs. These とじ込み／提出するs are written to using different API?s. Streams are used for some while 無作為の 接近 is used for others.
The 事業／計画（する）?s 目的（とする） is to 許す a 選び出す／独身 とじ込み／提出する to be used for all 永久の data (一時的な 開会／開廷／会期 data, or とじ込み／提出する locking may still use a separate とじ込み／提出する). So 存在するing とじ込み／提出するs that need to be 統合するd into one are the .所有物／資産／財産s, .スピードを出す／記録につける, .data and .backup とじ込み／提出するs. The new 選び出す／独身 とじ込み／提出する will be 接近d only as a 無作為の 接近 とじ込み／提出する.
The 事業／計画（する） consists of developing an interface between 存在するing code. At the low level, there is already an 実施 of a 無作為の 接近 とじ込み／提出する, org.hsqldb.固執する.ScaledRAFile. The new interfaces will 許す 存在するing とじ込み／提出する services to use the 選び出す／独身 無作為の 接近 とじ込み／提出する.
All the とじ込み／提出するs in the org.hsqldb.固執する 一括 should be 熟考する／考慮するd, with the understanding that the functionality of many of these とじ込み／提出するs, 含むing lock and 所有物／資産／財産 saving functionality, will become redundant with the introduction of 選び出す／独身 とじ込み／提出する persistence.
The student is 推定する／予想するd to 熟考する／考慮する and become proficient in the Java IO 一括s and the API calls to these 一括s 現在／一般に made from HSQLDB, and 令状 the code and 実験（する） 一括s.
The 助言者 will 供給する 正規の／正選手 指導／手引 and help on the design of 要求するd interfaces and 監督する their 実施.
As this is considered an 必須の 開発 for HSQLDB, all the work done by the student will be used, and if necessary, 修正するd or 改善するd by other 事業／計画（する） developers. The student will get 予定 credit and will be 供給するd with work 言及／関連s by the HSQLDB 事業／計画（する） Maintainer upon successful 完成 of the 事業／計画（する）.
| 要求するd 技術s |
|
| useful 技術s |
|
| 概算の 成果／努力 | 2 months |
| difficulty | high |
Embed Derby into OpenOffice.org databases
The descirption of this 事業／計画（する） has been moved to our Wiki.
See also some old （警察などへの）密告，告訴（状） on this topic from the dba@dev.openoffice.org 古記録s.
Native, cross-壇・綱領・公約 接近 to MS 接近 databases
description
予選 公式文書，認める: In the 合間, there is an alpha 見解／翻訳／版 of a driver for this. It's an OOo database driver which uses MDB 道具s to read MS 接近 databases. See it's home page for more info.
A major goal of OpenOffice.org is interoperability with other office 使用／適用s, 特に with a 確かな office 控訴 which 現在／一般に has some greater market 株 than OpenOffice.org has :).
Unfortunately, 現在／一般に OOo 使用者s, as long as they don't work on Windows, are not able at all to 接近 the databases of this office 控訴 - we cannot read MDB とじ込み／提出するs on 壇・綱領・公約s other than Windows (where we can use Microsofts own API).
So the goal here is to 許す Linux 使用者s to at least read the data from MDB とじ込み／提出するs, using OOo.
There are several ways how this could be done.
One is to use MDB 道具s, and 包む them in OOo. Since the SQL 能力s of the MDB 道具s parser are
限られた／立憲的な (e.g., no OR 条件s in WHERE 条項s are 許すd), this 要求するs work in either MDB 道具s
itself (by 改善するing their parser), or it would be used as provider for raw data, and OOo would faciliate
it's own parser/query engine (which unfortunately is also 限られた／立憲的な) to 過程 this data.
Another 現在の disadvantage of MDB 道具s is that it doesn't 扱う UTF8, and since jet4 databases
蓄える／店d their data in UTF8, this 暗示するs that it cannot be used for jet4 databases 含む／封じ込めるing 非，不，無-ASCII
characters (井戸／弁護士席, probably a little bit more that ASCII, but it's a serious 制限 for an 製品 as
international as OpenOffice.org).
Another way would be to re-engineer the MDB 判型 ourself, and 令状 a native SDBC driver (which could be in C++ or probably even in Java) which 供給するs the data. This is 類似の to the first approach, where MDB 道具s would have been used as the provider of raw data.
| 要求するd 技術s |
|
| useful 技術s |
|
| 概算の 成果／努力 | 2 months |
| difficulty | medium |
SDBC driver for vCards
description
OpenOffice.org has it's own open database 接近 API called SDBC which is modeled on the architecture of Java's JDBC. SDBC supports several databases and database-like API's 経由で an extensible provider architecture; ODBC 3.0, JDBC, ADO, dBase and CSV are の中で the databases and database 管理／経営 systems 現在／一般に supported. Each SDBC provider is 器具／実施するd as a UNO 構成要素.
It could be useful to have a 献身的な driver for 接近ing vCards. There is an 組織／基盤／下部構造 in the 存在するing SDBC 実施s for とじ込み／提出する-based databases, which could be 比較して easily 専攻するd for vCard 接近. This would broaden the 範囲 of 演説（する）／住所 調書をとる／予約する data which can be used in OpenOffice.org.
| 要求するd 技術s |
|
| useful 技術s |
|
| 概算の 成果／努力 | 2 weeks |
| difficulty | medium |
New Filter Dialog
description
類似の to the Sort Dialog, there is a dialog which 許すs to filter queries and （米）棚上げする／（英）提議するs – it can be reached the same way as the sort dialog, by using the "Default Filter..." button in the toolbox of the data source browser.
This dialog 苦しむs from some disadvantages:
- it's not dynamic, three filter criterions are the 最大限
-
The dialog does not really 明確に distinguish between ORing and ANDing
filters. Though there the 使用者 can make a choice for AND or OR, it's not （疑いを）晴らす
what is the result if these are
mixed. This UI is 簡単に not
intuitive.
One other place where a 類似の functionality is 利用できる is the filter 航海士 in the form based filter.
This will show the いわゆる filter 航海士, which uses a tree 見解（をとる） to 代表する the 現在／一般に used filter for the form. It has other disadvantages
- it's impossible to 追加する a filter with two AND criterions for the same column, such as "指名する LIKE '%Foo%" and "指名する LIKE '%妨げる／法廷，弁護士業%'".
- it's not intuitive, too (井戸／弁護士席, this is personal taste :)
-
some functionality cannot be 接近d from within the 航海士, but only by
entering text in the form fields (for instance, try creating a new filter in a
form which 以前 does not have any filter
If the interface of the new 実施 of the filter 支配（する）／統制する in the new filter dialog is abstract enough, then on the long 称する，呼ぶ／期間／用語 we can use it for the filter 航海士, too. This would 要求する some discipline in designing the classes for the new 実施s, and some abstraction 能力s. However, this is not the 最初の／主要な goal of this 実施.
| 要求するd 技術s |
|
| useful 技術s |
|
| 概算の 成果／努力 | 1 month for an experienced developer |
| difficulty | medium - high |
