Difference between revisions of "Development"
From Apache OpenOffice Wiki
B michaelsen (talk | contribs) |
B michaelsen (talk | contribs) |
||
Line 8: | Line 8: | ||
</div> | </div> | ||
− | + | You are at the start of a long, but very exciting journey! There are many ways to get started, but the easiest one is to: | |
− | + | * Get the source code and build you own OpenOffice.org so that you are able to modify things | |
+ | {{Template:Documentation/Tip| The [[Documentation/Building_Guide|Building Guide]] will walk you through this.<ref name="Foot1">An alternative is using [[ooo-build]]. which was originally started to work around some problems the vanilla build system had in earlier releases.</ref>}} | ||
+ | * Pick up your favorite bug/annoyance, and try to fix that | ||
+ | * When you see that hacking OOo pleases you, it's time to look for bigger tasks, get in contact on [[IRC]] or on the mailing list: mailto:dev@openoffice.org | ||
− | + | If you want to extend OpenOffice.org with extensions and UNO components take a look at the [[Documentation/DevGuide|Development Guide]]. The easiest way to get started is by using the plugins for [[OpenOffice_NetBeans_Integration|Netbeans]] and for [[OpenOffice_Eclipse_Integration|Eclipse]]. | |
− | + | == Development resources == | |
+ | * [[Documentation/DevGuide|Development Guide]] | ||
+ | * [http://svn.services.openoffice.org/opengrok/ Opengrok] - source browser | ||
+ | * [http://hg.services.openoffice.org/hg/ Mercurial-Webinterface] | ||
+ | * [http://api.openoffice.org OpenOffice.org API] | ||
+ | * [http://eis.services.openoffice.org/ Environment Information System also called EIS], more infos can be found [[EIS|here]]. | ||
+ | * [http://qa.openoffice.org/issues/ Bugtracker] | ||
+ | * [[Environment Variables]] - a description of handy environment variables used at runtime | ||
+ | * [[Source code directories| A description of the source directories]] | ||
+ | == Further reading == | ||
+ | * [[IRC Communication|Meet the team on IRC]] | ||
+ | * [[Using_Cpp_with_the_OOo_SDK|Using C++ with OOo SDK]] | ||
+ | * [[Tutorials]] - hacker tutorials to get the hang of the code | ||
+ | * [[Hacking]] | ||
+ | * [[Debugging]] - for when it all goes wrong | ||
+ | * [[Mercurial]] and [[OOo and Subversion]] - How to use the SCMs that OOo uses | ||
+ | * [[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]] | ||
+ | * [[Writing warning-free code|Warning-free Code]] and [[Writing correct Cplusplus|Correct C++]] | ||
+ | * [[Tinderbox]] - test new child workspaces and show your build logfile to others | ||
− | == | + | == Education project == |
+ | {{Template:Documentation/Tip|If you don't find the instructions in the Wiki good enough to guide you, feel free to [mailto:dev-subscribe_at_openoffice.org subscribe] and ask on the [mailto:dev_at_openoffice.org dev@openoffice.org] mailing list. If you are interested in some aspect that is not covered, ask the [http://www.openoffice.org/mail_list.html mailing list] as well. We'll guide you where to find people who will be able to answer your questions. Lots of developers also hang on [[IRC_Communication|IRC]] - join #dev.openoffice.org on irc.freenode.net.}} | ||
− | + | {{Template:Documentation/Tip|Another solution is to contact the [[Education Project]], who aims to find future OpenOffice.org developers, mainly students, who are discovering OpenOffice.org Project. The dedicated Education Project channel is : [irc://irc.freenode.net/education.openoffice.org #education.openoffice.org]}} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | {{Template:Documentation/Tip|In the [http://wiki.services.openoffice.org/wiki/Education_ClassRoom '''ClassRoom'''] page, you will find more information about the essentials. For example, you'll find on them [[Education_ClassRoom/Practice|Practice]], or [[Education_ClassRoom/Previous_Logs|IRC Meetings Logs]] we did as "ClassRooms".}} | ||
− | [[Category:Development]] | + | ---- |
+ | <references/> | ||
+ | [[Category:Development]][[Category:Build System]][[Category:SCM]] |
Revision as of 23:03, 7 November 2009
Getting started with OOo development
Get Started from Scratch
You will find how to:
- get the source
- and build OpenOffice.org
step by step in the Building Guide.
You are at the start of a long, but very exciting journey! There are many ways to get started, but the easiest one is to:
- Get the source code and build you own OpenOffice.org so that you are able to modify things
- Pick up your favorite bug/annoyance, and try to fix that
- When you see that hacking OOo pleases you, it's time to look for bigger tasks, get in contact on IRC or on the mailing list: mailto:dev@openoffice.org
If you want to extend OpenOffice.org with extensions and UNO components take a look at the Development Guide. The easiest way to get started is by using the plugins for Netbeans and for Eclipse.
Development resources
- Development Guide
- Opengrok - source browser
- Mercurial-Webinterface
- OpenOffice.org API
- Environment Information System also called EIS, more infos can be found here.
- Bugtracker
- Environment Variables - a description of handy environment variables used at runtime
- A description of the source directories
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
- Mercurial and OOo and Subversion - How to use the SCMs that OOo uses
- 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++
- Tinderbox - test new child workspaces and show your build logfile to others