Changes between Version 20 and Version 21 of dev/Primer

Timestamp:

Sep 22, 2007, 2:46:17 PM (17 years ago)

Author:

simon

Comment:

—

dev/Primer

@@ -58 +58 @@
 
 == 8. Compiling and Running ==
-To get Orxonox running on your system, first read the following articles: [wiki:Running How to get Orxonox running].
+To get Orxonox running on your system, first read [wiki:Running how to get Orxonox running].
 
 
 == 9. Finding your Way as a Developer ==
-As a developer of Orxonox you will want to communicate over our mailinglists, the wiki and the irc. You will find the current tasks, for the next orxonox release under:
+As a developer of Orxonox you will want to communicate over our mailing lists, the wiki and irc. You will find the current tasks, for the next orxonox release under:
  * [https://www.orxonox.net/cgi-bin/trac.cgi/roadmap Roadmap]
 and all tasks, that we have defined yet:
@@ -69 +69 @@
 the timeline of our Wiki:
 * [https://www.orxonox.net/cgi-bin/trac.cgi/timeline timeline]
-The commit messages will also be sent to your email adress, if you have registered to the orxonox-commit mailinglist
+The commit messages will also be sent to your email adress, if you have registered to the orxonox-commit mailinglist.
 
 
 == 10. Understanding Orxonox ==
-It definitely takes some time to understand the Orxonox source code. The best way to get your questions answered is to post them on the development-mailinglist. Even better is to just go to the developers and ask them to give you an overview... Once you know where to find which functions, you will want to read some more about special topics in the source files themselves: we use doxygen to comment the code, so you will find comments for every class/function. There is a second source of information, which we are currently working
-on: [wiki:ModulesDescription module description]
-
+It definitely takes some time to understand the Orxonox source code. The best way to get your questions answered is to post them on the development-mailinglist. Even better is to just go to the developers and ask specific questions... Once you know where to find which functions, you will want to read some more about special topics in the source files themselves: we use doxygen to comment the code, so you will find comments for every class/function. There are also [wiki:ModulesDescription module descriptions] which we are currently working on.