Graphic System 層事業／計画（する）

事業／計画（する） Lead: Philipp Lohmann

The Graphic System 層 (GSL) 事業／計画（する） is an umbrella 事業／計画（する） to 供給する graphic 生産（高） on different 装置s. Graphic 生産（高）言及するs to a 範囲 of 操作／手術s starting from simple line 製図／抽選 to コンビナート／複合体 raster 操作／手術s. その上に it 含む／封じ込めるs a 始める，決める of widgets and different APIs to make use of them. The most 目だつ examples for 装置s are of course computer 陳列する，発揮するs and printer.

The Visual Class Library (VCL) is the most 目だつ module of the 事業／計画（する）. It 含む／封じ込めるs 実施s for 根底となる概念s like windows, fonts, bitmaps, widgets (buttons, menus, ...) and so on. The 組織／基盤／下部構造 VCL 供給するs is ひどく used throughout all higher level 組織／基盤／下部構造層 and the different OpenOffice.org 使用／適用 modules. VCL lets OpenOffice.org look and feel the way it does. VCL 供給するs an 外部の operating system 独立した・無所属 API to higher level modules an 内部の API for 器具／実施するing those in a system 扶養家族 manner. 現在の実施s 供給する support for Microsoft Windows and Unix/XWindow based systems. The latter is used for the Mac OS X port 同様に (A その上の事業／計画（する） uses Java for 実施, however it's not hosted on OpenOffice.org). If you 計画（する） to port OpenOffice.org to a new 壇・綱領・公約 then it's probably 価値（がある） to have a look at VCL.

GSL and VCL are いつかs used as synonyms which is way too simple. GSL 含む／封じ込めるs a lot more modules than just VCL, a 完全にする名簿（に載せる）／表（にあげる） is given below.

Module	機能（する）／行事
Modules in the Graphic System 層事業／計画（する）
`accessibility`	Accessibility 道具s 橋（渡しをする）s (e.g. java accessibility 橋（渡しをする）)
awb	Accessibility workbench for checking accessibility 橋（渡しをする）s
awttools	Accessibility 実験（する） programs
basebmp	Base classes for bitmap 巧みな操作
canvas	実施 of a new graphical 生産（高）層 designed to 取って代わる vcl's OutputDevice
cppcanvas	C++ wrappers and helper classes for canvas
dtrans	System 明確な／細部交換 (e.g. clipboard, drag and 減少（する）)
`forms`	実施 of 支配（する）／統制するs that can be used as forms in 文書s. Form 支配（する）／統制するs are based on VCL.
fpicker	Support for system 明確な／細部とじ込み／提出する dialogs and a generic fallback 解答
`padmin`	Printer 行政公共事業（料金）／有用性. Used on Unix 壇・綱領・公約s to configure printer 列s and 能力s
`psprint`	Printer 発見 and PostScript code 世代. In 合同 with VCL it 供給するs an 使用／適用 printing 解答 on Unix based systems. In the 3.2 codeline the psprint code has moved from its own modules into vcl to 利益 from tighter 統合，差別撤廃.
`rsc`	資源 compiler. The basic layout of dialogs and the strings that are 支配する of translation/localization are 蓄える／店d in 資源とじ込み／提出するs. The 資源 compiler creates an efficient binary 代表 out of a human readable text 判型
爆撃する	System 統合，差別撤廃: bindings to mailers and other 外部の構成要素s
sysui	System desktop 統合，差別撤廃: mimetype and とじ込み／提出する type 登録, quickstarter
`toolkit`	Toolkit 供給するs a UNO API to VCL and UNO 支配（する）／統制するs
`unocontrols`	A 始める，決める of 支配（する）／統制するs that do not 直接／まっすぐに rely on VCL. 現在／一般に器具／実施するd are a 支配（する）／統制する for downloading とじ込み／提出するs and an embeddable 文書 preview.
`vcl`	Visual Class Library, 器具／実施するs graphic 操作／手術s, window 管理／経営 and basic 支配（する）／統制するs

What's going on for OpenOffice.org 3.2 ?

Printing recode

現在／一般に on the Mac 文書s are first “printed” to a 始める，決める of metafiles, then the actual Cocoa print 職業 is started. This is necessary for two 推論する／理由s: first for a print 職業 you need to know the page 範囲 in 前進する (which the 現在の vcl printer does not) and second individual pages are “pulled” from the print system in a 無作為の manner (e.g. the preview in the native print dialog prints a page to 陳列する，発揮する it). The 現在の機械装置作品 surprisingly 井戸／弁護士席 even for large 文書s but is 自然に rather memory 集中的な.

So the 計画（する） is to move vcl's print model more in the direction of Cocoa's (that is to a model where the printer pulls pages instead of the 使用／適用押し進めるing all pages to the printer). Aside from the Mac 明確な／細部 advantage this gives us the 適切な時期 for a better print dialog 含むing a nice preview on all 壇・綱領・公約s. Also things like multipage printing can be done in an 使用／適用独立した・無所属 manner this way.
その上の Mac 統合，差別撤廃 features

Netscape plugin support 許すs to embed e.g. shockwave/flash into our 文書s like on other 壇・綱領・公約s.
改良s in OpenType font support

CFF based OpenType fonts should finally find better support (like （判決などを）下すing, printing and PDF 輸出（する）) in OpenOffice.org.
業績／成果

The 全体にわたる業績／成果 of OpenOffice.org lets room for 改良. 現在／一般に there are no known big 孤立するd 問題／発行するs that would result in 抱擁する業績／成果伸び（る）s, so we need to find lots of different small 業績／成果改良s. In the gsl area one example for these is the 統一 of different modules into one which will result in より小数の libraries to 負担 - noticeable 特に on Windows where each library nowadays is 支配する to an antivirus ざっと目を通す.

What's going on for OpenOffice.org 3.1 ?

Printing recode (didn't make it into 3.1 予定 to time 強制s)
StartCenter enhancements (didn't make it into 3.1, UX lost 利益／興味 it seems)

The StartCenter in its 現在の form will change its 直面する and feature 始める，決める; the UX team is 現在／一般に thinking about its 未来 directions. 現実に this belongs to the 枠組み事業／計画（する）, but 現在／一般に it looks like we will be helping them out.
Enhancements for RTL (権利 To Left) languages

A lot of bug 直す／買収する，八百長をするs and enhancements are on our 名簿（に載せる）／表（にあげる） for arabic, hebrew and other RTL languages.
その上の Mac 統合，差別撤廃 features

While for 3.0 the main goal was bringing the Mac port up to the 基準s of the other 壇・綱領・公約s, we hope to 強化する it beyond this with その上の統合，差別撤廃 features. Support for the Apple Remote 同様に as Apple scripting is 現在／一般に in 開発. Scripting support will start with simple things and over time make more features 利用できる through Apple script. 十分な scriptability is already possible through our 存在するing scripting 枠組み (most 顕著に using BASIC) 同様に as through the UNO 橋（渡しをする） to Java, Python and possible other languages.

What's going on for OpenOffice.org 3.0 ?

Mac/Aqua Port

The newly invigorated MacOSX (which is now a mainstream 壇・綱領・公約) porting 成果／努力伴う／関わるs a lot of work in gsl. Goal is to 解放（する） a beta 見解／翻訳／版 along with the 3.0 beta on other mainstream 壇・綱領・公約s. Some 問題／発行するs 伴う／関わるd in the port 含む:
- Porting vcl 含むing native widget 主題ing.
- Drag&減少（する）
- Support for Apple's font 判型s
- QuickTime support
- ...

What was going on for OpenOffice.org 2.x ?

その上の PDF 輸出（する） enhancements

New features were 追加するd in 2.0.4: encrypted PDF and setting さまざまな使用者接近許可s. Support for PDF/A-1a compliant 生産（高） was 追加するd in 2.4.
Support for Unicode surrogates

OOo will be able to use Unicode characters outside the baseplane of 0x0000 to 0xffff if you have a font to （判決などを）下す those characters.
Multiscreen support for 贈呈

First 見解／翻訳／版利用できる in 2.1.
Refactoring the toolkit for better use in UNO 拡張s

What was going on for OpenOffice.org 2.0 ?

System 適合するing look and feel

VCL 供給するd a desktop and operating system 独立した・無所属 look to OpenOffice.org 1.x. However most 使用者 preferred OpenOffice.org to look and behave によれば their favorite desktop 主題. In 2.0 VCL will 選ぶ up that 主題, not by emulating it but 簡単に by using the desktops very own methods to draw a 支配（する）／統制する. 現在／一般に support for Windows XP and 最近の見解／翻訳／版s of Gnome 同様に as KDE with qt >= 3.2.2 is 器具／実施するd.
高めるd PDF support

OpenOffice.org 1.1 含む／封じ込めるd a basic PDF とじ込み／提出する輸出（する）おもに保存するing the 明白な content of a 文書. While this was already a big 取引，協定 for most 使用者, many 供給するd feedback about 存在 in need of more. In 2.0 more of the 文書 content that can be matched to the PDF とじ込み／提出する判型 will be 保存するd. This is for example 外部の and 内部の hyperlinks, （米）棚上げする／（英）提議する of contents, preview bitmaps for page preview, form 支配（する）／統制するs, and much more.
改良 of font 発見/matching

Not 明白な to the 使用者, VCL does a 抱擁する職業 in finding fonts and making them 利用できる to the higher level 使用／適用s. Over time the 実施 had to take more and more feature. For 2.0 it needed some 再編成 and 維持／整備 to stay 強健な and 成し遂げるing.

What was going on for OpenOffice.org 1.x ?

All 使用／適用 windows based on system windows

The 初めの実施 of OpenOffice.org used a 選び出す／独身 system window to 器具／実施する all 使用／適用 windows. 反して that 供給するd 罰金穀物d 支配（する）／統制する over the window 行為 it was 簡単に not possible to move a subwindow out of it's parents area. Good for developers, bad for 使用者s, however in the end the 使用者 won.
Asian language support

How to do proper support for Asian languages easily fills a 調書をとる／予約する. However the main 問題／発行するs solved in VCL where proper keyboard input and 延長するd text 生産（高） features like vertical 令状ing (from 権利 to left)
Glyph fallback

The typical 使用者 does not really care about what characters can be 代表するd by the glyphs from the 現在の font he uses. To still 許す him or her to see what's in the 文書, glyphs 行方不明の in the font are 代用品，人d if a richer font is 設立する.
PDF とじ込み／提出する輸出（する）

Creating PDF とじ込み／提出するs with OpenOffice.org 1.0 was a bit tricky on Unix, and really, really tricky on Windows. OpenOffice.org 1.1 was the first 見解／翻訳／版 to 含む／封じ込める the 可能性 to 簡単に "Save as ..." pdf. 使用者s loved it and asked for more.
Open source Unix printing system

It wasn't possible to open source the 初めの StarOffice 5.x printing system because Sun didn't own it. 反して Microsoft Windows already 供給するs 十分な API to 器具／実施する printing, on Unix there was nothing 利用できる at that time. In OpenOffice 1.0 psprint saw the light, an Asian language enable, PostScript based printing system.

Want more （警察などへの）密告，告訴（状） ? Want to help ?

There is a simple way to find out more about GSL and it's 役割 in OpenOffice.org. Just ask ! If you have questions then please 地位，任命する them in the dev@gsl mailing 名簿（に載せる）／表（にあげる）. Please have a look here for 接触する（警察などへの）密告，告訴（状）.

All trademarks 設立する herein are 所有物／資産／財産 of their 各々の owners.

Graphic System 層 事業／計画（する）