Difference between revisions of "Development"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Getting started with OOo development)
Line 8: Line 8:
 
</div>
 
</div>
  
[[Development/OpenOffice.org Building Guide|Building]] and [[hacking]] on OpenOffice.org (OOo) entails climbing a fairly lengthy and steep incline.  Hopefully, this wiki will make the learning curve less steep and less abrupt, and will give you a walking stick to help you out.
+
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:
  
Much of our documentation assumes that you'll be using a reasonably current Linux system, as this the most easy environment to start. On Linux all prerequisites are available as [http://www.gnu.org Free software]. There is also some information on developing on [[Documentation/Building_Guide/Building_on_Windows|Windows]].
+
* 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
  
It should also be noted that you can build either the [[Documentation/Building Guide|vanilla OOo]] or use an [[ooo-build]] release which adds some patches & fixes. The ooo-build process was originally started to work around some problems the vanilla build system had in earlier releases.
+
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]].
  
In the same way, learning UNO components development is not an easy task. To help you there are plugins for [[OpenOffice_NetBeans_Integration|Netbeans]] and for [[OpenOffice_Eclipse_Integration|Eclipse]].
+
== Development resources ==
 
+
* [[Documentation/DevGuide|Development Guide]]
== Going Further ==
+
* [http://svn.services.openoffice.org/opengrok/ Opengrok] - source browser
 
+
* [http://hg.services.openoffice.org/hg/ Mercurial-Webinterface]
* [[IRC Communication|Meet the team on IRC]]
+
* [http://api.openoffice.org OpenOffice.org API]
* [[Hacking]] - how to get started
+
* [http://eis.services.openoffice.org/ Environment Information System also called EIS], more infos can be found [[EIS|here]].
* [[Tutorials]] - hacker tutorials to get the hang of the code
+
* [http://qa.openoffice.org/issues/ Bugtracker]
* [[Debugging]] - for when it all goes wrong
+
* [[Environment Variables]] - a description of handy environment variables used at runtime  
* [[Tinderbox]] - test new child workspaces and show your build logfile to others
+
* [[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]]
* [[Contributing Patches]] - for when you have something to fold back
+
== Further reading ==
* [[Commit Rights]] - An overview of how to attain commit rights, and what to do with them once you get them
+
* [[IRC Communication|Meet the team on IRC]]
* [[Tips]] - misc. hints &amp; tips.
+
* [[FAQ]] - some infrequently asked questions
+
 
* [[Using_Cpp_with_the_OOo_SDK|Using C++ with OOo SDK]]
 
* [[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 &amp; 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

Further reading

Education project





Personal tools