Interview: Mathias Bauer, Lead, 使用／適用 枠組み 事業／計画（する） and J?rgen Schmidt, Lead, API 事業／計画（する）
2006-07-03
Mathias Bauer and J?rgen Schmidt are two of the 重要な developers taking OpenOffice.org to the next 行う／開催する／段階. Lead of the 使用／適用 枠組み (枠組み) 事業／計画（する）, and a 経営者／支配人 of ソフトウェア 工学 at Sun Microsystems, Mathias has long 補助装置d in the 開発 of 非常に／多数の facets of OpenOffice.org growth. As lead of the API 事業／計画（する）, and also of Sun, J?rgen 調整するs our API 政策s and 開発. Both 事業／計画（する）s are 決定的な to the 未来 of OpenOffice.org's growth and direction as a 製品 and open-source 事業／計画（する）. This interview, 行為／行うd 経由で email earlier this month, is part of a series 捜し出すing to chart the 形態／調整 of things to come for OpenOffice.org.
With 2.0 OpenOffice.org 器具／実施するd a 科学（工学）技術 that 許すs for the more or いっそう少なく 平易な 傾向 of 拡張s and thus new features on a rolling basis. Can you speak on the nature of the 科学（工学）技術 and what sort of 拡張s developers should be 利益／興味d in working on?
From the developer's point of 見解（をとる） OpenOffice.org 2.0 was the starting signal for an 改善するd way of developing OpenOffice.org 拡張s.
We 追加するd new amazing features to UNO and started to use them in our API. This needs to develop in the 未来 and we are are already working on this 現在進行中の 仕事. We 追加するd the new 一括 経営者／支配人 GUI as a graphical 前線-end to 簡単にする the 取り付け・設備 of 拡張s. Our 一括 判型 was 延長するd and now can 含む／封じ込める 独断的な content that is 述べるd in a structured and defined manner. One of our main goals was to 延長する the feature 始める，決める for 拡張s that want to 統合する with the OpenOffice.org GUI, 特に for our so called 追加する-Ons that use a configuration とじ込み／提出する approach for their 統合，差別撤廃. These 拡張s can be compared to what you might know from Mozilla or Firefox, though admittedly our 追加する-Ons still have much いっそう少なく 影響（力） on the OpenOffice.org GUI; on the other 手渡す, they also are much いっそう少なく 傾向がある to 見解／翻訳／版ing problems. As explained later, 申し込む／申し出ing more and tighter 統合，差別撤廃 into the OpenOffice.org GUI without getting the ugly 見解／翻訳／版ing problems is one of our main goals for その後の 見解／翻訳／版s of OpenOffice.org.
So, if you are planning to create OpenOffice.org 拡張s, don't ask what is possible, join us on the dev@api.openoffice.org mailing 名簿（に載せる）／表（にあげる） and discuss with us what needs to be done to make something possible. We are very 利益／興味d in the ideas of the developer community about what is 行方不明の and what can be 改善するd. This 含むs APIs, 統合，差別撤廃 interfaces, 開発 道具s and so on. [公式文書，認める: as with most of our 名簿（に載せる）／表（にあげる）s, you must be subscribed to 地位，任命する; send blank email to dev-subscribe@api.openoffice.org. All 名簿（に載せる）／表（にあげる）s are public. -Ed.]
I would 追加する that the new (and still under construction) 拡張s 事業／計画（する）, 始めるd by Laurent Godard last year 代表するs a superb 適切な時期 for new and experienced developers. The 事業／計画（する） centralizes （警察などへの）密告，告訴（状） 関心ing 拡張s to OpenOffice.org. It's an ideal 事業／計画（する） for developers 利益／興味d in 延長するing OpenOffice.org's functionality. 拡張s could 範囲 from usability modules that 満足させる usability 需要・要求するs to accounting 一括s to anything else that imagination and 技術 許す.
Another question: OpenOffice.org uses Java for Base 同様に as other things. Yet, there are very few Java apps that 延長する OpenOffice.org functionality. What can be done to 改善する that?
As 発表するd on the last OpenOffice.org 会議／協議会 in Koper we are working on an 統合，差別撤廃 of our 開発 道具s into the NetBeans and （太陽，月の）食／失墜 IDEs. Developers should be able to create UNO 構成要素s and OpenOffice.org 拡張s with the help of wizards that 解放する／自由な them from the boring 決まりきった仕事 work and 速度(を上げる）s up the 開発. While the NetBeans work is done in Hamburg, the （太陽，月の）食／失墜 統合，差別撤廃 is 供給するd by a very active member of our 開発 community, C?dric Bosdonnat, who joined the 事業／計画（する） by working with us on a Google Summer Of Code 事業／計画（する） last year. We and C?dric 同様に will 現在の results on the next OOoCon in Lyon.
With 2.0 we made a big splash--new 科学（工学）技術, new features, new とじ込み／提出する 判型. Of course, many of these things had been introduced in 1.x but 2.0 (or anyway the 1.9.x line) was 明確に technologically novel. Do you see something like that for "3.0"? Can you hint (or better yet, 明示する) what new APIs and 科学（工学）技術 it might 含む? (And yes, am aware that "3.0" is a little bit of a marketing 手段.)
After 2.0 we changed our 解放（する） model to having more たびたび（訪れる） feature 解放（する）s. This has an 衝撃 on the way we develop features: they will be 統合するd into the 製品 when they are done and at that point in time they need to have 製品 質 because we will not have an 延長するd beta 段階 for each and every 解放（する）. So on our way to a 見解／翻訳／版 that deserves the "3.0" 見解／翻訳／版 number we will 解放（する） several minor and micro 解放（する）s and a beta 見解／翻訳／版. This beta will 許す us to 統合する some "big" features that we don't dare to 配達する in a smaller 解放（する） time でっちあげる，人を罪に陥れる.
We are still trying to live in this new world and so at the moment we don't have an exact 計画（する） what will be done until the 3.0 解放（する）. We don't want to talk about individual 使用者 features here, instead of this we can tell you what we are 現在／一般に working on in a more general way:
- 業績／成果 改良s (startup, 負担ing and saving)
- 安定 (not just bug 直す／買収する，八百長をするing, more in a sense of refactoring)
- modularization of the code base (not as a "big bang", it's a continuous 成果／努力)
- looking for features that we can 器具／実施する together with other members of the community
- 改善するing the 開発 道具s (IDE support)
- 改善するing and 延長するing our API
- （軍隊などの）展開，配備 of "非，不，無 code" content as 拡張s, e.g., templates, gallery items, etc.
- 改良s in the area of 拡張 維持／整備 and （軍隊などの）展開，配備 -- (見解／翻訳／版ing, dependencies, licencing, 調印, updating)
A 重要な point for the 統合，差別撤廃 of 拡張s is the extensibility and accessibility of the 使用／適用 GUI and so we are 現在／一般に working on the APIs for this 統合，差別撤廃 and their technical base in the code. As a first step in the 2.0.3 解放（する） we have more toolbar 支配（する）／統制するs for 追加する-Ons that 許す much more コンビナート／複合体 interactions.
Another important 新規加入 in 2.0.3 is the ability to 輸出（する） basic libraries as UNO 一括s in the Basic IDE that will make the （軍隊などの）展開，配備 of basic 大型のs a lot easier.
Where should developers look to learn more? I would, for instance, recommend the developer wiki, but also the 開発 page, for starters, and then 攻撃する，衝突する the 重要な 名簿（に載せる）／表（にあげる）s, such as dev@openoffice.apache.org, dev@api.openoffice.org, and so on.
In the past all 開発 関係のある （警察などへの）密告，告訴（状） was collected on the 道具s.openoffice.org and 開発.openoffice.org page. Both pages also 申し込む／申し出 a lot of links to other 利益／興味ing pages. While these pages will still be the point where you can get the "whole story," we started with a wiki in last November that not only 許すs you to 追加する or change content more quickly but also 焦点（を合わせる）s on an easier 消費. You can find the wiki at http://wiki.services.openoffice.org/wiki/ . It is a 急速な／放蕩な growing 資源 that already 含む／封じ込めるs a lot of 出資／貢献s from OpenOffice.org developers around the world.
If you are 利益／興味d in 構成要素 or 拡張s 開発 and you have already swallowed the basics you can 会合，会う us on our 開発 名簿（に載せる）／表（にあげる）s, 特に the dev@api.openoffice.org and dev@openoffice.apache.org mailing 名簿（に載せる）／表（にあげる）s.
It's also important to 追加する that we are very 利益／興味d and committed to bettering the OpenOffice.org experience for developers new to the 事業／計画（する）. For instance, there's an 現在進行中の 成果／努力 to 改善するing the developer documentation, and a wiki has been started that features examples and tutorials. 同様に, our Code-Snippet Base, which has many useful snippets of code, is still growing. It's probably the easiest place for a developer's first 出資／貢献s.
What new features or 科学（工学）技術 do you think 長所 most attention?
We think that 特に the IDE 統合，差別撤廃 and the 拡張 （軍隊などの）展開，配備 改良s will be important for 拡張 developers. The first because it should make their life easier, the second because it makes the whole system reliable and usable even in the long 称する，呼ぶ／期間／用語.
Speaking 一般に, what is the most 利益／興味ing developer feature you would like to see その上の developed or 器具／実施するd?
As we are thinking that the 入ること／参加（者） to OpenOffice.org 開発 is still not an 平易な 仕事 and we would like to move away some 障壁s by 簡素化するing our APIs and modularizing the code base. This will 減ずる the 複雑さ that new developers 直面する nowadays. Another very important feature is the API for GUI programming with OpenOffice.org.
What about いわゆる "核心" 開発? That would seem to be in many ways one of the most 決定的な 開発 areas....
Now we talked a lot about APIs and UNO and how to work with it. But of course OOo 開発 is more than this: many of us work with the C++ code, the "核心 modules" and this is still the preferred or even the only way to work on bigger features, 特に if they need a lot of UI code.
We would love to get some more developers 伴う／関わるd in this and work together with us. We know that there are a lot of 障壁s, but we are trying to lower or even 除去する them.
The first 障害 seems to be the build 環境, but that's not my playground, so I leave it up to others like ツバメ Hollmichel and Kai Backmann to talk about it.
A developer that got himself used to the build 環境 usually will ask questions like these:
- Where do I start my 開発?
- How can I understand how the code 作品?
- How can I find the code of a particular feature?
- Where can I 追加する a new feature I want to develop?
You can get some help from OOo developers on IRC [irc.freenode.逮捕する, #OpenOffice.org] or the [事業／計画（する）] mailing 名簿（に載せる）／表（にあげる）s, but this is a time 消費するing 過程 that doesn't 規模 very 井戸／弁護士席. We need to enable 利益／興味d developers to find their way into the code with much いっそう少なく 永久の help from our 味方する than now. I think we can 演説（する）／住所 these questions by 供給するing more and better documentation and 文書d code examples. There is already some （警察などへの）密告，告訴（状） 利用できる in the 急速な／放蕩な growing OpenOffice.org Wiki at
and the code snippets database at
but additionally we could:
- 述べる the general module architecture of the code base
- Explain the general code architecture of the OOo 枠組み and 使用／適用s
- 割り当てる features to code modules
- 述べる typical 実施s
and many things more. I hope to talk about this in my 贈呈 at the OOoCon and I'd love to hear suggestions from the community about what else we could do. [The programme to the 会議／協議会, which takes place 11-13 September, in Lyon, will be published すぐに. But all developers of OpenOffice.org should 本気で consider …に出席するing this 会議／協議会, as it 申し込む／申し出s the chance to discuss 核心 科学技術の 問題／発行するs 直面する-to-直面する with the lead developers.]
Thanks! As について言及するd, this is the first in a 一連の interviews 焦点（を合わせる）ing on the 現在の and 未来 科学（工学）技術 of OpenOffice.org. 心配するd interviews 含む one ツバメ Hollmichel, of 道具s, and other 事業／計画（する）s, and probably one of the most important 解放（する） engineers.
Return to Articles
