Apache OpenOffice Wiki - User contributions [en]

Ubuntu Build Instructions

2011-02-15T21:22:13Z

Gang65: /* Ubuntu 9.10 Karmic Koala and Ubuntu 10.04 Lucid Lynx */

{{Documentation/Building Guide TOC
|ShowNextPage=none
|ShowPrevPage=none
}}
{{Documentation/Note|Please add only Ubuntu-specifics here! Use the information on the [[Development/OpenOffice.org Building Guide/Building on Linux|Building Guide]] and only fall back to this document if you need help with Ubuntu-specifics (like package names).}}
== Ubuntu 9.10 Karmic Koala and Ubuntu 10.04 Lucid Lynx==

To build you need the following packages:
<pre>
sudo apt-get install g++ gcc bison flex libarchive-zip-perl libcups2-dev libpam0g-dev \
sun-java6-jdk gperf libfreetype6-dev libxaw7-dev libfontconfig1-dev libxrandr-dev patch \
libgconf2-dev libgnomevfs2-dev ant libgtk2.0-dev junit junit4</pre>

For the sun jdk you must activate the "ubuntu lucid partner" archive in the software sources.

To make sure that all packages are installed you could just simply run command:
<pre>
sudo apt-get build-dep openoffice.org
</pre>

Then you can build OOo with
<pre>
./configure --disable-mozilla --with-junit="/usr/share/java/junit4.jar"
</pre>

