Difference between revisions of "Development"
From Apache OpenOffice Wiki
m (Added and updated some links.) |
(cleanup of the most important infos for Apache OpenOffice) |
||
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
| − | == Getting started with | + | == Getting started with Apache OpenOffice development == |
| − | You are at the start of a long, but very exciting journey! OpenOffice | + | You are at the start of a long, but very exciting journey! Apache OpenOffice is a large and inclusive project. No matter what your interests are, there is always a place for you here. There are many ways to get started, but the easiest one is to: |
=== Get the source code and start building === | === Get the source code and start building === | ||
| − | Build you own OpenOffice | + | Build you own OpenOffice so that you are able to modify things |
| − | {{Template:Documentation/Tip| The [[Documentation/ | + | {{Template:Documentation/Tip| The [[Documentation/Building_Guide_AOO|Building Guide]] will walk you through this.}} |
=== Fix a bug or an annoyance === | === Fix a bug or an annoyance === | ||
| Line 13: | Line 13: | ||
=== Contribute more === | === Contribute more === | ||
| − | When you see that hacking | + | When you see that hacking AOO pleases you, it's time to look for bigger tasks, get in contact on [[IRC]] or on the mailing list: mailto:ooo-dev@openoffice.apache.org The list is friendly and supportive; the people want to help. |
| Line 23: | Line 23: | ||
* [[Documentation/Building Guide AOO|Building Guide]] | * [[Documentation/Building Guide AOO|Building Guide]] | ||
* [[Documentation/DevGuide|Development Guide]] | * [[Documentation/DevGuide|Development Guide]] | ||
| − | * [http:// | + | * [http://opengrok.adfinis-sygroup.org/source/ Opengrok] - source browser |
| − | + | ||
* [http://api.openoffice.org OpenOffice.org API] | * [http://api.openoffice.org OpenOffice.org API] | ||
| − | * [ | + | * [https://issues.apache.org/ooo/ Bugtracker] |
| − | + | ||
* [[Environment Variables]] - a description of handy environment variables used at runtime | * [[Environment Variables]] - a description of handy environment variables used at runtime | ||
* [[Source code directories| A description of the source directories]] | * [[Source code directories| A description of the source directories]] | ||
| Line 39: | Line 37: | ||
* [[Hacking]] | * [[Hacking]] | ||
* [[Debugging]] - for when it all goes wrong | * [[Debugging]] - for when it all goes wrong | ||
| − | |||
* [[Contributing Patches]] - for when you have something to fold back | * [[Contributing Patches]] - for when you have something to fold back | ||
* [[Commit Rights]] - An overview of how to attain commit rights, and what to do with them once you get them | * [[Commit Rights]] - An overview of how to attain commit rights, and what to do with them once you get them | ||
| Line 45: | Line 42: | ||
* [[Compiler versions used by port maintainers and release engineers]] | * [[Compiler versions used by port maintainers and release engineers]] | ||
* [[Writing warning-free code|Warning-free Code]] and [[Writing correct Cplusplus|Correct C++]] | * [[Writing warning-free code|Warning-free Code]] and [[Writing correct Cplusplus|Correct C++]] | ||
| − | |||
== Education project == | == Education project == | ||
Revision as of 10:28, 2 November 2012
Contents
Getting started with Apache OpenOffice development
You are at the start of a long, but very exciting journey! Apache OpenOffice is a large and inclusive project. No matter what your interests are, there is always a place for you here. There are many ways to get started, but the easiest one is to:
Get the source code and start building
Build you own OpenOffice so that you are able to modify things Template:Documentation/Tip
Fix a bug or an annoyance
Pick up your favorite bug/annoyance, and try to fix that. Read how to Contribute a patch via Issue Tracker. Template:Documentation/Tip
Contribute more
When you see that hacking AOO pleases you, it's time to look for bigger tasks, get in contact on IRC or on the mailing list: mailto:ooo-dev@openoffice.apache.org The list is friendly and supportive; the people want to help.
Create an extension
Exensions are easy to write and fun to see in action. You can add features that millions of others will use by using Java, Python, StarBasic, or JavaScript. Find more on Extension development wiki page. The OpenOffice.org UNO component model is quite extensive and can be daunting at first. To help you, there is a comprehensive Development Guide. The easiest way to get started is by using the plugins for Netbeans and for Eclipse. Plus, you can get help from mailto:dev@api.openoffice.org.
Development resources
- Building Guide
- Development Guide
- Opengrok - source browser
- OpenOffice.org API
- Bugtracker
- Environment Variables - a description of handy environment variables used at runtime
- A description of the source directories
- Localization for developers
- Build Bootstrapping
Further reading
- Meet the team on IRC
- Using C++ with OOo SDK
- Tutorials - hacker tutorials to get the hang of the code
- Hacking
- Debugging - for when it all goes wrong
- Contributing Patches - for when you have something to fold back
- Commit Rights - An overview of how to attain commit rights, and what to do with them once you get them
- Tips - misc. hints & tips.
- Compiler versions used by port maintainers and release engineers
- Warning-free Code and Correct C++