For other options regarding mozilla code please see [[Documentation/Building_Guide/Building_on_Linux#create_prebuilt_mozilla|here]].

In case you want to get some libraries from the system instead of building them yourself, the following packages are candidates to be installed also:

<pre>
sudo apt-get install python-dev ccache libgraphite-dev \
libwpd8-dev libxslt-dev libdb4.7-dev libneon27-dev libhunspell-dev libaltlinuxhyph-dev
</pre>

Then follow the '''[[Documentation/Building Guide|Building Guide]]''' to continue.

==See also==
*[[Building]]
*[[Debug Build Problems]]

[[Category: Distribution-Specific Build Instructions]]

Calc/Performance/The Ou case

2010-12-04T20:03:11Z

Gang65:

{{Performance}}
{{DISPLAYTITLE:The Ou Case}}

Loading a large plain data file takes very long.

References:
* [http://blogs.zdnet.com/Ou/?p=120 George Ou's blog entry]
* [http://www.lanarchitect.net/Examples/200264-l.sxc The test case file] (.sxc), convert to ODF .ods for profiling
* [http://www.lanarchitect.net/Examples/200264-l.zip Same data, but zip'ed Excel-XML]
Note that the numbers published in the article compare Excel .xls binary file format with Calc .ods, which is apples and oranges.

Findings:

* [http://svn.services.openoffice.org/opengrok/xref/Current%20(trunk)/sc/source/filter/xml/xmlsubti.cxx source/filter/xml/xmlsubti.cxx]
** 38% of time spent in ScMyTables::NewColumn() because of replicated use of aTableVec[nTableCount - 1] (vector::operator[]) <br> Note: percentage may be off due to compilation without optimization to obtain exact line numbers that may result in STLport's vector methods being differently compiled.
*** proposed fix: should obtain the pointer once instead.
** Similar for other places where aTableVec[xxx] is used.

* '''TODO:''' Check all ScMyTables::.*() and ScMyTableData::.*()
** Especially for 63342857 calls to AddColumn() and NewColumn() that result in 1168654944 calls to operator[] ...
** 63081776 calls to AddColumn() originate from ScXMLTableRowCellContext::EndElement()
** Those are highly suspicious and seem to indicate that too many temporary elements are created for empty columns/cells (needs verification).

[[Category:Calc|Performance/{{SUBPAGENAME}}]]
[[Category:Performance]]
[[Category:To-Do]]
[[Category:InProgress]]

Architecture/To-Dos

2010-09-17T23:17:38Z

Gang65: /* Replace code with 3rd party */

<noinclude>[[Category:Architecture]] [[Category:To-Do]]</noinclude>

This page intends to collect various architectural deficiencies (aka the pet peeves of various people) of OpenOffice.org, and lists the areas where's work in progress to improve on the architecture.

Depending on the specific count algorithm, OOo consists of approximately 7E6 lines of code (the overwhelming lot being c++, all other being an order of magnitude less (Java, Perl, Basic, Python)). This sheer size in and of itself is a problem - the code base is notorious for crashing or slowing down to a crawl various software engineering tools, from debugger to dependency analysis to reverse design extraction.

The code itself varies greatly in quality, style, and age (the latter invariably leading to the former, if you recall the history and evolvement of c++), with parts being there virtually unmodified for 10+ years, and others just recently written from scratch.

Taken together, this leads to a lot of complexity and [http://artax.karlin.mff.cuni.cz/~kendy/ooo/cut-n-paste/src680-m154.txt.gz redundancy], which is very hard to remove.

Facing this amount of code, the big rules must be:
*simplify
**remove internal redundancy
**remove external redundancy (use external projects, whereever possible)
**remove unused or dead code
**remove legacy functionality, which does no longer provide noticeable value (e.g. [[Framework/Modules/binfilter|binfilter]])

*refactor for orthogonality
**make subsystems implement independent functionality
**enable combinations of those subsystems to be freely combinable
**carry that to the UI level (no artificial restrictions on what one can do with UI objects - e.g. shapes can be rotated, and clearly text frames should, too)

==Architectural To-Dos==
<DPL>category=To-Do
category=Architecture</DPL>

==Infrastructure Improvements==

*[[BuildSpeedup | Speeding up the build system]], and maybe even make it consider global dependencies (currently, OOo has the notion of modules, which approximately map to toplevel directories in the build tree. Automatic build-time dependency calculation is currently only available on the intra-module level).

*Making the actual design more accessible, improving upon existing solutions like [http://ooo.ximian.com/lxr/ LXR] or [http://ooo.ximian.com/bonsai/ Bonsai]. Ultimately, this should result in refactorings of the source code being both much easier and much safer than today, by providing information where and how specific functionality is used. A prerequisite for that would be a parser that ''really'' knows about c++ - [http://www.gccxml.org/ gccxml] might be a starting point.

==Runtime System Improvements==

This is about making the implementation languages safer, and easier to use. What follows could also be subsumed under "transparency on the implementation level". When something can be used transparently, or appears transparent to a user, it is an implementation aspect she need not care about. Being able to program in an environment which is transparent with regard to lots of aspects, empowers the developer to focus on the problem at hand, not having to litter her code with mundane tasks such as memory management or locking.

*Make threading transparent. Currently, fulfilling the contract of a UNO component regarding thread-safeness is
#tedious work, because normally each involved object has to acquire and release a mutex on method entry and exit, respectively
#almost impossible to get right, let alone verified to work correctly (no races, no deadlocks), because of the sheer mass of involved objects and mutices (the number of distinct states that would have to be checked for a proper verification is intractable for anything but the most trivial examples). The upcoming [[Uno/Effort/Binary/Extend Threading-Model|extended Binary Uno threading-model]] makes thread-safeness transparent, by automatically locking and unlocking when entering or exiting components on a much coarser level than single methods.

*Make other mundane stuff transparent. Like memory management (via garbage collection, or refcounting via [http://www.boost.org/libs/smart_ptr/index.html smart ptrs], [http://api.openoffice.org/docs/DevelopersGuide/ProfUNO/ProfUNO.htm#1+4+2+7+3+Mapping+of+Interface UNO reference]), or [http://en.wikipedia.org/wiki/Transaction_processing transactionality] (the mode of making changes take place either completely, or not at all. Having a component behave in a non-transactional way in the face of an error makes recovery rather hard. There's more to transactionality than exception-safeness. Imagine two users collaborating on the same document).

==General Refactoring Improvements==
For many reasons the OpenOffice.org codebase is difficult to understand and navigate. On of the reasons is a lack of cleanup in the code. There is a never ending list of things that ought to be done-- add some of your own.

*Actually remove deprecated things. Things like String and [http://go-oo.org/lxr/ident?i=UniString UniString] need to go. svtools and tools have loads of stuff that is duplicated elsewhere or is deprecated. Getting rid of these sorts of things will make maintaining application code much easier.

*Document things. Some of the code has comments that at one time were correct. Some code has German comments. While most of the OpenOffice.org programmers sind Deutschschprachig, there is an unofficial understanding that German comments mean "don't touch."

==Code Improvements==
===Remove unused code===
Binary Loading/Saving stuff in ItemSets, depend on EditEngine Loading/Saving (only used for Clipboard) - MT

===Remove duplicate code===
Consolidate slightly copied and modified code.
* BigPointerArray vs. SvPointerArray
* RTL Strings with Tools Strings

Consolidate Text Engines
* Text Engine
* Writer Engine
* Edit Engine

===Replace code with 3rd party===
Replace self made containers with STL containers.
* Tools Container,
* SvPointerArray ([http://www.openoffice.org/issues/show_bug.cgi?id=112395 Issue 112395]),
* BigPointerArray,
* "GetPos" is mostly used wrong -> remove it (algorithmic complexity to hight O(n*n)) - [http://svn.services.openoffice.org/opengrok/search?q=GetPos&project=/DEV300_m87 list of the GetPos usage]

===Improve modularity===
?Clear "Mission Statements" for modules?

===[[VCL]]===
get rid of internal event queue.

==Framework Improvements==

The framework module already has a very modular architecture solely based on UNO components. Amongst others, it manages menus and toolbars, but it does not manage docked windows like e.g. navigator or impress task pane. These windows are still managed in sfx2 and their implementations are based on sfx2 classes. No non-sfx2 based module can use them.

Here's the roadmap:

* add a LayoutManager for DockingWindows to the framework module that works in the same way as the LayoutManager for toolbars
* implement docking handlers for the windows managed by this LayoutManager in the same way as for the toolbars
* provide factories for the sfx2 based implementations of Docking Windows
* simplify the frame classes in sfx2; without the sfx internal layout manager for DockingWindows only one "frame" class is necessary
* put the current container windows inside of task windows managed by a Task service (later they might become tabs in a tab bar)
* move the LayoutManager from the frame to the task (or add some "super manager") so that frames can share their tools

Amongst others this will allow to have more than one view to one ("split view") or several documents in one system task window.

===Status Quo===

The new LayoutManager and the docking handlers are already worked on and nearly finished. Next step will be the mentioned factories. There also is a prototype for a task window and a task service that can be adjusted to our needs. The biggest challenge currently is the "super manager".

==Application-specific Improvements==
One of the lingering problems on the application level is the fact that, in spite of modularized lower-level functionality, application functionality cannot be shared ''between'' OOo's applications (except via embedding of a whole application (OLE)). This is because for neither Calc nor Writer, there are reusable application engines, like a text engine providing text editing and layouting functionality, or a table engine providing formula and calculation support. Draw/Impress already uses a shared engine, dubbed 'Drawing Layer'. But there's still considerable functionality hidden in the application code, which is worth extracting. Especially the missing Writer engine manifests itself in duplicated text editing functionality in EditEngine and TextEngine (used by Impress and Calc for their corresponding text functionality).

<div name="Example" class="boilerplate metadata" id="example" style="background-color: #fee; margin: 0 1em; padding: 0 10px; border: 1px solid #aaa;">
'''Example 1'''

The Writer uses a different implementation when displaying pictures, opposed to Draw/Impress. Thus, if you insert a picture into a writer document, you have a different feature set available as in Draw/Impress or Calc. For example, the Writer graphic object is able to render a variety of border styles, but at the same time, is unable to rotate the picture. To have rotated pictures in Writer, one has to insert that picture in a Draw document, copy the resulting drawing layer object, and paste that into Writer.
</div>

<p>

<div name="Example" class="boilerplate metadata" id="example" style="background-color: #fee; margin: 0 1em; padding: 0 10px; border: 1px solid #aaa;">
'''Example 2'''

The Draw/Impress applications use a different implementation for displaying text, as opposed to the Writer. Thus, if you insert a text shape in Impress, you can't have two-column layout with it, nor does it provide change tracking ('redlining'). On the other hand, the Writer's fly frames, which superficially perform the same task as the Impress text shape, cannot be rotated.
</div>

Another area of improvement is rendering. Currently, all application's graphical output is based on the OutputDevice class, which provides only very basic rendering facilities (in fact, besides largely extended text output functionality (to handle OOo's i18n requirements), this interface has basically remained unchanged for a long time). Specifically, things like performant alpha compositing or anti-aliased geometry rendering are extremely hard to achieve with the current design. Therefore, starting with OOo 2.0, the [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas] interface is slated to gradually replace OutputDevice in all applications.

===Writer===

*break up the monolith
*make the import filters more modular
*port rendering to XCanvas

===Calc===
See [[Calc/To-Dos]]

===Draw/Impress===

*break up the monolith
*become more decoupled from sfx2
*redesign API ([[Impress_Performance | performance]])

*port Drawing Layer to XCanvas (see [[DrawingPrimitives]] for one of the preconditions)

*Allow slides to inherit animations from the master slide

DomainDeveloper

2010-09-17T22:43:33Z

Gang65: /* Developers */

A mapping of names to OOo accounts.

Abbrev.:

* PL : Project Lead
* CL : Project Co-Lead
* CC : Community Council Member
* ESC : Engineering Steering Committee Member
* CVS : has write access to the OOo CVS repository

----

=== Developers ===

{| class="prettytable sortable"
|-
! Name || CVS || @openoffice.org || [[IRC Communication]] || Notes || Affiliation
|-
| [[User:Agerskov|Claus Agerskov]]|| || cs||Agerskov, cagerskov||PL Project Management Tool ([http://oopm.openoffice.org oopm])||AgerCon
|-
| Volker Ahrendt|| X || va||||||Sun Microsystems
|-
| Kai Ahrens|| X || ka || Kai_Ahrens ||PL Graphic Applications||Sun Microsystems
|-
| Rail Aliev || X || rail || rail || Ru and Tr NL Co-lead || Infra-Resource
|-
| Gene Anaya|| || ganaya||||||
|-
| [[User:JoostAndrae|Joost Andrae]]|| X || ja||ja_||CL qa, release testing en-US builds and releasing/uploading builds and releases||Sun Microsystems
|-
| [[User:ericb|Eric Bachard]] || X || ericb||ericb2|| PL Education, Mac OSX/Linux PPC port and vcl/impress hacker || [http://education.openoffice.org Education project], unaffiliated
|-
| Kai Backman|| || kaib ||KaiB||||
|-
| Sascha Ballach|| X || sab||||||
|-
| Jayant Balraj Madavi|| || jayant_madavi||aZEN_JM||Connectivity / Database||Novell, Inc.
|-
| Jörg Barfurth|| X || jb||JoergB||Configuration Util||Sun Microsystems
|-
| Omer Bar-or|| X || cremlae||cremlae||Mac porting||Google Summer of Code
|-
| Mathias Bauer|| X || mba||||PL Writer, CL Framework, XML||Sun Microsystems
|-
| Thorsten Behrens|| X || thb||thorsten||vcl/impress/toolkit visionary||Novell, Inc.
|-
| Thomas Benisch|| X || tbe||||Scripting framework||Sun Microsystems
|-
| Stephan Bergmann|| X || sb||||CL UDK||Sun Microsystems
|-
| Andreas Bille|| X || abi||||||
|-
| Éric Bischoff|| X || ebischoff||ebischoff||KDE A/B driver||Bureau Cornavin
|-
| Nick Blievers|| X || nick||||IRIX||
|-
| Daniel Boelzle|| X || dbo||||UNO core/bridges/packages||Sun Microsystems
|-
| Oliver Bolte|| X || obo||||RE||Sun Microsystems
|-
| Henning Brinkmann|| X || hbrinkm|| hbrinkm|| WW8 Filter, DOCX Filter ||Oracle
|-
| [[User:Cedricbosdo|Cédric Bosdonnat]]|| X || cedricbosdo || cbosdonnat || Writer Filters, ooeclipse integration || Novell, Inc.
|-
| Rafaella Braconi|| || coni||Rafaella ||PL l10n, Globalization Program Manager||Sun Microsystems
|-
| Michael Brauer|| X || mib||||PL XML||Sun Microsystems
|-
| Oliver Braun|| X || obr||obr||System Integration/Accessibility Hacker||Sun Microsystems
|-
| Andreas Bregas|| X || ab||||StarBasic||Sun Microsystems
|-
| Jörg Brunsmann|| || jbrunsmann||||UDK||
|-
| Jörg Budischewski|| || jbu||PyUNO hacker||||
|-
| Peter Burow|| X || pb||plumbumm||UI||Oracle
|-
| Aidan Butler|| || aidan||||XML filters||
|-
| [[User:ScottCarr|Scott Carr]] || X || kcarr||kcarr||Documentation||Progbits
|-
| Giuseppe Castagno || X || beppec56 || beppec56_ or beppe_c || PDF output||
|-
| Colin Charles|| || drbyte||bytee||Malaysian native-lang project||bytebot.net
|-
|Jian Hong Cheng || X || chengjh || || Writer || IBM Corp.
|-
| Xiuzhi Cheng|| X || xzcheng || xiuzhi|| ESC,Xml,ODF|| OOo community
|-
| [[User:jza|Alexandro Colorado]]|| X || jza || jza|| CL [[OOoES|ES]] ||
|-
| Behrend Cornelius|| X || bc||||Wizards||Sun Microsystems
|-
| [[User:ccornell|Clayton Cornell]] || X || ccornell || ccornell || Documentation Project co-lead ||Oracle
|-
| Michael Cziebalski|| || mci||||||
|-
| [[User:pdefilippis|Pierre de Filippis]]|| X || pdefilippis||aliscafo||Mac OSX native porting||
|-
| Yuri Dario || || ydario || Paperino || OS/2 Port || Serenity Systems intl
|-
| Andrew Dent|| X ||ace_dent||ace_dent||ui/custom_images||
|-
| Naren Devaiah|| || ||ndev||Performance||Intel Corporation
|-
| Nitin Dongre|| || ||nitin_BITS||||Novell, Inc.(intern)
|-
| Radek Doulik|| || radekdoulik||rodo_||Canvas hacker||Novell, Inc.
|-
| Carsten Driesner|| X || cd|| cd_oo ||PL Framework||Oracle
|-
| Herbert Duerr|| X || hdu||hdu_hh||GSL||Sun Microsystems
|-
| [[User:bei|Bernd Eilers]]|| X || bei||rfc821||[[EIS]]||Oracle
|-
| René Engelhard|| X || rene||_rene_||config_office, Debian packager||Debian
|-
| [[User:Pereriksson|Per Eriksson]] || || pereriksson || || CL, MarCon Sweden ||
|-
|[[User:Jbfaure|Jean-Baptiste Faure]]||X||jbfaure||jbfaure ||PL FR native-lang project||
|-
| Hubert Figuière|| X || hub || hub || PPTX || Novell, Inc.
|-
| Claudio F Filho|| || filhocf||filhocf||Brazilian portuguese Localization||BrOffice.org
|-
| Andre Fischer|| X || af||||Impress||Sun Microsystems
|-
| Uwe Fischer || X || ufi || ufiooo || Application Help, Documentation || Oracle
|-
| Ken Foskey|| || waratah||waratah||config_office/dmake man||slug.org.au
|-
| Duncan Foster|| || dfoster||||||
|-
| David Fraser|| || davidfraser||davidfraser||South African translations, multilingual builds||translate.org.za
|-
| [[User:Nf|Nils Fuhrmann]]|| || nf||SunNF||||Sun Microsystems
|-
| Martin Gallwey|| X || mtg||marty_||XML/Writer/packaging||
|-
| Pierre-Andre Galmes || || pagalmes || pagalmes || Chart2 ||StarXpert
|-
| Tony Galmiche|| X || tonygalmiche||||FR native-lang project||
|-
| Sunil Gandhi|| || ||tyro||||NOSIP
|-
|Zemin Gao || || gaozemin|| gaozm || Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sophie Gautier|| X || sgauti|| sophi || ||.
|-
| Vladimir Glazounov|| X || vg||||RE||Sun Microsystems
|-
| Laurent Godard || X || laurentgodard || lgodard || CC, PL Extensions, Fr Native-lang Project || inDesko/Nuxeo
|-
| Jody Goldberg|| X || jodygoldberg||jody||[[Calc]] spreadsheet-ness||
|-
| Dirk Grobler|| X || dg|||| ||Sun Microsystems
|-
| [[User:Sg|Steffen Grund]]|| X || sg|| || NetBeans Integration ||Sun Microsystems
|-
| Bettina Haberer|| || bh||||RFEOwner||Sun Microsystems
|-
| Bo Han || X || hanbo || hanbo || VBA Interop || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Ingrid Halama|| X || iha||||Chart||Sun Microsystems
|-
| Chris Halls|| X || haggai||haggai||Debian packager&misc. hacker||Credativ Ltd., Debian
|-
| Gregor Hartmann|| X || gh|| Lachs ||Testtool, gsicheck, buildbot||Sun Microsystems
|-
| Bustamam Harun|| || bustamam||||Malaysian stuff||
|-
| Kevin Hendricks|| X || khendricks||||PL Lingucomponent, PowerPC||
|-
| Con Hennessy|| || cphennessy||cph2 or cph_||hacker & former council person||OpenApp
|-
| Ivo Hinkelmann|| X || ihi||ivo||l10n tooling/general/RE||Sun Microsystems
|-
| Eric Hoch|| X || maveric||mav_eric||Mac Porting||
|-
| [[User:Lutz_Hoeger|Lutz Hoeger]]|| X || lh ||lutzh||||Sun Microsystems
|-
| Michael Hönnig|| X || mi||||PL API||
|-
| Ilko Höpping|| X || ih||||||Sun Microsystems
|-
| Jan Holešovský|| X || kendy||kendy||KDE integration||Novell, Inc.
|-
| Martin Hollmichel|| X || mh||Ratte/Nesshof||PL External, Tools, Porting, CC||Sun Microsystems
|-
| Karl Hong|| X || khong||||i18n, CJK expert||
|-
| [[User:icobgr|Hristo Hristov]] || || icobgr || icobgr || PL Bulgarian native-lang project ||
|-
| Matthias Huetsch|| X || mhu||||Performance/strategy, PL UCB, CC, ESC||Sun Microsystems
|-
| Sven Jacobi|| X || sj||||Escherwizard||Sun Microsystems
|-
| Jörg Jahnke|| || jj||||tooling||Sun Microsystems
|-
| Pavel Janík|| X || pjanik||paveljanik||PL Czech native-lang project, CL l10n, CC, ESC, l10n builds||
|-
| Sunil Amitkumar Janki || || sjanki || sjanki || GNU Linux mipsel porter ||
|-
| Christian Jansen|| || cj ||||Menu and Toolbar?||Sun Microsystems
|-
| Ocke Janssen|| X || oj||Base||||Sun Microsystems
|-
| Berry Jia|| X || berryjia||||||
|-
| Mingfei Jia || X || jiamingfei || || Lotus Smart Suite filter,MS Word encryption || IBM Corp.
|-
| Chuang Jiang || || jiangc || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Pascal Junck|| || pjunck||||||
|-
| [[User:pj@openoffice.org|Peter Junge]]|| X || pj|| peter13j|| OOo community contact ||
|-
| Christian Junker|| || Cyb||christianju||API||Trees For Life
|-
| Etsushi Kato || X || ekato || || Mac OS X Port || Independent
|-
| Hirano Kazunari|| || khirano||||Japanese||
|-
| Mihaela Kedikova|| X || misheto||||grid control||Sun Microsystems
|-
| Dhananjay Keskar|| X || dkeskar ||dkeskar||Performance,Buildbot,cat-herder||Intel Corporation
|-
| Volodymyr Khrystynych|| || volody||||XML Filter||
|-
| Robert Kinsella|| || rkinsella||||||Sun Microsystems
|-
| Matthias Klose|| || doko||doko||Ubuntu, gcc, python packager||Canonical, Inc.
|-
| Bartosz Kosiorek|||| gang65|||| Bug Tracker||
|-
| Laszlo Kovacs|| || lkovacs||||Documentation||
|-
| Tobias Krause|| X || tkr||||ucb||Sun Microsystems
|-
| Martin Kretzschmar|| X || mkretzschmar||martink||Gnome / Debian||Student
|-
| Will Lachance|| || wlach||wlach_||Word Perfect File Filters||Net Integration Technologies, Inc.
|-
| Marcus Lange|| X || mla||mla||[http://download.openoffice.org download websites], uploading/releasing Developer Snapshots, Beta versions, RCs and releases||Oracle
|-
| Thomas Lange|| X || tl||tl13||||Oracle
|-
| Lars Langhans|| X || lla||||||Sun Microsystems
|-
| Hans-Joachim Lankenau|| X || hjs||ause||dmake makefile expert, RE||Sun Microsystems
|-
| Németh László|| X || nemeth||||PL lingucomponent||
|-
| Jakob Lechner|| X || jakob_lechner||||Writer||Fabalabs
|-
| Michael Leibowitz|| X || mikeleib ||mikeleib||performance||Intel Corporation
|-
| Hui Li|| || lihuiibm || Hui_Li ||VBA Interop||IBM Corp.
|-
|Jian Li|| || lijian || lijian|| Writer|| CS2C
|-
| Wind Li|| X || windly||||Address books||
|-
| Xing Li || X || lixxing || || Accessibility || IBM Corp.
|-
|Weike Liang || X || liangweike || liangweike || Graphics ||
|-
| Ping Liao|| || pliao||||||
|-
| Tor Lillqvist|| X || tml||tml_||||Novell, Inc.
|-
| Fong Lin || X || pflin || Fong || VBA Interop, Scripting, CJK Enhancement || Novell, Inc.
|-
| Joachim Lingner|| X || jl||||Java, CLI||Sun Microsystems
|-
| Christian Lippka|| X || cl || cl ||Graphic Applications||Sun Microsystems
|-
| Chen Liu|| || liuchenn|| liuchen ||VBA Interop||IBM Corp.
|-
|Jianli Liu || || liujl|| liujianli || Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Mindy Liu|| || mindyliu||||||
|-
|[[User:liutao |Tao Liu]] || X || liutao || liutao ||PL modularization ,PyUNO, Async dialogs,||
|-
| YiSong Liu|| || Liu YiSong || Liu YiSong|| PYUNO || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yu Liu || X || ch2000liuy || LiuYU || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yuhua Liu || || liuyuhua|| yuhua|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| [[User:fl|Frank Loehmann]]|| X || fl ||frankl||PL [http://ux.openoffice.org User Experience]||Sun Microsystems
|-
| [[User:Dl|Dieter Loeschky]]|| X || dl ||||PL: ODF Toolkit||Sun Microsystems
|-
| Philipp Lohmann|| X || pl||PhilippL||VCL/X11 (GSL) hacker||Sun Microsystems
|-
| Michel Loiseleur|| || mloiseleur|| coren`|| Bugfixes ||Linagora
|-
| Jackson Low|| X || xxjack12xx||||Porting||
|-
| Patrick Luby|| || pluby||||Mac||
|-
|Jingrong Luo || || Luo Jingrong|| Luo Jingrong|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yue Lv || || lvyue || lvyue || Calc ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|[[User:majun|Jun Ma]]|| ||majun51 || || writer || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Katarina Machalkova|| X || bubli|| bubli|| OOXML Export ||Novell, Inc.
|-
| Prasad Madhav || X || pmadhav || pmadhav || Buildbot || Intern@Intel
|-
| Babak Mahbod|| || bmahbod||||||
|-
| Martin Maher|| || mmaher||||Writer & Filter chap||
|-
| Nakata Maho|| X || maho||_maho_||PL QA, PL JA, FreeBSD guy||Independent
|-
|Yonggang Mao || X || maoyonggang|| maoyg|| Calc || CS2C
|-
| John Marmion|| X || jmarmion||||||
|-
| Andreas Martens|| X || ama||||PL Writer||Sun Microsystems
|-
| Shane M Mathews|| X || smmathews|| smmathews ||[[Impress:_OpenGL_rendered_transitions]]||student
|-
| Frank Mau|| X || fma||||tooling||Sun Microsystems
|-
| [[User:smsm1|Shaun McDonald]] || X || smsm1 || shaunmcdonald || Mac Port, buildbot MacPort1 || Graduate
|-
| Caolán McNamara|| X || cmc||caolan||CL Writer & Filter man|| [http://www.redhat.com Red Hat Inc.]
|-
| Michael Meeks|| X || mmeeks||michael_||ugly hack-er, ESC||Novell, Inc.
|-
| Frank Meies|| X || fme||||Writer||Sun Microsystems
|-
| Federico Mena-Quintero|| || federicomena||federico||perfectionist||Novell, Inc.
|-
| Ismael Merzaq|| X || isma87||ismael_||Mac OSX native porting||Student
|-
| Michael Mi|| || mmi||||||
|-
| Björn Michaelsen|| X || b_michaelsen ||b_michaelsen|| Writer, Bookmarks, Performance, User Feedback Program, New Build System||Oracle
|-
| Björn Milcke|| X || bm||bm_||Chart||Sun Microsystems
|-
| Petr Mladek|| || pmladek||pmladek||SUSE RPMs, ooo-build releases||Novell, Inc.
|-
| Cyrille Moureaux|| X || cyrillem||Cyrille||||
|-
| [[User:Mmp|Matthias Müller-Prove]]|| X || mmp|| mprove|| [[User Experience]] || Sun Microsystems
|-
| [[User:Bluedwarf|Takashi Nakamoto]]|| || bluedwarf|| || Japanese || Student
|-
| Jan Navrátil || X || jnavrati || jnavrati || || [http://www.redhat.com Red Hat Inc.]
|-
| Niklas Nebel|| X || nn||niklasn||PL [[Calc]]||Sun Microsystems
|-
| Christoph Neumann|| X || cn||||[[UnoApiTest]]||Sun Microsystems
|-
| Frank Neumann|| X || fne||||MacPort||
|-
| NicelKM|| X || mnicel||nicel||||Novell, Inc.
|-
| Jan Nieuwenhuizen|| X || jcn||janneke||Layout code, hacker ||Novell, Inc.
|-
| [[User:ChristophNoack|Christoph Noack]]|| X || christophnoack ||christoph_n||CL [http://ux.openoffice.org User Experience]||
|-
| Bertram Nolte|| || bnolte||||||
|-
| Tomas O'Connor|| || toconnor||||Scripting Framework||
|-
| Maximilian Odendahl|| X || mod||mod||[[Notes2]] [[SQL_Syntax_Highlighting]]|| Student / SEPT-Solutions
|-
| Takashi Ono || X || tono || || MinGW port || Independent
|-
| Lars Oppermann|| X || lo||||||
|-
| Rakesh Pandit || X || rakeshpandit|| chacha_chaudhry|| Education Project - Starmath/fix module warnings|| Education Project
|-
| Rodrigo Parra Novo|| X || rodarvus||rodarvus||Gnumeric/Abiword OpenDocument Format support and port to Maemo||INdT (Instituto Nokia de Tecnologia)
|-
| Pierre Pasteau|| X || pastea_p || pierrep|| Education Project, SeaMonkey migration || Education Project
|-
| Edward Peterlin|| X || OPENSTEP||||Mac||
|-
| [[User:Fpe|Frank Peters]]|| X || fpe||||CL Documentation||Sun Microsystems
|-
| Christof Pintaske|| X || cp||||||Sun Microsystems
|-
| Ron Piterman|| || rpiterman||||||
|-
| Sebastien Plisson|| X || plipli||plipli||Developer on Aqua port||OO Aqua Port
|-
| Noel Power|| || npower||noelp||VBA Interop, Scripting||Novell, Inc.
|-
| Nikolai Pretzell|| X || np || ||Autodoc, code quality||Sun Microsystems
|-
| Jonathan Pryor|| || jpryor || jonp || || Novell, Inc.
|-
| Canghua Qu|| || quch || Canghua || AutoTest, Graphics || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Volker Quetschke|| X || vq||vq||W32-tcsh/bash build environment and dmake Hacker, ESC||Gravity Waves
|-
| Tino Rachui|| X || tra||tinor||GSL/Unix Hacker||Sun Microsystems
|-
| Goran Rakić || X ||goranrakic || || Serbian Native-Lang PL ||
|-
| [[User:Kr|Kay Ramme]]|| X || kr||||PL UDK||Sun Microsystems
|-
| [[User:ErAck|Eike Rathke]]|| X || er||erAck||CL [[Calc]], engine; CL i18n; stricken with number formatter||Sun Microsystems
|-
| Michael Rauch|| X || mrauch||||NetBSD||
|-
| Jens-Heiner Rechtien|| X || hr||blauwal||RE; OOo SCM (CVS, CWS tooling); Porting; Compilers||Sun Microsystems
|-
| Daniel Rentz|| X || dr|| drr ||[[Calc]] Excel filter, UI||Sun Microsystems
|-
| Florian Reuter|| X || flr||||Writer filters||Novell, Inc.
|-
| Georg Richter|| X || grichter||georg||Base, native MySQL driver||MySQL AB
|-
| Hennes Rohling|| X || hro||||GSL & Util||Sun Microsystems
|-
| Bibek Sahu|| || Bibek||bibek||Impress pieces||Trees For Life
|-
| Andreas Schlüns|| X || as||||Framework||Oracle
|-
| Ingo Schmidt|| X || is||||(Native) Installation||Sun Microsystems
|-
| [[User:Jsc|Jürgen Schmidt]]|| X || jsc||jsc||PL API, PL Extensions, UNO, SDK||Sun Microsystems
|-
| [[User:Schmidtm|Matthias Schmidt]] || || schmidtm || schmidtm || Mac OSX Aqua Port || Sun Microsystems
|-
| Stephan Schäfer|| X || ssa||ssa||VCL||Sun Microsystems
|-
| Frank Schönheit|| X || fs||FrankS||Database Access, Forms||Sun Microsystems
|-
| [[User:Sus|Svante Schubert]]|| X || sus||Svante||XML & ODFTOOLKIT co-lead, ODFDOM project chair, Member of OASIS ODF TC, OASIS OIC TC, OASIS ODF SC Metadata||Sun Microsystems
|-
| [[User:Sts|Stella Schulze]]|| X || sts||||[http://ui.openoffice.org/nonav/VisualDesign/ Visual Design]||Sun Microsystems
|-
| Julian Seward || || sewardj || || valgrind ||
|-
| Darragh Sherwin|| || dsherwin||darragh||E-Legislation / E-GovSystems||Propylon
|-
| Wei Guo Shi || X || shiwg || || Accessibility and Smart Suite filter || IBM Corp.
|-
|[[User:Robertzhou | RobertZhou]]|| X || robertzhou|| shizhoubo|| [[Framework]] || CS2C
|-
| Raul Siddhartha|| || rsiddhartha||raul||GTK File Selector||Novell, Inc.
|-
| Sarah Smith|| || ssmith||||||
|-
| [[User:mox|Mox Soini]] || X || mox || Moxed || Mac Porting ||
|-
| Rajesh Sola|| || rajeshsola||sola||misc.||NOSIP
|-
| Kai Sommerfeld|| X || kso||||manager & hacker||Sun Microsystems
|-
| Oliver Specht|| X || os||||PL UI||Oracle
|-
| Jörg Spindler|| || jspindler||||||
|-
| Michael Stahl|| X || mst||||Writer, RDF, Metadata||Oracle
|-
| [[User:Rescue|Joey Stanford]] || || Rescue/k0fcc || Rinchen || CL [http://eo.openoffice.org/ Esperanto native-lang project] || [http://canonical.com Canonical]
|-
| Fridrich Štrba|| X || fridrich_strba||Fridrich||Word Perfect Hacker||Novell, Inc.
|-
| Keith Stribley|| X || kstribley||||Graphite fonts, Myanmar l10n||
|-
| [[User:Muthusuba|Muthu Subramanian]]|| X || muthusuba||muthusuba||misc.||
|-
| Louis Suárez-Potts|| || louis||louis||Community Manager||Collab.net
|-
|Quanfa Tang || || tqfa|| tangquanfa|| Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| David Tardon || X || dtardon || dtardon || || [http://www.redhat.com Red Hat Inc.]
|-
| Stefan Taxhet|| X || st||stx12||CC, interpersonal problem fixer||Sun Microsystems
|-
| Armin Theissen|| || armin||||||
|-
| Caio Tiago Oliveira|| X || asrail||asrail||CL QA, release testing pt-BR builds||BrOffice.org
|-
| Jan Tietjens|| || tietjens||||||
|-
| Rüdiger Timm|| X || rt|| rtimm ||RE||Sun Microsystems
|-
| [[User:mt|Malte Timmermann]]|| X || mt|| Malte || Accessibility, Security, Performance||Sun Microsystems
|-
| Gerhard Tonn|| || tonn||||s390||
|-
| Willem van Dorp|| || willem.vandorp||||||
|-
| Tom Verbeek|| X || tv|||| ||
|-
| Sander Vesik|| || svesik||||||
|-
| Daniel Vogelheim|| X || dvo||||XML||
|-
| Mikhail Voitenko|| X || mav||mav||Framework||Sun Microsystems
|-
| Robert Vojta|| X || rvojta||rvojta||Mac OS X related issue||
|-
| Dirk Völzke|| X || dv||||Installation||Sun Microsystems
|-
|Xu Ming Wang || X || flyccloud or Wangxum || || Calc || IBM Corp.
|-
| [[User:Sparcmoz|Jim Watson]]|| X || sparcmoz|| sparcmoz||GNU Linux sparc porter||clug.org.au
|-
| [[User:Weiz |Zhao Wei ]] || || weiz || weiz || Chart2 || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Armin Weiss|| X || aw||||||Sun Microsystems
|-
| Gerd Weiss|| X || gm||||RE||Sun Microsystems
|-
| Dan Williams|| X || fa||dcbw||Mac et. al. hacker|| [http://www.redhat.com Red Hat Inc.]
|-
| Oliver Wittmann|| X || od||Writer||||Oracle
|-
|[[User:wuy|Yan Wu]] || X || wuy || ||Framework ||CS2C
|-
| Stephan Wunderlich|| X || sw||||||
|-
| Antonio Xu|| X || antoxu || antoxu || Async dialogs, PRC improvements || Intel Corporation
|-
|Dehua Xu || || xudehua || xudh ||||
|-
| [[User:Steve_yin|Steve Yin]] || X || steve_yin || steve_yin || Microsoft Office file format, PDF, Accessibility, ODF || [http://symphony.lotus.com IBM Corp.]
|-
| Kohei Yoshida|| X || kohei||kohei_||[[Calc]] hacker, Calc optimization solver developer||Novell, Inc.
|-
| Guoqiang Yu|| X || yugq || yugq|| Performance || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Xiaoyang Yu|| || || ||Disk block reordering||Intel Corporation
|-
| George Zahopoulos|| X || georgez||||||
|-
| Kurt Zenker|| X || kz||smoketester||RE||Sun Microsystems
|-
|[[User:Zhangxiaofei|Xiaofei Zhang]]|| X || Zhangxiaofei || zhangxiaofei/FelixZ || [[Framework]] ||CS2C
|-
|Jianwei Zhao || || zhaojianwei || zhaojianwei || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Jeremy Zheng|| X || zhiming || Jeremy || Async dialogs, PRC improvements || Intel Corporation
|-
| Zengliangjun || X || Zengliangjun || liangjun || [[Performance]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Kuang Liang || X || Kuang Liang || kuangliang || [[Performance]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| [[User:liheng|Heng Li]] || X || liheng || liheng || [[Performance]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-}

=== QA Engineers ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Name ||CVS||@openoffice.org || [[IRC Communication]] || Interested modules || Notes || Affiliation
|-
| Stefan Baltzer||||sba||||writer||||Sun Microsystems
|-
| Thorsten Bosbach||X||tbo||||framework, testautomation||framework test automation||Sun Microsystems
|-
| Oliver Craemer||X||oc||||[[Calc]], testautomation||calc test automation||Sun Microsystems
|-
| Helge Delfs||X||hde||||testautomation, writer||Test automation||Sun Microsystems
|-
| Fredrik Haegg||X||fha||||||||
|-
| Hasan Ilter||||hi||||writer, printing, pdf export||||Sun Microsystems
|-
| Michael Rüß||||mru||||writer, word im/export||||Sun Microsystems
|-
| Éric Savary||||es||||writer, accessibility||||Sun Microsystems
|-
| [[User:jsi|Joerg Sievers]]||X||jsi||jogi||porting||Mac- and Solaris SPARC port testing||
|-
| Joerg Skottke||X||jsk||skotti||framework, qa/qatesttool||Framework test automation||Sun Microsystems
|-
| Marc Neumann||X||msc||||database, testautomation||Database access test automation||Sun Microsystems
|-
| Chris Lukasiak||||clu||||database||||Sun Microsystems
|-
| Frank Stecher||||fst||||[[Calc]]||||Sun Microsystems
|-
| Jack Warchold|||| jw||||writer, import/export filters||||
|-
| Uwe Luebbers||||ul||||framework||||Sun Microsystems
|-
| Thorsten Martens||||tm||||framework||||Sun Microsystems
|-
| Olaf Felka|||| of||of_sun||framework, installation||||Sun Microsystems
|-
| Thomas Klarhoefer||||kla||||chart||||Sun Microsystems
|-
| Wolfram Garten||X|| wg||||draw, impress||draw, impress test automation||Sun Microsystems
|-
| Christian Guenther||||cgu||||draw, impress||||Sun Microsystems
|-
| Ulf Stroehler|||| us||||||||Sun Microsystems
|-
| [[User:Thorsten_Ziehm|Thorsten Ziehm]]||||| thorstenziehm||||||QA lead||Sun Microsystems
|}

We are tracking pending JCAs in the document [[Pending JCAs]].

== Related Pages ==
* [[Commit Rights]]
* [[Contributing Patches]]
* [[User_Experience/Community|User Experience Team]]
* A map of OOo developers around the world is available at http://www.frappr.com/ooodev, please add yourself to the map if you're involved in OOo development. It's just fun to see who's where :-)

[[Category:Development]]

Documentation/Building Guide/Getting the source

2010-07-13T20:42:37Z

Gang65: /* SCM-Access for the current development line (named DEV300) using Mercurial as SCM */

{{Documentation/Building Guide TOC
|ShowNextPage=none
|ShowPrevPage=none
}}
{{DISPLAYTITLE:Getting the source}}

The source code can be fetched in several ways, as described below.

= Source Tarballs (for package maintainers) =

The latest release version of the source code can be downloaded as tarballs from [http://download.openoffice.org/ Download], see '''Source''' on the right.

The source is pretty big and has therefore been split into several files.

{| class="prettytable" border="1" width="100%"
|-
!Tarball
!Description
|-
|OOo_3.x.x_src_core.tar.bz2
|The necessary part for each build, the other tarballs depend on this one.
|-
|OOo_3.x.x_src_system.tar.bz2
|Libraries that usually exist on a standard Linux system<ref name="Foot1">{{Template:Documentation/Note|It's not absolutely necessary to build own versions for these modules on Linux. If you intend to build on Linux '''without''' the '''system''' tarball:
* You will need to tell ./configure explicitly to use the system libraries for the software that is otherwise contained in this tarball. Otherwise the build will fail.
* System software is in active development. If it has changed significantly (and Mozilla sometimes does), the build may fail or OpenOffice.org may not work correctly.
* unowinreg.dll - Do not be fooled by the .dll extension. Without it, the build will fail on Linux and it is not included in the core package. Don't worry about downloading this now because the build process will tell you where to get it and where to stick it to proceed.}}

</ref>. For a Windows build this package is usually required.
|-
|OOo_3.x.x_src_binfilter.tar.bz2
|The filters for old binary StarOffice formats
|-
|OOo_3.x.x_src_l10n.tar.bz2
|Translations of the software for many languages
|-
|OOo_3.x.x_src_extensions.tar.bz2
|Extensions source package
|-
|OOo_3.x.x_src_testautomation.tar.bz2
|Automated test suite (optional)
|}

For a full build you need them all. For development, the '''core''' package is usually all you need.

Unpack the tarballs one at a time to a directory. They will create a new directory with the name of the milestone, such as <tt>OOO310_m11</tt>. This folder will from now on be the <code>$SRC_ROOT</code>, when you run <code>./configure</code> it will create a shell-script that will set the environment variable to this path.
{{Template:Documentation/Caution|Avoid using winzip to extract the downloaded source archive. Observed problems include:
* CR-LF errors that can affect makefiles and cause compile errors
* Certain files unpacked into root folder, esp. likely when actual path is deeply nested (e.g. <code>foo/bar/source/foo/java/org/x/y/z/w/LongFileName.hmm</code>) which again causes mysterious compile errors.
Use the tar from Cygwin instead:

unzip for <tt>.gz</tt>
<pre>tar xvzf OOo_3.x.x_src_core.tar.gz</pre>
bzip2 for <tt>.bz2</tt>
<pre>tar xvjf OOo_3.1.0_src_core.tar.bz2</pre>}}

= SCM-Access for the current development line (named DEV300) using Mercurial as SCM =

Mercurial (hg) replaces Subversion end of October 2009. The mercurial master repository is already in place. You can clone the repository with

hg clone http://hg.services.openoffice.org/DEV300 <working_dir>

The OOo Mercurial repository is huge. Cloning the OOo repository as shown above my take some hours depending on the quality of your internet connection. We provide a nightly snapshot as Mercurial bundle which is currently about 1.3 GB in size. Utilizing this bundle is the fastest way to get an initial clone of the repository.

Download the bundle here: http://hg.services.openoffice.org/bundle/DEV300.hg
mkdir <working_dir>
cd <working_dir>
hg init
hg unbundle <path_to_bundle>/DEV300.hg
hg pull http://hg.services.openoffice.org/DEV300
hg update

Both methods will get you a repository and a working tree with the latest changes.

List all available milestones (a stable development version released by RelEng):
hg tags

Checking out a milestone
hg update -rDEV300_mXX

{{Template:Documentation/Tip| For more information on using Mercurial with OOo, see:
* [[Mercurial]]
* [[:Category:Mercurial]]}}

= SCM-Access for the 3.2 release code line (named OOO320) using Subversion as SCM =
Checking out a milestone (a stable development version released by RelEng)

svn checkout svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX/

Replace XX with the highest currently available milestone.

The files will be placed in the current directory.

See:

http://svn.services.openoffice.org/ooo/tags/

for a list of available milestones.
{{Template:Documentation/Note|For more information on using Subversion with OOo, see:
* [[Setting up Subversion Access]]
* [[OOo and Subversion|Using Subversion and the new CWS Tooling]]}}

= See also =

{{Template:Documentation/Note|For pre-3.1 releases, see [[Getting the source (older versions)]].}}

----
<references/>
{{PDL1}}
[[Category:SVN]][[Category:Mercurial]]

Mercurial/Getting Started

2010-06-30T07:38:50Z

Gang65:

{{Mercurial}}
__TOC__

This page aims to help cvs/svn users to get started with mercurial, without the need to dig in cyberspace for basic stuff.
If you have a tip or general remark to share, feel free to edit the page - It's a wiki after all :-)
Especially if you see something wrong here, just correct it without asking for permission on the ML

= The very basics: Mercurial is a DVCS =
Mercurial (hg) is a distributed version control system. This is a major difference compared to tools like CVS or subversion and that difference imposes a changed workflow compared to centralized version control systems.

== Your checkout is a full repository ==
In a simplified view, every checkout is a full repository. You have history and version info for other branches in your local tree. So naturally such a checkout is rather big compared to a single-revision checkout done by cvs and svn. So you won't checkout a full repo every time (unless you have bandwidth to waste and too much time on your hands :-)
Instead you will regularly update your local copy with the changes that were added to the repository and then "clone" (that's the term used for a "checkout") your local repository instead.

== Your commits go to your local repository first ==
Another difference is that any change you commit will be done in your local copy only at first.
You can accumulate many different commits locally and need to "push" changes to the master to finally have them in the main repo/available for everyone.

== There are no version numbers anymore ==
Because multiple persons can do local commits, have different "local master copies" (somebody else could have pushed a change to the master before that alters the file you change yourself), it is impossible to refer to a specific version of a file by a version number. What is version 23 of a file? The one in your local copy, that doesn't exist on the master yet? Or version 23 of a file of another user that did commit the same file locally?
So instead of version numbers, specific versions are referred to using "changeset" identifiers. Think of it as checksums.

{{Template:Documentation/Tip| Mercurial offers the possibilities to use easier to type numeric revisions instead of changeset identifiers during work with a local repository. But remember: these numbers have no meaning outside this specific local repository. Don't use them when communicating with others.}}

== Further reading ==
Remembering the three points above are enough to get you going. If you want to know more you'll find all things Mercurial at the [[hg:|Mercurial Wiki]]. An excellent tutorial can be found in "tour" chapters of the [http://hgbook.red-bean.com/read/ Mercurial book], which is also available online. Another excellent illustrated tutorial aimed at a broad audience (written by [http://joelonsoftware.com/ Joel Spolski], no less) can be found [http://hginit.com/ here].

The Mercurial command line help is quite well written and concise. Make good use of it. Example:
<pre>
$ hg merge --help
</pre>

To get an overview over all commands and some concepts type:
<pre>
$ hg help
</pre>

= So how to use it then (aka: What commands do I have to type?) =

You want to play around with the OpenOffice.org sources without bothering with all the things a OOo domain developer needs to keep in mind? You aren't interested in this CWS thing at all? Good, this section is for you.

== Creating a local copy ==
Creating a local copy means to clone from the master - the URL for the the main OOo development code line is http://hg.services.openoffice.org/DEV300
$ hg clone http://hg.services.openoffice.org/DEV300 local_DEV300
If you know that you'll only use this as basis for different local clones and don't want it to create the actual source-files, then you can use
$ hg clone -U http://hg.services.openoffice.org/DEV300 local_DEV300
This will create a treeless version, i.e. you'll get an (apparently) empty OOo-tip-repo-only directory that holds the history/changeset data only, but not the actual files. Saves some diskspace and lessens the risk of modifying the master you intended to keep pristine.

{{Template:Documentation/Tip| The OOo mercurial repository is quite huge, so doing cloning from the OOo server will take substantial time. A significant faster way is to download a nightly (GMT) created so called ''[[hg:Bundle|bundle]]'' of DEV300 which is available at http://hg.services.openoffice.org/bundle/DEV300.hg. This bundle contains the full history in one highly compressed file (currently about 800MB in size). Create a treeless local DEV300 copy with
$ mkdir local_DEV300
$ cd local_DEV300
$ hg init
$ hg unbundle <path_to_bundle>/DEV300.hg
and proceed with updating it with the latest changes as described below.}}

== Pulling new changes from the master and updating the local copy ==
As mentioned above, doing a full clone from the OOo server every time would be a waste, so how to stay up-to-date then?

Updating means "pulling the new changes" from the master:
$ cd local_DEV300 # change to the directory of your main clone
$ hg pull http://hg.services.openoffice.org/DEV300
{{Template:Documentation/Caution| While this grabs all the changes that were done on the master since the last checkout, it will '''not''' automatically update the source-code files on your disk. It basically only gets the history and changesets.}}
Not updating the source tree is just what we want for a treeless copy. But if you want local source-files to reflect the newest changes, you need to do an update of your tree:
$ hg update
Since pulling the newest changes and updating to those changes is rather common, you can use the -u switch to the pull command to do both in one go:
# alternative to separate pull and update
$ hg pull -u http://hg.services.openoffice.org/DEV300
{{Template:Documentation/Note| The URL is optional in all of the above commands - if omitted, it will just use the URL that was used to clone the repo.}}

== Cloning from the local repo to create a working copy ==
It is easier to keep a pristine copy of the sources as a base for new work, than to clean up an already modified repo, especially when you're not familiar with the tools yet :-) - so to create a working playground for your real work, clone from your local main-clone:
$ hg clone local_DEV300 working_DEV300 # where local_DEV300 is your main-checkout

If you need an earlier milestone examine the tags and update your working copy to the desired milestone (you might want to use clone -U in the command above then).
$ cd working_DEV300
$ hg tags # in case you don't already know the name of the tag
$ hg update -r DEV300_m60 # if you want milestone DEV300:m60

{{Template:Documentation/Caution| The above method is much faster than the apparently easier method of using clone with a revision.
<strong>Don't use</strong>
$ hg clone -r DEV300_m60 local_DEV300 working_DEV300
as mercurial would have to examine the whole history to throw out everything that wasn't part of DEV300_m60, and it cannot make use of hardlinks, thus it will require a significant amount of diskspace as well.
Depending on how fast your system is, the difference can be something like 30 minutes for the "clone -r" method and just 3 minutes for the "first clone, then update" one. You have been warned.}}

== Explore the working tree and history ==

The basic Mercurial commands are very similar to their equivalents in SVN and CVS.

$ hg status sw # shows the status of all files in directory sw
$ hg status # shows the status of the whole tree!

{{Template:Documentation/Caution| Most Mercurial commands, when specified without file/directory argument, will operate on the whole tree. This will come as a surprise to SVN and CVS users. You'll notice it when your status command scans the whole tree instead of a single directory, or you accidentally commit files in a far away directory.}}

$ hg log cws.pl # shows all changesets affecting file cws.pl
$ hg log -v | more # shows all changes in the repository in verbose format
$ hg log -v -r 262026 # shows verbose log of the changset with the numeric id 262026 (only locally valid!)

$ hg diff cws.pl # shows local (= not yet committed) modifications of cws.pl
$ hg diff --git # shows all not yet committed modifications in tree, format is git-diff
$ hg diff -c 2e9d06d9922d # show all changes made by changeset 2e9d06d9922d
$ hg diff -r 4e62cb377115 -r d6f5cf344cec cws.pl # show diff of cws.pl between the two rev.

== Committing your changes ==

Commit your changes to your local repository is straighforward:

$ hg commit -m"foo42: #i4711# implement foobar gadget" # Commit all your locally modified files
$ hg commit cws.pl # Commit cws.pl, an editor will pop up for the commit log

== Merging ==

Occasionally you will need to merge changes. Say you are working on repository cloned a while ago and now you want to update to the latest DEV300 milestone:

$ hg pull http://hg.services.openoffice.org/DEV300

Mercurial will tell you that you need to merge the freshly pull changes with your local changes

$ hg merge

In many cases automerging the files will suffice, but occasionally you'll get conflicts. Fix the conflicts and mark the conflicted file as resolved.

$ hg resolve -m solenv/bin/cws.pl # mark the conflict in cws.pl as resolved

Check if there are more unresolved conflicts with

$ hg resolve -l

When all conflicted files are resolved commit the result with

$ hg commit -m"foo42: merge with DEV300 m63"

== Exchanging your work with others ==

There are a number of ways on how to exchange your work with others. OpenOffice.org domain developers use a process called "child workspaces (CWS)" as the main way to organize collaboration. How to work with Mercurial based Child Workspaces is described [[Mercurial/Cws|here]].

If you are not (yet) a OOo domain developer you can export your changes as patch and attach it to an issue or send it to the developers mailing list

$ hg export tip > tip.patch

When you made larger changes you could use the [[hg:PatchbombExtension|patchbomb extension]] for proper formatting before sending to the mailing list.

Mercurial/Setup

2010-06-30T07:36:22Z

Gang65:

{{Mercurial}}

=Installing Mercurial=

Mercurial source and binary distributions are available at the [[hg:|Mercurial Wiki]]. Many Linux distributions, OpenSolaris and cygwin (Windows) offer Mercurial packages as well. Installing from source requires a working [http://www.python.org/ Python] installation. Windows users have the choice between a cygwin based Mercurial and [[hg:TortoiseHg|TortoiseHg]], the latter one "is an all-inclusive Mercurial binary installer package for Windows".

{{Template:Documentation/Caution| Some cygwin versions exhibit a bug which affects hg and other tools. If your cygwin hg complains about: "*** fatal error - could not load shell32, Win32 error 487" use TortoiseHg instead.}}

=SSH Authentication=

Domain developers can publish their changes on [http://hg.services.openoffice.org hg.services.openoffice.org]. If you are not a domain developer or do not plan to publish your changes via this way to the OOo community just skip this section. Mercurial is a distributed SCM, there are other ways to contribute your changes without having write access to this server.

==SSH key generation==

On Unix or Windows/cygwin a SSH identity (private/public key pair) is generated with:

ssh-keygen -t dsa

You'll be asked for pass phrase which protects your private key. Per default the public key is named <tt>$HOME/.ssh/id_dsa.pub</tt>.

Note that SSH keys created between September 2006 and May 2008 on Debian or Debian derived systems like Ubuntu may be insecure. Please use recent SSH tools.

If you want a dedicated identity for just OOo SVN usage, generate a specially named key pair

ssh-keygen -t dsa -f ~/.ssh/id_dsa_ooo_svn

==Initial Migration of Keys==

All existing public keys for SVN usage have been migrated for Mercurial use as well. If you are a new domain developer please create a new issue, attach your public key to it and and add it as a dependency to [http://www.openoffice.org/issues/show_bug.cgi?id=94002 issue 94002].

==Ongoing Maintenance==

We will continue to use IssueZilla for managing and tracking key additions and changes.
Please see [http://www.openoffice.org/docs/ddSSHGuide.html#sendingkey Submitting Your Certificate (Public Key)].

=Configuring Mercurial=

Mercurial can be configured via system, user and repository configure files. The most interesting one is the user specific configuration file in <tt>$HOME/.hgrc</tt>. Example:

<pre>
[ui]
# The user name will appear as author tag on commits.
username=Joe Developer <nowiki><jdeveloper@openoffice.org></nowiki>
# Domain developers only: OOo ssh authentication for pushing
# to 'outgoing' repositories.
ssh=ssh -C -i <path_to_OOo_ssh_identity>

[extensions]
# Required if 'cws fetch' is used to fetch a CWS.
hgext.mq=
# Enables the bundled win32text extension. See [hooks] section.
hgext.win32text=

[hooks]
# Reject commits which would introduce windows-style CR/LF.
# Enabling this hook is strongly suggested for OOo development.
pretxncommit.crlf = python:hgext.win32text.forbidcrlf
</pre>

Let's examine this configuration file entry for entry:

<pre>
[ui]
username=Joe Developer <nowiki><jdeveloper@openoffice.org></nowiki>
</pre>

The author tag of a changeset is set on commit, and becomes part of the history. Set this entry to identify yourself as author, common usage is to use your name and the OOo email address here.

{{Template:Documentation/Tip| It's possible to use other email addresses than the OOo one, but in this case please add your OOo account in square braces. Example: "Joe Developer [jdeveloper] <joe@example.com>". It must always be possible to relate a contribution with an OOo account, the contribution will be rejected otherwise. If you are absolutely not comfortable with disclosing your real name it's possible to use a pseudonym or just your account name instead, but be reasonable.}}

<pre>
[ui]
ssh=ssh -C -i <path_to_OOo_ssh_identity>
</pre>

OOo domain developers can create "child workspaces", which are effectively public feature branches. Publishing changes on [http://hg.services.openoffice.org hg.services.openoffice.org] requires SSH access, which is configured here. Be sure to use a compressed ssh connection (<tt>-C</tt>).

<pre>
[extensions]
hgext.mq=
hgext.win32text=
</pre>

Mercurial supports a huge number of useful [http://mercurial.selenic.com/wiki/UsingExtensions extensions], many of them come bundled. Enable here whatever you want to use. The 'mq' extension is required if you want to use the 'cws fetch' tool since it makes use of 'hg strip' which is part of the 'mq' extension. The 'win32text' extension is strongly suggested for all OOo developers who work on windows at least occasionally, it provides a hook which prevents you from committing files with CR/LF in them.

<pre>
[hooks]
pretxncommit.crlf = python:hgext.win32text.forbidcrlf
</pre>

This is one of the hooks provided by 'win32text'. Disable it on the peril of aggravating the whole OOo developer community.

Mercurial/Cws

2010-06-29T19:50:23Z

Gang65: /* Creating the child workspace in EIS */

{{Mercurial}}
This page discusses the Mercurial part of handling child workspaces (CWSs). It assumes some basic Mercurial knowledge which you can find at the [[Mercurial/Getting Started|Getting Started Page]].

= The OpenOffice.org repository setup =

The OpenOffice.org Mercurial repository is huge, it contains more than 260000 changesets and exceeds 1 GiB in size. Repeatably exchanging this vast numbers of changesets over the Net is prohibitive and wasteful. It's also not necessary. We were careful to employ a setup which is designed to minimize the number of changesets exchanged over the Net. The basic idea is to create a so called 'outgoing' repository for each CWS on the main OOo SCM server. The 'outgoing' repository already has each changeset up to and including the milestone the CWS was created on. It is meant as the main collaboration point around the child workspace and is also the place where release engineering will fetch a child workspace when it's ready for integration.

[[Image:Dscm-setup-ver3.png|500px|center|OpenOffice.org repository setup]]

= Workflow =

The workflow is best explained with an example:

== Creating the child workspace in EIS ==

You need to have <code>perl SOAP::Lite</code> module installed for <tt>cws create</tt> to work. See [[CPAN install]] page for how to install Perl modules.

{{Template:Documentation/Note|On a Debian/Ubuntu based distribution install the <tt>libsoap-lite-perl</tt> package:
sudo aptitude install libsoap-lite-perl
}}
Create CWS config file <code>$HOME/.cwsrc</code> [http://wiki.services.openoffice.org/wiki/CWS following on instruction]

Create child workspace with name <code>foo42</code>, latest available milestone:

$ cws create --hg DEV300 foo42

This command will register CWS ''foo42'' with EIS and set its SCM property to Mercurial. An 'outgoing' repository will be created (this may take up to one hour) on the SCM server where you can publish your changes.

{{Template:Documentation/Note| <code>cws create</code> will in future default to hg, obsoleting the <code>--hg</code> switch - as soon as we get rid of SVN for the OOO310 and OOO320 codelines.}}

As an alternative way you can use the EIS web fronted to create the CWS and set it to status 'new'. Don't forget to set the SCM property to 'HG'.

== Preparing the working tree ==

===Method A===

Make sure that your local pristine copy contains the latest milestone.

$ cd <local_pristine_copy>
$ hg pull http://hg.services.openoffice.org/DEV300

Clone your working tree from the pristine local copy

$ hg clone <local_pristine_copy> foo42

{{Documentation/Caution|''' Note the above is valid only for a new created cws, not for older cws!''' This is because the above command will clone the cws up to the current head of the master. This might not be what you want when you want to work on an existing cws currently based on an older milestone, because in that case you would need to merge changes from the master immediately (what once was a "cws rebase"). So when you need a working copy of an older cws and dont want to merge the newest changes on the master use:

<code>$ hg clone -r <current_cws_milestone> <local_pristine_copy> foo42</code>.

For more information see the [[Mercurial/Tips And Tricks|Tips And Tricks Section]].}}

Change the default push location to the OOo SCM server

$ echo 'default-push=ssh://hg@hg.services.openoffice.org/cws/foo42' >> foo42/.hg/hgrc

If there are already changes in the outgoing repository pull them into your working tree

$ cd foo42
$ hg pull -u http://hg.services.openoffice.org/cws/foo42

===Method B===

If there is a proper ''$HOME/.cwsrc'' configuration (see below), you can use the ''cws fetch'' command.

{{Template:Documentation/Note| Use the version of ''cws fetch'' which comes with DEV300 m63 or later. }}

$ cws fetch -c foo42 foo42

{{Template:Documentation/Caution| Make sure that either your local source contains the used milestone *or* the 'outgoing' repository is already available on the server. Otherwise you might base your working tree on an older milestone. If this happened, just do a pull/update from http://hg.services.openoffice.org/DEV300}}

The ''cws fetch'' command adds the default-push location and a hook (prevents the commit of CR/LF in changed files), no need to configure this by hand.

== Commit changes ==

Not much to be said here. Please format the first line of the commit message according to the example below:

$ hg commit -m"foo42: #i4711#: implement feature foo" foo.cxx

{{Template:Documentation/Caution| Remember, ''hg commit'' will search the whole tree for to be committed changes if no file/directory is specified.}}

{{Template:Documentation/Note| Why the name of the CWS in front of the first commit message line? This way we can immediately see which CWS was the origin of a changeset when browsing the history.}}

{{Template:Documentation/Tip| Make the first line of your commit message concise and stand alone (like an email subject). This will make for a far better browseable history in the long run. See [http://mercurial.selenic.com/wiki/ChangeSetComments] why.}}

== Publishing changes ==

Committing changes just does add them to your local repository. For publishing your changes to the OOo developer community just push them to the 'outgoing' repository.

$ hg push ssh://hg@hg.services.openoffice.org/cws/foo42

If the repository ''hgrc'' has the correct "default-push" entry, the URL can be omitted.

{{Template:Documentation/Caution| If someone else pushed changes to the outgoing repository, ''hg push'' might tell you that your push would create a new head and abort. It's possible to override the abort with the'' -f (--force)'' switch. '''Never''' do this. Just pull the changesets in question, merge them and then push the combined result.}}

{{Template:Documentation/Note| If you are inclined to fake^H^H^H^Hbeautify the commit history, do it before pushing your changesets to the outgoing repository. Once there, your changesets are published and thus should never be meddled with.}}

==Merge changes from the latest milestone in to the CWS==

Updating your CWS to the latest milestone is easier and by *far* faster than with CVS and SVN.

First pull the latest changes from DEV300 into your CWS

$ cd foo42
$ hg pull http://hg.services.openoffice.org/DEV300
$ hg merge

Often enough the merge might result in conflicts. You can list the merged files with and without conflicts with
$ hg resolve -l

Once a conflict is fixed mark the corresponding file as resolved
$ hg resolve -m <conflicted_file>

To start over with the merge process (this will loose all your conflict resolutions up to now!!!)
$ hg resolve -a

When every conflict is resolved commit the result of the merge
$ hg commit -m"foo42: merge with DEV300 m60"

When you are satisfied with merge don't forget to bump up the milestone in EIS
$ hg push ssh://hg@hg.services.openoffice.org/cws/foo42
$ cws setcurrent -m m60

The milestone can also be changed via EIS web front end.

Don't know which was the latest milestone? Find out with
$ cws query latest

==Integration==

When the CWS is nominated, RE will take the changesets from the 'outgoing' repository. Obviously at this point in time latest your changesets must be published there.

RE might ask you to update your CWS again if there are to many conflicts. Just do another pull/merge/resolve/commit/push cycle then.

=Configuring ''cws fetch''=

''cws fetch'' can be configured to make use of LOCAL (means: on the same disk) and LAN resources for fast clone operations.

Simply add and configure the following entries in your $HOME/.cwsrc

<pre>
# Directory where pristine copies of OOo master workspaces (ie. DEV300) are kept on the local disk
# HG_LOCAL_SOURCE=
# Example:
HG_LOCAL_SOURCE=/export/hg_clean

# URL where pristine copies of OOo master workspaces (ie. DEV300) are available in a LAN
# HG_LAN_SOURCE=
# Example:
HG_LAN_SOURCE=http://myserver.example.com:8000/

# The OOo SCM server
HG_REMOTE_SOURCE=http://hg.services.openoffice.org
</pre>

See [[.cwsrc]] for a complete configuration file.

[[Category:CWSTooling]]

Mercurial/Cws

2010-06-29T19:37:18Z

Gang65: /* Creating the child workspace in EIS */

{{Mercurial}}
This page discusses the Mercurial part of handling child workspaces (CWSs). It assumes some basic Mercurial knowledge which you can find at the [[Mercurial/Getting Started|Getting Started Page]].

= The OpenOffice.org repository setup =

The OpenOffice.org Mercurial repository is huge, it contains more than 260000 changesets and exceeds 1 GiB in size. Repeatably exchanging this vast numbers of changesets over the Net is prohibitive and wasteful. It's also not necessary. We were careful to employ a setup which is designed to minimize the number of changesets exchanged over the Net. The basic idea is to create a so called 'outgoing' repository for each CWS on the main OOo SCM server. The 'outgoing' repository already has each changeset up to and including the milestone the CWS was created on. It is meant as the main collaboration point around the child workspace and is also the place where release engineering will fetch a child workspace when it's ready for integration.

[[Image:Dscm-setup-ver3.png|500px|center|OpenOffice.org repository setup]]

= Workflow =

The workflow is best explained with an example:

== Creating the child workspace in EIS ==

You need to have <code>perl SOAP::Lite</code> module installed for <tt>cws create</tt> to work. See [[CPAN install]] page for how to install Perl modules.

On a Debian/Ubuntu based distribution install the <tt>libsoap-lite-perl</tt> package:
sudo aptitude install libsoap-lite-perl

Create CWS config file <code>$HOME/.cwsrc</code> [http://wiki.services.openoffice.org/wiki/CWS following on instruction]

Create child workspace with name <code>foo42</code>, latest available milestone:

$ cws create --hg DEV300 foo42

This command will register CWS ''foo42'' with EIS and set its SCM property to Mercurial. An 'outgoing' repository will be created (this may take up to one hour) on the SCM server where you can publish your changes.

{{Template:Documentation/Note| <code>cws create</code> will in future default to hg, obsoleting the <code>--hg</code> switch - as soon as we get rid of SVN for the OOO310 and OOO320 codelines.}}

As an alternative way you can use the EIS web fronted to create the CWS and set it to status 'new'. Don't forget to set the SCM property to 'HG'.

== Preparing the working tree ==

===Method A===

Make sure that your local pristine copy contains the latest milestone.

$ cd <local_pristine_copy>
$ hg pull http://hg.services.openoffice.org/DEV300

Clone your working tree from the pristine local copy

$ hg clone <local_pristine_copy> foo42

{{Documentation/Caution|''' Note the above is valid only for a new created cws, not for older cws!''' This is because the above command will clone the cws up to the current head of the master. This might not be what you want when you want to work on an existing cws currently based on an older milestone, because in that case you would need to merge changes from the master immediately (what once was a "cws rebase"). So when you need a working copy of an older cws and dont want to merge the newest changes on the master use:

<code>$ hg clone -r <current_cws_milestone> <local_pristine_copy> foo42</code>.

For more information see the [[Mercurial/Tips And Tricks|Tips And Tricks Section]].}}

Change the default push location to the OOo SCM server

$ echo 'default-push=ssh://hg@hg.services.openoffice.org/cws/foo42' >> foo42/.hg/hgrc

If there are already changes in the outgoing repository pull them into your working tree

$ cd foo42
$ hg pull -u http://hg.services.openoffice.org/cws/foo42

===Method B===

If there is a proper ''$HOME/.cwsrc'' configuration (see below), you can use the ''cws fetch'' command.

{{Template:Documentation/Note| Use the version of ''cws fetch'' which comes with DEV300 m63 or later. }}

$ cws fetch -c foo42 foo42

{{Template:Documentation/Caution| Make sure that either your local source contains the used milestone *or* the 'outgoing' repository is already available on the server. Otherwise you might base your working tree on an older milestone. If this happened, just do a pull/update from http://hg.services.openoffice.org/DEV300}}

The ''cws fetch'' command adds the default-push location and a hook (prevents the commit of CR/LF in changed files), no need to configure this by hand.

== Commit changes ==

Not much to be said here. Please format the first line of the commit message according to the example below:

$ hg commit -m"foo42: #i4711#: implement feature foo" foo.cxx

{{Template:Documentation/Caution| Remember, ''hg commit'' will search the whole tree for to be committed changes if no file/directory is specified.}}

{{Template:Documentation/Note| Why the name of the CWS in front of the first commit message line? This way we can immediately see which CWS was the origin of a changeset when browsing the history.}}

{{Template:Documentation/Tip| Make the first line of your commit message concise and stand alone (like an email subject). This will make for a far better browseable history in the long run. See [http://mercurial.selenic.com/wiki/ChangeSetComments] why.}}

== Publishing changes ==

Committing changes just does add them to your local repository. For publishing your changes to the OOo developer community just push them to the 'outgoing' repository.

$ hg push ssh://hg@hg.services.openoffice.org/cws/foo42

If the repository ''hgrc'' has the correct "default-push" entry, the URL can be omitted.

{{Template:Documentation/Caution| If someone else pushed changes to the outgoing repository, ''hg push'' might tell you that your push would create a new head and abort. It's possible to override the abort with the'' -f (--force)'' switch. '''Never''' do this. Just pull the changesets in question, merge them and then push the combined result.}}

{{Template:Documentation/Note| If you are inclined to fake^H^H^H^Hbeautify the commit history, do it before pushing your changesets to the outgoing repository. Once there, your changesets are published and thus should never be meddled with.}}

==Merge changes from the latest milestone in to the CWS==

Updating your CWS to the latest milestone is easier and by *far* faster than with CVS and SVN.

First pull the latest changes from DEV300 into your CWS

$ cd foo42
$ hg pull http://hg.services.openoffice.org/DEV300
$ hg merge

Often enough the merge might result in conflicts. You can list the merged files with and without conflicts with
$ hg resolve -l

Once a conflict is fixed mark the corresponding file as resolved
$ hg resolve -m <conflicted_file>

To start over with the merge process (this will loose all your conflict resolutions up to now!!!)
$ hg resolve -a

When every conflict is resolved commit the result of the merge
$ hg commit -m"foo42: merge with DEV300 m60"

When you are satisfied with merge don't forget to bump up the milestone in EIS
$ hg push ssh://hg@hg.services.openoffice.org/cws/foo42
$ cws setcurrent -m m60

The milestone can also be changed via EIS web front end.

Don't know which was the latest milestone? Find out with
$ cws query latest

==Integration==

When the CWS is nominated, RE will take the changesets from the 'outgoing' repository. Obviously at this point in time latest your changesets must be published there.

RE might ask you to update your CWS again if there are to many conflicts. Just do another pull/merge/resolve/commit/push cycle then.

=Configuring ''cws fetch''=

''cws fetch'' can be configured to make use of LOCAL (means: on the same disk) and LAN resources for fast clone operations.

Simply add and configure the following entries in your $HOME/.cwsrc

<pre>
# Directory where pristine copies of OOo master workspaces (ie. DEV300) are kept on the local disk
# HG_LOCAL_SOURCE=
# Example:
HG_LOCAL_SOURCE=/export/hg_clean

# URL where pristine copies of OOo master workspaces (ie. DEV300) are available in a LAN
# HG_LAN_SOURCE=
# Example:
HG_LAN_SOURCE=http://myserver.example.com:8000/

# The OOo SCM server
HG_REMOTE_SOURCE=http://hg.services.openoffice.org
</pre>

See [[.cwsrc]] for a complete configuration file.

[[Category:CWSTooling]]

Mercurial/Cws

2010-06-29T19:27:24Z

Gang65: /* Creating the child workspace in EIS */

{{Mercurial}}
This page discusses the Mercurial part of handling child workspaces (CWSs). It assumes some basic Mercurial knowledge which you can find at the [[Mercurial/Getting Started|Getting Started Page]].

= The OpenOffice.org repository setup =

The OpenOffice.org Mercurial repository is huge, it contains more than 260000 changesets and exceeds 1 GiB in size. Repeatably exchanging this vast numbers of changesets over the Net is prohibitive and wasteful. It's also not necessary. We were careful to employ a setup which is designed to minimize the number of changesets exchanged over the Net. The basic idea is to create a so called 'outgoing' repository for each CWS on the main OOo SCM server. The 'outgoing' repository already has each changeset up to and including the milestone the CWS was created on. It is meant as the main collaboration point around the child workspace and is also the place where release engineering will fetch a child workspace when it's ready for integration.

[[Image:Dscm-setup-ver3.png|500px|center|OpenOffice.org repository setup]]

= Workflow =

The workflow is best explained with an example:

== Creating the child workspace in EIS ==

You need to have perl SOAP::Lite module installed for <tt>cws create</tt> to work. See [[CPAN install]] page for how to install Perl modules.
On a Debian/Ubuntu based distribution install the <tt>libsoap-lite-perl</tt> package:
sudo aptitude install libsoap-lite-perl

Create child workspace with name foo42, latest available milestone:

$ cws create --hg DEV300 foo42

This command will register CWS ''foo42'' with EIS and set its SCM property to Mercurial. An 'outgoing' repository will be created (this may take up to one hour) on the SCM server where you can publish your changes.

{{Template:Documentation/Note| ''cws create'' will in future default to hg, obsoleting the ''--hg'' switch - as soon as we get rid of SVN for the OOO310 and OOO320 codelines.}}

As an alternative way you can use the EIS web fronted to create the CWS and set it to status 'new'. Don't forget to set the SCM property to 'HG'.

== Preparing the working tree ==

===Method A===

Make sure that your local pristine copy contains the latest milestone.

$ cd <local_pristine_copy>
$ hg pull http://hg.services.openoffice.org/DEV300

Clone your working tree from the pristine local copy

$ hg clone <local_pristine_copy> foo42

{{Documentation/Caution|''' Note the above is valid only for a new created cws, not for older cws!''' This is because the above command will clone the cws up to the current head of the master. This might not be what you want when you want to work on an existing cws currently based on an older milestone, because in that case you would need to merge changes from the master immediately (what once was a "cws rebase"). So when you need a working copy of an older cws and dont want to merge the newest changes on the master use:

<code>$ hg clone -r <current_cws_milestone> <local_pristine_copy> foo42</code>.

For more information see the [[Mercurial/Tips And Tricks|Tips And Tricks Section]].}}

Change the default push location to the OOo SCM server

$ echo 'default-push=ssh://hg@hg.services.openoffice.org/cws/foo42' >> foo42/.hg/hgrc

If there are already changes in the outgoing repository pull them into your working tree

$ cd foo42
$ hg pull -u http://hg.services.openoffice.org/cws/foo42

===Method B===

If there is a proper ''$HOME/.cwsrc'' configuration (see below), you can use the ''cws fetch'' command.

{{Template:Documentation/Note| Use the version of ''cws fetch'' which comes with DEV300 m63 or later. }}

$ cws fetch -c foo42 foo42

{{Template:Documentation/Caution| Make sure that either your local source contains the used milestone *or* the 'outgoing' repository is already available on the server. Otherwise you might base your working tree on an older milestone. If this happened, just do a pull/update from http://hg.services.openoffice.org/DEV300}}

The ''cws fetch'' command adds the default-push location and a hook (prevents the commit of CR/LF in changed files), no need to configure this by hand.

== Commit changes ==

Not much to be said here. Please format the first line of the commit message according to the example below:

$ hg commit -m"foo42: #i4711#: implement feature foo" foo.cxx

{{Template:Documentation/Caution| Remember, ''hg commit'' will search the whole tree for to be committed changes if no file/directory is specified.}}

{{Template:Documentation/Note| Why the name of the CWS in front of the first commit message line? This way we can immediately see which CWS was the origin of a changeset when browsing the history.}}

{{Template:Documentation/Tip| Make the first line of your commit message concise and stand alone (like an email subject). This will make for a far better browseable history in the long run. See [http://mercurial.selenic.com/wiki/ChangeSetComments] why.}}

== Publishing changes ==

Committing changes just does add them to your local repository. For publishing your changes to the OOo developer community just push them to the 'outgoing' repository.

$ hg push ssh://hg@hg.services.openoffice.org/cws/foo42

If the repository ''hgrc'' has the correct "default-push" entry, the URL can be omitted.

{{Template:Documentation/Caution| If someone else pushed changes to the outgoing repository, ''hg push'' might tell you that your push would create a new head and abort. It's possible to override the abort with the'' -f (--force)'' switch. '''Never''' do this. Just pull the changesets in question, merge them and then push the combined result.}}

{{Template:Documentation/Note| If you are inclined to fake^H^H^H^Hbeautify the commit history, do it before pushing your changesets to the outgoing repository. Once there, your changesets are published and thus should never be meddled with.}}

==Merge changes from the latest milestone in to the CWS==

Updating your CWS to the latest milestone is easier and by *far* faster than with CVS and SVN.

First pull the latest changes from DEV300 into your CWS

$ cd foo42
$ hg pull http://hg.services.openoffice.org/DEV300
$ hg merge

Often enough the merge might result in conflicts. You can list the merged files with and without conflicts with
$ hg resolve -l

Once a conflict is fixed mark the corresponding file as resolved
$ hg resolve -m <conflicted_file>

To start over with the merge process (this will loose all your conflict resolutions up to now!!!)
$ hg resolve -a

When every conflict is resolved commit the result of the merge
$ hg commit -m"foo42: merge with DEV300 m60"

When you are satisfied with merge don't forget to bump up the milestone in EIS
$ hg push ssh://hg@hg.services.openoffice.org/cws/foo42
$ cws setcurrent -m m60

The milestone can also be changed via EIS web front end.

Don't know which was the latest milestone? Find out with
$ cws query latest

==Integration==

When the CWS is nominated, RE will take the changesets from the 'outgoing' repository. Obviously at this point in time latest your changesets must be published there.

RE might ask you to update your CWS again if there are to many conflicts. Just do another pull/merge/resolve/commit/push cycle then.

=Configuring ''cws fetch''=

''cws fetch'' can be configured to make use of LOCAL (means: on the same disk) and LAN resources for fast clone operations.

Simply add and configure the following entries in your $HOME/.cwsrc

<pre>
# Directory where pristine copies of OOo master workspaces (ie. DEV300) are kept on the local disk
# HG_LOCAL_SOURCE=
# Example:
HG_LOCAL_SOURCE=/export/hg_clean

# URL where pristine copies of OOo master workspaces (ie. DEV300) are available in a LAN
# HG_LAN_SOURCE=
# Example:
HG_LAN_SOURCE=http://myserver.example.com:8000/

# The OOo SCM server
HG_REMOTE_SOURCE=http://hg.services.openoffice.org
</pre>

See [[.cwsrc]] for a complete configuration file.

[[Category:CWSTooling]]

Mercurial/Cws

2010-06-28T23:43:15Z

Gang65: /* Creating the child workspace in EIS */

{{Mercurial}}
This page discusses the Mercurial part of handling child workspaces (CWSs). It assumes some basic Mercurial knowledge which you can find at the [[Mercurial/Getting Started|Getting Started Page]].

= The OpenOffice.org repository setup =

The OpenOffice.org Mercurial repository is huge, it contains more than 260000 changesets and exceeds 1 GiB in size. Repeatably exchanging this vast numbers of changesets over the Net is prohibitive and wasteful. It's also not necessary. We were careful to employ a setup which is designed to minimize the number of changesets exchanged over the Net. The basic idea is to create a so called 'outgoing' repository for each CWS on the main OOo SCM server. The 'outgoing' repository already has each changeset up to and including the milestone the CWS was created on. It is meant as the main collaboration point around the child workspace and is also the place where release engineering will fetch a child workspace when it's ready for integration.

[[Image:Dscm-setup-ver3.png|500px|center|OpenOffice.org repository setup]]

= Workflow =

The workflow is best explained with an example:

== Creating the child workspace in EIS ==

You need to have perl SOAP::Lite module installed for <tt>cws create</tt> to work. See [[CPAN install]] page for how to install Perl modules.

Create child workspace with name foo42, latest available milestone:

$ cws create --hg DEV300 foo42

This command will register CWS ''foo42'' with EIS and set its SCM property to Mercurial. An 'outgoing' repository will be created (this may take up to one hour) on the SCM server where you can publish your changes.

{{Template:Documentation/Note| ''cws create'' will in future default to hg, obsoleting the ''--hg'' switch - as soon as we get rid of SVN for the OOO310 and OOO320 codelines.}}

As an alternative way you can use the EIS web fronted to create the CWS and set it to status 'new'. Don't forget to set the SCM property to 'HG'.

== Preparing the working tree ==

===Method A===

Make sure that your local pristine copy contains the latest milestone.

$ cd <local_pristine_copy>
$ hg pull http://hg.services.openoffice.org/DEV300

Clone your working tree from the pristine local copy

$ hg clone <local_pristine_copy> foo42

{{Documentation/Caution|''' Note the above is valid only for a new created cws, not for older cws!''' This is because the above command will clone the cws up to the current head of the master. This might not be what you want when you want to work on an existing cws currently based on an older milestone, because in that case you would need to merge changes from the master immediately (what once was a "cws rebase"). So when you need a working copy of an older cws and dont want to merge the newest changes on the master use:

<code>$ hg clone -r <current_cws_milestone> <local_pristine_copy> foo42</code>.

For more information see the [[Mercurial/Tips And Tricks|Tips And Tricks Section]].}}

Change the default push location to the OOo SCM server

$ echo 'default-push=ssh://hg@hg.services.openoffice.org/cws/foo42' >> foo42/.hg/hgrc

If there are already changes in the outgoing repository pull them into your working tree

$ cd foo42
$ hg pull -u http://hg.services.openoffice.org/cws/foo42

===Method B===

If there is a proper ''$HOME/.cwsrc'' configuration (see below), you can use the ''cws fetch'' command.

{{Template:Documentation/Note| Use the version of ''cws fetch'' which comes with DEV300 m63 or later. }}

$ cws fetch -c foo42 foo42

{{Template:Documentation/Caution| Make sure that either your local source contains the used milestone *or* the 'outgoing' repository is already available on the server. Otherwise you might base your working tree on an older milestone. If this happened, just do a pull/update from http://hg.services.openoffice.org/DEV300}}

The ''cws fetch'' command adds the default-push location and a hook (prevents the commit of CR/LF in changed files), no need to configure this by hand.

== Commit changes ==

Not much to be said here. Please format the first line of the commit message according to the example below:

$ hg commit -m"foo42: #i4711#: implement feature foo" foo.cxx

{{Template:Documentation/Caution| Remember, ''hg commit'' will search the whole tree for to be committed changes if no file/directory is specified.}}

{{Template:Documentation/Note| Why the name of the CWS in front of the first commit message line? This way we can immediately see which CWS was the origin of a changeset when browsing the history.}}

{{Template:Documentation/Tip| Make the first line of your commit message concise and stand alone (like an email subject). This will make for a far better browseable history in the long run. See [http://mercurial.selenic.com/wiki/ChangeSetComments] why.}}

== Publishing changes ==

Committing changes just does add them to your local repository. For publishing your changes to the OOo developer community just push them to the 'outgoing' repository.

$ hg push ssh://hg@hg.services.openoffice.org/cws/foo42

If the repository ''hgrc'' has the correct "default-push" entry, the URL can be omitted.

{{Template:Documentation/Caution| If someone else pushed changes to the outgoing repository, ''hg push'' might tell you that your push would create a new head and abort. It's possible to override the abort with the'' -f (--force)'' switch. '''Never''' do this. Just pull the changesets in question, merge them and then push the combined result.}}

{{Template:Documentation/Note| If you are inclined to fake^H^H^H^Hbeautify the commit history, do it before pushing your changesets to the outgoing repository. Once there, your changesets are published and thus should never be meddled with.}}

==Merge changes from the latest milestone in to the CWS==

Updating your CWS to the latest milestone is easier and by *far* faster than with CVS and SVN.

First pull the latest changes from DEV300 into your CWS

$ cd foo42
$ hg pull http://hg.services.openoffice.org/DEV300
$ hg merge

Often enough the merge might result in conflicts. You can list the merged files with and without conflicts with
$ hg resolve -l

Once a conflict is fixed mark the corresponding file as resolved
$ hg resolve -m <conflicted_file>

To start over with the merge process (this will loose all your conflict resolutions up to now!!!)
$ hg resolve -a

When every conflict is resolved commit the result of the merge
$ hg commit -m"foo42: merge with DEV300 m60"

When you are satisfied with merge don't forget to bump up the milestone in EIS
$ hg push ssh://hg@hg.services.openoffice.org/cws/foo42
$ cws setcurrent -m m60

The milestone can also be changed via EIS web front end.

Don't know which was the latest milestone? Find out with
$ cws query latest

==Integration==

When the CWS is nominated, RE will take the changesets from the 'outgoing' repository. Obviously at this point in time latest your changesets must be published there.

RE might ask you to update your CWS again if there are to many conflicts. Just do another pull/merge/resolve/commit/push cycle then.

=Configuring ''cws fetch''=

''cws fetch'' can be configured to make use of LOCAL (means: on the same disk) and LAN resources for fast clone operations.

Simply add and configure the following entries in your $HOME/.cwsrc

<pre>
# Directory where pristine copies of OOo master workspaces (ie. DEV300) are kept on the local disk
# HG_LOCAL_SOURCE=
# Example:
HG_LOCAL_SOURCE=/export/hg_clean

# URL where pristine copies of OOo master workspaces (ie. DEV300) are available in a LAN
# HG_LAN_SOURCE=
# Example:
HG_LAN_SOURCE=http://myserver.example.com:8000/

# The OOo SCM server
HG_REMOTE_SOURCE=http://hg.services.openoffice.org
</pre>

See [[.cwsrc]] for a complete configuration file.

[[Category:CWSTooling]]

Architecture/To-Dos

2010-06-28T11:51:24Z

Gang65: /* Replace code with 3rd party */

<noinclude>[[Category:Architecture]] [[Category:To-Do]]</noinclude>

This page intends to collect various architectural deficiencies (aka the pet peeves of various people) of OpenOffice.org, and lists the areas where's work in progress to improve on the architecture.

Depending on the specific count algorithm, OOo consists of approximately 7E6 lines of code (the overwhelming lot being c++, all other being an order of magnitude less (Java, Perl, Basic, Python)). This sheer size in and of itself is a problem - the code base is notorious for crashing or slowing down to a crawl various software engineering tools, from debugger to dependency analysis to reverse design extraction.

The code itself varies greatly in quality, style, and age (the latter invariably leading to the former, if you recall the history and evolvement of c++), with parts being there virtually unmodified for 10+ years, and others just recently written from scratch.

Taken together, this leads to a lot of complexity and [http://artax.karlin.mff.cuni.cz/~kendy/ooo/cut-n-paste/src680-m154.txt.gz redundancy], which is very hard to remove.

Facing this amount of code, the big rules must be:
*simplify
**remove internal redundancy
**remove external redundancy (use external projects, whereever possible)
**remove unused or dead code
**remove legacy functionality, which does no longer provide noticeable value (e.g. [[Framework/Modules/binfilter|binfilter]])

*refactor for orthogonality
**make subsystems implement independent functionality
**enable combinations of those subsystems to be freely combinable
**carry that to the UI level (no artificial restrictions on what one can do with UI objects - e.g. shapes can be rotated, and clearly text frames should, too)

==Architectural To-Dos==
<DPL>category=To-Do
category=Architecture</DPL>

==Infrastructure Improvements==

*[[BuildSpeedup | Speeding up the build system]], and maybe even make it consider global dependencies (currently, OOo has the notion of modules, which approximately map to toplevel directories in the build tree. Automatic build-time dependency calculation is currently only available on the intra-module level).

*Making the actual design more accessible, improving upon existing solutions like [http://ooo.ximian.com/lxr/ LXR] or [http://ooo.ximian.com/bonsai/ Bonsai]. Ultimately, this should result in refactorings of the source code being both much easier and much safer than today, by providing information where and how specific functionality is used. A prerequisite for that would be a parser that ''really'' knows about c++ - [http://www.gccxml.org/ gccxml] might be a starting point.

==Runtime System Improvements==

This is about making the implementation languages safer, and easier to use. What follows could also be subsumed under "transparency on the implementation level". When something can be used transparently, or appears transparent to a user, it is an implementation aspect she need not care about. Being able to program in an environment which is transparent with regard to lots of aspects, empowers the developer to focus on the problem at hand, not having to litter her code with mundane tasks such as memory management or locking.

*Make threading transparent. Currently, fulfilling the contract of a UNO component regarding thread-safeness is
#tedious work, because normally each involved object has to acquire and release a mutex on method entry and exit, respectively
#almost impossible to get right, let alone verified to work correctly (no races, no deadlocks), because of the sheer mass of involved objects and mutices (the number of distinct states that would have to be checked for a proper verification is intractable for anything but the most trivial examples). The upcoming [[Uno/Effort/Binary/Extend Threading-Model|extended Binary Uno threading-model]] makes thread-safeness transparent, by automatically locking and unlocking when entering or exiting components on a much coarser level than single methods.

*Make other mundane stuff transparent. Like memory management (via garbage collection, or refcounting via [http://www.boost.org/libs/smart_ptr/index.html smart ptrs], [http://api.openoffice.org/docs/DevelopersGuide/ProfUNO/ProfUNO.htm#1+4+2+7+3+Mapping+of+Interface UNO reference]), or [http://en.wikipedia.org/wiki/Transaction_processing transactionality] (the mode of making changes take place either completely, or not at all. Having a component behave in a non-transactional way in the face of an error makes recovery rather hard. There's more to transactionality than exception-safeness. Imagine two users collaborating on the same document).

==General Refactoring Improvements==
For many reasons the OpenOffice.org codebase is difficult to understand and navigate. On of the reasons is a lack of cleanup in the code. There is a never ending list of things that ought to be done-- add some of your own.

*Actually remove deprecated things. Things like String and [http://go-oo.org/lxr/ident?i=UniString UniString] need to go. svtools and tools have loads of stuff that is duplicated elsewhere or is deprecated. Getting rid of these sorts of things will make maintaining application code much easier.

*Document things. Some of the code has comments that at one time were correct. Some code has German comments. While most of the OpenOffice.org programmers sind Deutschschprachig, there is an unofficial understanding that German comments mean "don't touch."

==Code Improvements==
===Remove unused code===
Binary Loading/Saving stuff in ItemSets, depend on EditEngine Loading/Saving (only used for Clipboard) - MT

===Remove duplicate code===
Consolidate slightly copied and modified code.
* BigPointerArray vs. SvPointerArray
* RTL Strings with Tools Strings

Consolidate Text Engines
* Text Engine
* Writer Engine
* Edit Engine

===Replace code with 3rd party===
Replace self made containers with STL containers.
* Tools Container,
* SvPointerArray ([http://www.openoffice.org/issues/show_bug.cgi?id=112395 Issue 112395]),
* BigPointerArray,
* "GetPos" is mostly used wrong -> remove it (algorithmic complexity to hight O(n*n))

===Improve modularity===
?Clear "Mission Statements" for modules?

===[[VCL]]===
get rid of internal event queue.

==Framework Improvements==

The framework module already has a very modular architecture solely based on UNO components. Amongst others, it manages menus and toolbars, but it does not manage docked windows like e.g. navigator or impress task pane. These windows are still managed in sfx2 and their implementations are based on sfx2 classes. No non-sfx2 based module can use them.

Here's the roadmap:

* add a LayoutManager for DockingWindows to the framework module that works in the same way as the LayoutManager for toolbars
* implement docking handlers for the windows managed by this LayoutManager in the same way as for the toolbars
* provide factories for the sfx2 based implementations of Docking Windows
* simplify the frame classes in sfx2; without the sfx internal layout manager for DockingWindows only one "frame" class is necessary
* put the current container windows inside of task windows managed by a Task service (later they might become tabs in a tab bar)
* move the LayoutManager from the frame to the task (or add some "super manager") so that frames can share their tools

Amongst others this will allow to have more than one view to one ("split view") or several documents in one system task window.

===Status Quo===

The new LayoutManager and the docking handlers are already worked on and nearly finished. Next step will be the mentioned factories. There also is a prototype for a task window and a task service that can be adjusted to our needs. The biggest challenge currently is the "super manager".

==Application-specific Improvements==
One of the lingering problems on the application level is the fact that, in spite of modularized lower-level functionality, application functionality cannot be shared ''between'' OOo's applications (except via embedding of a whole application (OLE)). This is because for neither Calc nor Writer, there are reusable application engines, like a text engine providing text editing and layouting functionality, or a table engine providing formula and calculation support. Draw/Impress already uses a shared engine, dubbed 'Drawing Layer'. But there's still considerable functionality hidden in the application code, which is worth extracting. Especially the missing Writer engine manifests itself in duplicated text editing functionality in EditEngine and TextEngine (used by Impress and Calc for their corresponding text functionality).

<div name="Example" class="boilerplate metadata" id="example" style="background-color: #fee; margin: 0 1em; padding: 0 10px; border: 1px solid #aaa;">
'''Example 1'''

The Writer uses a different implementation when displaying pictures, opposed to Draw/Impress. Thus, if you insert a picture into a writer document, you have a different feature set available as in Draw/Impress or Calc. For example, the Writer graphic object is able to render a variety of border styles, but at the same time, is unable to rotate the picture. To have rotated pictures in Writer, one has to insert that picture in a Draw document, copy the resulting drawing layer object, and paste that into Writer.
</div>

<p>

<div name="Example" class="boilerplate metadata" id="example" style="background-color: #fee; margin: 0 1em; padding: 0 10px; border: 1px solid #aaa;">
'''Example 2'''

The Draw/Impress applications use a different implementation for displaying text, as opposed to the Writer. Thus, if you insert a text shape in Impress, you can't have two-column layout with it, nor does it provide change tracking ('redlining'). On the other hand, the Writer's fly frames, which superficially perform the same task as the Impress text shape, cannot be rotated.
</div>

Another area of improvement is rendering. Currently, all application's graphical output is based on the OutputDevice class, which provides only very basic rendering facilities (in fact, besides largely extended text output functionality (to handle OOo's i18n requirements), this interface has basically remained unchanged for a long time). Specifically, things like performant alpha compositing or anti-aliased geometry rendering are extremely hard to achieve with the current design. Therefore, starting with OOo 2.0, the [http://api.openoffice.org/docs/common/ref/com/sun/star/rendering/XCanvas.html XCanvas] interface is slated to gradually replace OutputDevice in all applications.

===Writer===

*break up the monolith
*make the import filters more modular
*port rendering to XCanvas

===Calc===
See [[Calc/To-Dos]]

===Draw/Impress===

*break up the monolith
*become more decoupled from sfx2
*redesign API ([[Impress_Performance | performance]])

*port Drawing Layer to XCanvas (see [[DrawingPrimitives]] for one of the preconditions)

*Allow slides to inherit animations from the master slide

Keyboard Shortcuts Specification Guidelines

2010-06-24T08:22:30Z

Gang65: /* Useful links */

<div style="float:left; width:100px:">
= Scope =

This page gives some hints for specifying new keyboard shortcuts.
The addressees are UX people, developers, QA people and all those who contribute in an I-Team to the redaction of a specification.

'''WARNING''': most of the time it will not be possible to fulfill all requirements at the same time but the specification of a shortcut should have reviewed ALL requirements and note the known conflicts, technical gaps.

'''Possible conflicts and influence areas around keyboard shortcuts'''

[[image:Shortcutcloud.jpg]]

= How to choose a shortcut =
== The "mnemonic effect" ==
Take, if possible, the first letter of the function name ('''C'''opy, '''O'''pen...) or a letter which "brands" this name (e'''X'''ecute, po'''W'''er)

== Interoperability & Integration ==
What do competitors or the operating systems use when they have the same function?

= Possible Conflicts and Influence Areas =

== Internal Consistency ==

Take care about the consistency of a shortcut across every OOo applications which share the same functions.

if a function exists in Writer, Calc, Impress, it should have the same shortcut.

Have a look at "Tools - Customize - Shortcuts" for every application to compare the mapping, see what is in use and is not.

But don't trust blindly this dialog! Some shortcuts are unfortunately hard coded and don't appear there! *Try* the shortcut in the application.

== External Consistency ==
=== Interoperability ===

Take care about the consistency of the shortcut vs competitors' similar applications and functions.

=== Integration ===

Take care about the consistency of the shortcut vs "standard" operating systems'/window managers' shortcut with similar functions.

Think *multi platform*: Linux (KDE, Gnome...), Solaris, Windows, MAC (cmd vs. ctrl)
Avoid collisions with system shortcuts

== Localization ==

Some shortcuts have been localized (See: http://specs.openoffice.org/g11n/menus/LocalizedShortcuts.sxw).

Respect the existing localization before moving any existing shortcut or even creating new ones by analogy (with the existing English terms).

Ex: provided a new function "Open Document Read-Only".

It could be smart to think about Ctrl+Shift+O by analogy with Ctrl+O.

This is good but not enough... Think about the Localization and check that e.g. in Spanish "Open" is "Abrir" hence "Ctrl+A" so that it might be clever to localize to Ctrl+Shift+A...

== Useful links ==
* [http://developer.kde.org/documentation/standards/kde/style/keys/shortcuts.html KDE Standard shortcuts]
* [http://msdn.microsoft.com/en-us/library/bb545460.aspx Guideline for user interaction with your MS Win applications]
* [http://support.apple.com/kb/HT1343 Mac OS X keyboard shortcuts]
* [http://www.novell.com/coolsolutions/tip/2289.html Gnome / KDE Keyboard Shortcuts]

</div>
[[Category:Specification Guidelines]][[Category:Specification]][[Category:Shortcut]]

Keyboard Shortcuts Specification Guidelines

2010-06-24T08:20:13Z

Gang65: /* Useful links */

<div style="float:left; width:100px:">
= Scope =

This page gives some hints for specifying new keyboard shortcuts.
The addressees are UX people, developers, QA people and all those who contribute in an I-Team to the redaction of a specification.

'''WARNING''': most of the time it will not be possible to fulfill all requirements at the same time but the specification of a shortcut should have reviewed ALL requirements and note the known conflicts, technical gaps.

'''Possible conflicts and influence areas around keyboard shortcuts'''

[[image:Shortcutcloud.jpg]]

= How to choose a shortcut =
== The "mnemonic effect" ==
Take, if possible, the first letter of the function name ('''C'''opy, '''O'''pen...) or a letter which "brands" this name (e'''X'''ecute, po'''W'''er)

== Interoperability & Integration ==
What do competitors or the operating systems use when they have the same function?

= Possible Conflicts and Influence Areas =

== Internal Consistency ==

Take care about the consistency of a shortcut across every OOo applications which share the same functions.

if a function exists in Writer, Calc, Impress, it should have the same shortcut.

Have a look at "Tools - Customize - Shortcuts" for every application to compare the mapping, see what is in use and is not.

But don't trust blindly this dialog! Some shortcuts are unfortunately hard coded and don't appear there! *Try* the shortcut in the application.

== External Consistency ==
=== Interoperability ===

Take care about the consistency of the shortcut vs competitors' similar applications and functions.

=== Integration ===

Take care about the consistency of the shortcut vs "standard" operating systems'/window managers' shortcut with similar functions.

Think *multi platform*: Linux (KDE, Gnome...), Solaris, Windows, MAC (cmd vs. ctrl)
Avoid collisions with system shortcuts

== Localization ==

Some shortcuts have been localized (See: http://specs.openoffice.org/g11n/menus/LocalizedShortcuts.sxw).

Respect the existing localization before moving any existing shortcut or even creating new ones by analogy (with the existing English terms).

Ex: provided a new function "Open Document Read-Only".

It could be smart to think about Ctrl+Shift+O by analogy with Ctrl+O.

This is good but not enough... Think about the Localization and check that e.g. in Spanish "Open" is "Abrir" hence "Ctrl+A" so that it might be clever to localize to Ctrl+Shift+A...

== Useful links ==
* [http://developer.kde.org/documentation/standards/kde/style/keys/shortcuts.html KDE Standard shortcuts]
* [http://msdn.microsoft.com/en-us/library/bb545460.aspx How to create shortcuts for MS Windows applications]
* [http://support.apple.com/kb/HT1343 Mac OS X keyboard shortcuts]
* [http://www.novell.com/coolsolutions/tip/2289.html Gnome / KDE Keyboard Shortcuts]

</div>
[[Category:Specification Guidelines]][[Category:Specification]][[Category:Shortcut]]

Keyboard Shortcuts Specification Guidelines

2010-06-24T08:19:42Z

Gang65:

<div style="float:left; width:100px:">
= Scope =

This page gives some hints for specifying new keyboard shortcuts.
The addressees are UX people, developers, QA people and all those who contribute in an I-Team to the redaction of a specification.

'''WARNING''': most of the time it will not be possible to fulfill all requirements at the same time but the specification of a shortcut should have reviewed ALL requirements and note the known conflicts, technical gaps.

'''Possible conflicts and influence areas around keyboard shortcuts'''

[[image:Shortcutcloud.jpg]]

= How to choose a shortcut =
== The "mnemonic effect" ==
Take, if possible, the first letter of the function name ('''C'''opy, '''O'''pen...) or a letter which "brands" this name (e'''X'''ecute, po'''W'''er)

== Interoperability & Integration ==
What do competitors or the operating systems use when they have the same function?

= Possible Conflicts and Influence Areas =

== Internal Consistency ==

Take care about the consistency of a shortcut across every OOo applications which share the same functions.

if a function exists in Writer, Calc, Impress, it should have the same shortcut.

Have a look at "Tools - Customize - Shortcuts" for every application to compare the mapping, see what is in use and is not.

But don't trust blindly this dialog! Some shortcuts are unfortunately hard coded and don't appear there! *Try* the shortcut in the application.

== External Consistency ==
=== Interoperability ===

Take care about the consistency of the shortcut vs competitors' similar applications and functions.

=== Integration ===

Take care about the consistency of the shortcut vs "standard" operating systems'/window managers' shortcut with similar functions.

Think *multi platform*: Linux (KDE, Gnome...), Solaris, Windows, MAC (cmd vs. ctrl)
Avoid collisions with system shortcuts

== Localization ==

Some shortcuts have been localized (See: http://specs.openoffice.org/g11n/menus/LocalizedShortcuts.sxw).

Respect the existing localization before moving any existing shortcut or even creating new ones by analogy (with the existing English terms).

Ex: provided a new function "Open Document Read-Only".

It could be smart to think about Ctrl+Shift+O by analogy with Ctrl+O.

This is good but not enough... Think about the Localization and check that e.g. in Spanish "Open" is "Abrir" hence "Ctrl+A" so that it might be clever to localize to Ctrl+Shift+A...

== Useful links ==
* [http://developer.kde.org/documentation/standards/kde/style/keys/shortcuts.html KDE Standard shortcuts]
* [http://msdn.microsoft.com/en-us/library/bb545460.aspx How to create shortcuts for MS Windows applications]
* [http://support.apple.com/kb/HT1343 - Mac OS X keyboard shortcuts]
* [http://www.novell.com/coolsolutions/tip/2289.html Gnome / KDE Keyboard Shortcuts]

</div>
[[Category:Specification Guidelines]][[Category:Specification]][[Category:Shortcut]]

ReleaseSchedule

2010-06-17T12:53:44Z

Gang65:

=OpenOffice.org release roadmap=

[[OOoRelease33 | OpenOffice.org 3.3]] : June 2010
[[OOoRelease331 | OpenOffice.org 3.3.1]] : September 2010
[[OOoRelease34 | OpenOffice.org 3.4]] : December 2010
[[OOoRelease341 | OpenOffice.org 3.4.1]] : March 2011

{{OOo Releases}}

[[Category:Releases]]

Ubuntu Build Instructions

2010-06-08T17:41:04Z

Gang65: /* Ubuntu 9.10 Karmic Koala */

{{Documentation/Building Guide TOC
|ShowNextPage=none
|ShowPrevPage=none
}}
{{Documentation/Note|Please add only Ubuntu-specifics here! Use the information on the [[Development/OpenOffice.org Building Guide/Building on Linux|Building Guide]] and only fall back to this document if you need help with Ubuntu-specifics (like package names).}}
== Ubuntu 9.10 Karmic Koala and Ubuntu 10.04 Lucid Lynx==

To build you need the following packages:
<pre>
sudo apt-get install g++ gcc bison flex libarchive-zip-perl libcups2-dev libpam0g-dev subversion \
sun-java6-jdk gperf libfreetype6-dev libxaw7-dev libfontconfig1-dev libxrandr-dev patch \
libgconf2-dev libgnomevfs2-dev ant python-dev libgtk2.0-dev ccache libgraphite-dev \
libwpd8-dev libxslt-dev libdb4.7-dev libneon27-dev libhunspell-dev libaltlinuxhyph-dev
</pre>
or use this url:
<pre>
apt:g++,gcc,bison,flex,libarchive-zip-perl,libcups2-dev,libpam0g-dev,subversion,sun-java6-jdk,gperf,libfreetype6-dev,libxaw7-dev,libfontconfig1-dev,libxrandr-dev,patch,libgconf2-dev,libgnomevfs2-dev,ant,python-dev,libgtk2.0-dev,ccache,libgraphite-dev,libwpd8-dev,libxslt-dev,libdb4.7-dev,libneon27-dev,libhunspell-dev,libaltlinuxhyph-dev
</pre>

then follow the '''[[Documentation/Building Guide|Building Guide]]''' to continue.

==See also==
*[[Building]]
*[[Debug Build Problems]]

[[Category: Distribution-Specific Build Instructions]]

Documentation/Building Guide/Building on Linux

2010-06-08T17:38:18Z

Gang65: /* configure */

{{Documentation/Building Guide TOC
|ShowNextPage=none
|ShowPrevPage=none
}}
{{DISPLAYTITLE:Building on Linux}}

__TOC__
= Overview =
{{Template:Documentation/Note|<code>$SRC_ROOT</code> will denote the directory in which the source code of OpenOffice.org is stored.}}
{{Template:Documentation/Tip|You are advised to check the release notes for the release you are building to inform yourself about changes since previous releases.}}

= Requirements =
== hardware requirements ==

* 1 or more reasonable fast CPUs, x-way CPU's recommended.

* 1 GB Ram ( 2 GB recommended )

* at least 10 GB free disk space

== software requirements ==

{{Template:Documentation/Tip|You can find distribution specific package lists in the [[:Category:Distribution-Specific_Build_Instructions|Distribution specific build instructions pages]].}}

* glibc:
** for OOo<=3.1: 2.2.x or higher
** for OOo>3.1: 2.3.2 or higher

* C/C++ Compiler:
** gcc >= 3.3
** gcc 4.2.3 is the current reference compiler

* The X11 development libraries and header files<ref name="Foot1">{{Template:Documentation/Note|Should be in place with most Linux distributions. Note the there are currently some issues with X version 4.3.}}</ref>

* PAM including the development headers<ref name="Foot2">{{Template:Documentation/Note|PAM should be installed by default on most linux distributions. You should only need to add the development package.}}</ref>

* bash<ref name="Foot3">{{Template:Documentation/Note|You can also (still?) use tcsh instead of bash, but bash is installed almost everywhere anyway. It is possible to use bash or tcsh as shell. This is switched with the <CODE>--with-use-shell</CODE> configure switch.}}</ref>.

* gtk2 and libtiff including the development headers<ref name="Foot4">{{Template:Documentation/Note|The gtk2, jpeg and tiff libraries are not required if you disable the crash-reporter when running <CODE>./configure</CODE>.}}
</ref>

= Full Builds =

To perform a full build, you need to follow these steps:

== configure ==
* Run the <code>configure</code> script to check all requirements. Run the following command to view all possible options.

./configure --help

An example configure command:
./configure --with-use-shell=bash --disable-mozilla --without-junit --disable-odk

See the last information box in the configure script or [[:Category:Distribution-Specific_Build_Instructions]] for more information for your platform.

{{Documentation/Caution| Please check for any warnings emitted by the configure-script. The page [[OpenSolaris Build Instructions/Configure Errors]] may be helpful in debugging all the dependencies.}}

== bootstrap ==
When configure finished successfully, run:

./bootstrap

to create the dmake executable required to build OpenOffice.org.

== setting the environment ==

When the configure script has been run successfully a file <code>LinuxX86Env.Set.sh</code> or <code>LinuxX86-64Env.Set.sh</code> was created<ref name="Foot5">{{Template:Documentation/Note|When you want to use tcsh instead of bash, you will need to use the file <code>LinuxX86Env.Set</code> instead:<br>
<pre> source LinuxX86Env.Set
rehash</pre>
If you do not use tcsh, it is better to delete that file, as it will get in the way for tab-completion sooner or later.}}
</ref>.
Do this:

source LinuxX86Env.Set.sh

or

source LinuxX86-64Env.Set.sh

to set up the environment for the build<ref name="Foot6">By default, native packages (.deb/.rpm) will be build.<br>
{{Template:Documentation/Tip|If you want to have something faster and easier to test:<br>
<pre>export FORCE2ARCHIVE=true</pre>
This will create a tarball that can easily be unpacked and run anywhere.}}
</ref>.

== starting the build ==
Build the software by typing the following in <code>$SRC_ROOT</code><ref name="Foot7">{{Template:Documentation/Note|You can also run:<br>
<pre>make</pre>
but GNU make will just start build.pl.
For details run:<br>
<pre>build --help</pre>}}
</ref>:
cd instsetoo_native && build --all
The building procedure will take at least an hour (on a 3 GHz Quad-Core with 8GB RAM without CCACHE).

= Partial Builds =
There are two ways to do partial builds:
* compatible
* incompatible
Only do compatible partial builds if you know exactly what you are doing.
{{Documentation/Note|For more information, see [[Compatible Builds]].}}
== rebuilding from a module (incompatible build) ==

If you decide to change a module in an incompatible way, you will need to rebuild all modules depending on it (directly or indirectly):

cd $SRC_ROOT/instsetoo_native
build --from $INCOMPATIPLEMODULE --prepare
build --from $INCOMPATIBLEMODULE

== rebuilding a module (compatible build) ==

To rebuild a module you can delete all output directories with, rebuild and redeliver into the solver with:

cd $MODULE
build --from $MODULE --prepare
build && deliver

A simple <code>build</code> in <code>$SRC_ROOT/instsetoo_native</code> will recreate the installation sets, provided all other modules have already been build.<ref name="Foot8">{{Documentation/Caution|<code>build --all</code> would rebuild changed/missing files. However, it does not check for incompatible modules. If unsure, use <code>build --from --prepare</code>.}}
</ref>

{{Documentation/Caution|This does '''not''' check for incompatible modules. If unsure, use an incompatible build (see above).}}

= Building a Module with Debug Information =

To rebuild a module with debug information and additional assertions and checks, run:

cd $MODULE
build --from $MODULE --prepare # removes old output trees and solver
build debug=true --from $MODULE

Drop the newly created binaries into an existing installation. Building an installation set with them will not help, as binaries are stripped on packing by default.

{{Template:Documentation/Tip|For details, see [[Debugging]].}}

= Finding Installation Sets =

The english installation set will be located at <code>$SRC_ROOT/instsetoo_native/unxlngi6.pro/OpenOffice/{deb,rpm,archive}/install/en-US/</code><ref name="Foot9">The en-US in the path names indicates that the localization is American English. This value corresponds to the language tags defined by RFC 1766 (Tags for the Identification of Languages). The German installation set will be located in a <tt>de</tt> subdirectory. This scheme holds true for all localizations you may have chosen explicitly.

{{Template:Documentation/Tip|Running the configure script with the --with-lang option will introduce the build of additional language resources. This switch accepts one or more RFC 1766 language tags as arguments. Check the value of the <code>completelangiso</code> macro in <code>$SRC_ROOT/solenv/inc/postset.mk</code> for all the currently supported language tags.<br>
Example:<br>
<pre>./configure --with-lang="de fr"</pre>
This enables the build of the localized German and French version. The environment variable <code>WITH_LANG</code> will then contain the language tags of the additional (en-US will always be build)
languages.}}

{{Template:Documentation/Note|If you build additional localized languages it is possible to generate Language Packs that contain only the changes needed to add the additional language to an OpenOffice.org of a different language. The following commands will generate language packs languages that were specified with the --with-lang switch during the configure phase. <br>
<pre>cd $SRC_ROOT/instsetoo_native/util
dmake ooolanguagepack</pre>}}
{{Template:Documentation/Caution|Note that you can only build the language packs '''after''' you have build the complete office with all selected languages.}}
</ref>.

{{Template:Documentation/Note| For 64-bit Linux it is <code>unxlngx6.pro</code> instead of <code>unxlngi6.pro</code>.}}

= Tips And Tricks =
== ccache ==

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 100000
export CXX="ccache g++"
export CC="ccache gcc"

== dependencies ==

'''nodep'''

If you set the environment variable <code>nodep</code> to <code>TRUE</code>, then dependency information files are not created - the build finishes faster.

{{Template:Documentation/Caution|But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.}}

'''NO_HIDS'''

Similar to the <code>nodep</code> variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile (directory) level, the other one on the global level. The two levels of parallelism result from the two-step build procedure in the OOo build environment. The build script runs through all the directories it reads from the build.lst files in all modules and calls dmake for every directory.

'''parallelism on the global level'''

For parallelism on the global level, you have to run build from <code>$SRC_ROOT>/instsetoo_native</code> with the <code>-P<number></code> switch, for example:
<pre>
build -P2
</pre>

This takes build how many dmake processes it is allowd to start in parallel.

'''parallelism on the directory level'''

export MAXPROCESS=<numer or processes>

This tells dmake how many targets it is allowed to build in parallel. When you don't use build.pl but build a single directory (single makefile), you can achieve the same with

<pre>
dmake -P2
</pre>

'''combining both levels'''

If you want to have parallelism on both levels, you can call

<pre>
build -P2 -- -P2
</pre>

"--" is a special build.pl parameter that passes every further parameters to the dmake processes it starts.

''' Recommendation '''

Experience tells that using the doubled number of cores in your machine is a good choice, using more threads does not make a big difference, except if the combined option is chosen. So even on single core machines using two threads will speed up the build considerably.

== create prebuilt mozilla ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed).
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources
* use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{platform}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla).
= See Also =
* [[:Category:Distribution-Specific Build Instructions]]
* [[Prepared Build Images]]

----

<references/>

{{PDL1}}
[[Category:Linux]]

DerivedWorks

2010-06-08T09:43:35Z

Gang65:

[This page is in serious need of updating. Then again, it's been somewhat superseded by the Solutions page.]

This page will track derivatives of OpenOffice.org. Feel free to add to it if you know of any, and please include URLs. A derived work listed here could be free or proprietary, and should not be limited to language or platform. It may include those works that use OpenOffice.org in part or in whole. As well, a separate section could also track distributions, e.g., by Novell or Debian or Ubuntu. We are listing these mainly to track them and not for advertising purposes. Some of the companies listed below may no longer be producing derivatives of OpenOffice.org, as the license for the source changed in 2005, with 2.0, when we dropped the [http://www.openoffice.org/license.html SISSL] and moved to using the LGPL exclusively.

== Preliminary List ==

{| border=1 cellspacing=0 cellpadding=3
!Product name
!Company
!Windows
!Mac OS X
!Linux
!Solaris
!License
!Web Site
!Wikipedia
|-
|ChinaOffice
|GoldSoft
|X
|
|X
|
|proprietary
|http://www.goldsoft.net/
|
|-
|Co-Create Office
|Co-Create
|
|
|X
|
|Free
|http://www.ccoss.com.cn/
|
|-
|EuroOffice 2005
|Multiráció Kft.
|X
|
|X
|
|proprietary
|http://www.eurooffice2005.com/
|
|-
|KaiOffice
|KaiSource
|X
|
|
|
|proprietary
|http://www.kaisource.com/
|
|-
|MagyarOffice
|Multiráció Kft.
|X
|
|X
|X
|proprietary
|http://www.magyaroffice.hu/
|
|-
|MultiMedia Office
|Platasoft
|X
|
|X
|X
|LGPL/proprietary
|http://www.platasoft.com/
|
|-
|MYOffice 2007
|OASYS
|X
|
|
|
|proprietary
|http://www.oasys.com.my/
|
|-
|NeoOffice
|NeoOffice.org
|
|X
|
|
|GPL
|http://neooffice.org/
|
|-
|NextOffice
|Well Develop
|X
|
|
|
|proprietary
|http://www.nextoffice.net/
|
|-
|OfficeOne
|?
|X
|
|
|
|proprietary
|http://shop.avanquest.com/france/produits/prod.php?pid=120/
|
|-
|OfficeTLE
|?
|X
|
|
|
|proprietary
|http://www.thaisoftware.co.th/index.php?tpid=pro:AR-0028
|
|-
|OpenOfficePL
|OpenOffice Software
|X
|X
|X
|
|proprietary
|http://www.openoffice.com.pl/index.php?id=201
|
|-
|OpenOffice.ux.pl
|Ux Systems
|X
|
|X
|
|LGPL/proprietary
|http://www.ux.pl/openoffice/
|
|-
|OpenOfficeT7
|Top7
|X
|
|
|
|?
|http://www.openzone.pl/
|
|-
|[[Oracle Open Office]]
|Oracle
|X
|
|X
|X
|proprietary
|http://www.oracle.com/us/products/applications/open-office/index.html
|http://en.wikipedia.org/wiki/Oracle_Open_Office
|-
|OxygenOffice Professional
|OxygenOffice Professional
|X
|
|X
|
|LGPL
|http://ooop.sf.net/
|
|-
|RedOffice
|Red Flag 2000
|X
|
|X
|
|proprietary
|http://www.redoffice.com/
|
|-
|SunShine Office
|CS2C
|
|
|X
|
|?
|http://www.cs2c.com.cn/
|
|-
|ThizOffice
|ThizTech
|X
|
|X
|
|?
|http://www.thizlinux.com.cn/
|
|-
|UP Office
|Philippines University
|1.0
|
|2.0
|
|?
|http://os.up.edu.ph/modules.php?name=Downloads&d_op=viewdownload&cid=2
|
|
|-
|Workplace
|IBM
|X
|
|X
|
|proprietary
|[workplacehome|http://www-142.ibm.com/software/workplace/products/product5.nsf/wdocs/workplacehome
|
|-
|WPS Office
|KingSoft
|X
|
|
|
|proprietary
|http://www.wps.com.cn/
|
|-
|602Office
|Software602
|
|
|
|
|?
|http://www.602.cz/cz/produkty/602office_2_2/
|http://cs.wikipedia.org/wiki/602Office
|
|-
|Jambo OpenOffice
|
|
|
|
|
|?
|http://www.o.ne.tz/
|http://en.wikipedia.org/wiki/Jambo_OpenOffice
|
|-
|RomanianOffice
|
|
|
|
|
|?
|http://www.romanianoffice.ro/
|http://en.wikipedia.org/wiki/RomanianOffice
|
|-
|Go-OO
|Novell
|X
|
|X
|
|LGPL
|http://go-oo.org/
|
|}

[[Category:Redoffice]]

DerivedWorks

2010-06-08T09:41:44Z

Gang65: /* Preliminary List */

[This page is in serious need of updating. Then again, it's been somewhat superseded by the Solutions page.]

This page will track derivatives of OpenOffice.org. Feel free to add to it if you know of any, and please include URLs. A derived work listed here could be free or proprietary, and should not be limited to language or platform. It may include those works that use OpenOffice.org in part or in whole. As well, a separate section could also track distributions, e.g., by Novell or Debian or Ubuntu. We are listing these mainly to track them and not for advertising purposes. Some of the companies listed below may no longer be producing derivatives of OpenOffice.org, as the license for the source changed in 2005, with 2.0, when we dropped the [http://www.openoffice.org/license.html SISSL] and moved to using the LGPL exclusively.

== Preliminary List ==

{| border=1 cellspacing=0 cellpadding=3
!Product name
!Company
!Windows
!Mac OS X
!Linux
!Solaris
!License
!Web Site
!Wikipedia
|-
|ChinaOffice
|GoldSoft
|X
|
|X
|
|proprietary
|http://www.goldsoft.net/
|
|-
|Co-Create Office
|Co-Create
|
|
|X
|
|Free
|http://www.ccoss.com.cn/
|
|-
|EuroOffice 2005
|Multiráció Kft.
|X
|
|X
|
|proprietary
|http://www.eurooffice2005.com/
|
|-
|KaiOffice
|KaiSource
|X
|
|
|
|proprietary
|http://www.kaisource.com/
|
|-
|MagyarOffice
|Multiráció Kft.
|X
|
|X
|X
|proprietary
|http://www.magyaroffice.hu/
|
|-
|MultiMedia Office
|Platasoft
|X
|
|X
|X
|LGPL/proprietary
|http://www.platasoft.com/
|
|-
|MYOffice 2007
|OASYS
|X
|
|
|
|proprietary
|http://www.oasys.com.my/
|
|-
|NeoOffice
|NeoOffice.org
|
|X
|
|
|GPL
|http://neooffice.org/
|
|-
|NextOffice
|Well Develop
|X
|
|
|
|proprietary
|http://www.nextoffice.net/
|
|-
|OfficeOne
|?
|X
|
|
|
|proprietary
|http://shop.avanquest.com/france/produits/prod.php?pid=120/
|
|-
|OfficeTLE
|?
|X
|
|
|
|proprietary
|http://www.thaisoftware.co.th/index.php?tpid=pro:AR-0028
|
|-
|OpenOfficePL
|OpenOffice Software
|X
|X
|X
|
|proprietary
|http://www.openoffice.com.pl/index.php?id=201
|
|-
|OpenOffice.ux.pl
|Ux Systems
|X
|
|X
|
|LGPL/proprietary
|http://www.ux.pl/openoffice/
|
|-
|OpenOfficeT7
|Top7
|X
|
|
|
|?
|http://www.openzone.pl/
|
|-
|[[Oracle Open Office]]
|Oracle
|X
|
|X
|X
|proprietary
|http://www.oracle.com/us/products/applications/open-office/index.html
|http://en.wikipedia.org/wiki/Oracle_Open_Office
|-
|OxygenOffice Professional
|OxygenOffice Professional
|X
|
|X
|
|LGPL
|http://ooop.sf.net/
|
|-
|Pladao Office
|?
|X
|
|X
|X
|LGPL
|http://pladao.org/index.php?newlang=english
|
|-
|RedOffice
|Red Flag 2000
|X
|
|X
|
|proprietary
|http://www.redoffice.com/
|
|-
|SunShine Office
|CS2C
|
|
|X
|
|?
|http://www.cs2c.com.cn/
|
|-
|ThizOffice
|ThizTech
|X
|
|X
|
|?
|http://www.thizlinux.com.cn/
|
|-
|UP Office
|Philippines University
|1.0
|
|2.0
|
|?
|http://os.up.edu.ph/modules.php?name=Downloads&d_op=viewdownload&cid=2
|
|
|-
|Workplace
|IBM
|X
|
|X
|
|proprietary
|[workplacehome|http://www-142.ibm.com/software/workplace/products/product5.nsf/wdocs/workplacehome
|
|-
|WPS Office
|KingSoft
|X
|
|
|
|proprietary
|http://www.wps.com.cn/
|
|-
|602Office
|Software602
|
|
|
|
|?
|http://www.602.cz/cz/produkty/602office_2_2/
|http://cs.wikipedia.org/wiki/602Office
|
|-
|Jambo OpenOffice
|
|
|
|
|
|?
|http://www.o.ne.tz/
|http://en.wikipedia.org/wiki/Jambo_OpenOffice
|
|-
|RomanianOffice
|
|
|
|
|
|?
|http://www.romanianoffice.ro/
|http://en.wikipedia.org/wiki/RomanianOffice
|
|-
|Go-OO
|Novell
|X
|
|X
|
|LGPL
|http://go-oo.org/
|
|}

[[Category:Redoffice]]

Oracle Open Office

2010-06-08T09:27:39Z

Gang65:

[http://www.oracle.com/us/products/applications/open-office/index.html Oracle Open Office] (known before 2010 as [http://www.sun.com/software/star/staroffice/index.jsp StarOffice]) is a [http://www.oracle.com Oracle] proprietary office suite based on [[OpenOffice.org]].

See [http://en.wikipedia.org/wiki/Oracle_Open_Office the Wikipedia entry].
[[Category:Term]]

Oracle Open Office

2010-06-08T09:26:51Z

Gang65:

StarOffice

2010-06-08T09:25:28Z

Gang65: moved StarOffice to Oracle Open Office: Change the name of StarOffice

#REDIRECT [[Oracle Open Office]]

Oracle Open Office

2010-06-08T09:25:28Z

Gang65: moved StarOffice to Oracle Open Office: Change the name of StarOffice

[http://www.sun.com/software/star/staroffice/index.jsp StarOffice] is a [http://www.sun.com Sun Microsystems] proprietary office suite based on [[OpenOffice.org]].

See [http://en.wikipedia.org/wiki/StarOffice the Wikipedia entry].
[[Category:Term]]

DerivedWorks

2010-06-08T09:24:04Z

Gang65:

[This page is in serious need of updating. Then again, it's been somewhat superseded by the Solutions page.]

This page will track derivatives of OpenOffice.org. Feel free to add to it if you know of any, and please include URLs. A derived work listed here could be free or proprietary, and should not be limited to language or platform. It may include those works that use OpenOffice.org in part or in whole. As well, a separate section could also track distributions, e.g., by Novell or Debian or Ubuntu. We are listing these mainly to track them and not for advertising purposes. Some of the companies listed below may no longer be producing derivatives of OpenOffice.org, as the license for the source changed in 2005, with 2.0, when we dropped the [http://www.openoffice.org/license.html SISSL] and moved to using the LGPL exclusively.

== Preliminary List ==

{| border=1 cellspacing=0 cellpadding=3
!Product name
!Company
!Windows
!Mac OS X
!Linux
!Solaris
!License
!Web Site
!Wikipedia
|-
|ChinaOffice
|GoldSoft
|X
|
|X
|
|proprietary
|http://www.goldsoft.net/
|
|-
|Co-Create Office
|Co-Create
|
|
|X
|
|Free
|http://www.ccoss.com.cn/
|
|-
|EuroOffice 2005
|Multiráció Kft.
|X
|
|X
|
|proprietary
|http://www.eurooffice2005.com/
|
|-
|KaiOffice
|KaiSource
|X
|
|
|
|proprietary
|http://www.kaisource.com/
|
|-
|Lycoris
|Lycoris (now Mandriva)
|
|
|X
|
|?
|http://www.lycoris.com/products/ppak/ (broken)
|
|-
|MagyarOffice
|Multiráció Kft.
|X
|
|X
|X
|proprietary
|http://www.magyaroffice.hu/
|
|-
|MultiMedia Office
|Platasoft
|X
|
|X
|X
|LGPL/proprietary
|http://www.platasoft.com/
|
|-
|MYOffice 2007
|OASYS
|X
|
|
|
|proprietary
|http://www.oasys.com.my/
|
|-
|NeoOffice
|NeoOffice.org
|
|X
|
|
|GPL
|http://neooffice.org/
|
|-
|NextOffice
|Well Develop
|X
|
|
|
|proprietary
|http://www.nextoffice.net/
|
|-
|OfficeOne
|?
|X
|
|
|
|proprietary
|http://shop.avanquest.com/france/produits/prod.php?pid=120/
|
|-
|OfficeTLE
|?
|X
|
|
|
|proprietary
|http://www.thaisoftware.co.th/index.php?tpid=pro:AR-0028
|
|-
|OpenOfficePL
|OpenOffice Software
|X
|X
|X
|
|proprietary
|http://www.openoffice.com.pl/index.php?id=201
|
|-
|OpenOffice.ux.pl
|Ux Systems
|X
|
|X
|
|LGPL/proprietary
|http://www.ux.pl/openoffice/
|
|-
|OpenOfficeT7
|Top7
|X
|
|
|
|?
|http://www.openzone.pl/
|
|-
|[[Oracle Open Office]]
|Oracle
|X
|
|X
|X
|proprietary
|http://www.oracle.com/us/products/applications/open-office/index.html
|http://en.wikipedia.org/wiki/Oracle_Open_Office
|-
|OxygenOffice Professional
|OxygenOffice Professional
|X
|
|X
|
|LGPL
|http://ooop.sf.net/
|
|-
|Pladao Office
|?
|X
|
|X
|X
|LGPL
|http://pladao.org/index.php?newlang=english
|
|-
|RedOffice
|Red Flag 2000
|X
|
|X
|
|proprietary
|http://www.redoffice.com/
|
|-
|SunShine Office
|CS2C
|
|
|X
|
|?
|http://www.cs2c.com.cn/
|
|-
|ThizOffice
|ThizTech
|X
|
|X
|
|?
|http://www.thizlinux.com.cn/
|
|-
|UP Office
|Philippines University
|1.0
|
|2.0
|
|?
|http://os.up.edu.ph/modules.php?name=Downloads&d_op=viewdownload&cid=2
|
|
|-
|Workplace
|IBM
|X
|
|X
|
|proprietary
|[workplacehome|http://www-142.ibm.com/software/workplace/products/product5.nsf/wdocs/workplacehome
|
|-
|WPS Office
|KingSoft
|X
|
|
|
|proprietary
|http://www.wps.com.cn/
|
|-
|602Office
|Software602
|
|
|
|
|?
|http://www.602.cz/cz/produkty/602office_2_2/
|http://cs.wikipedia.org/wiki/602Office
|
|-
|Jambo OpenOffice
|
|
|
|
|
|?
|http://www.o.ne.tz/
|http://en.wikipedia.org/wiki/Jambo_OpenOffice
|
|-
|RomanianOffice
|
|
|
|
|
|?
|http://www.romanianoffice.ro/
|http://en.wikipedia.org/wiki/RomanianOffice
|
|-
|Go-OO
|Novell
|X
|
|X
|
|LGPL
|http://go-oo.org/
|
|}

[[Category:Redoffice]]