Development

From OpenTTD
(Difference between revisions)
Jump to: navigation, search
Line 45: Line 45:
 
<font size="3">'''Coding'''</font>  <!-----------------------Coding--------->
 
<font size="3">'''Coding'''</font>  <!-----------------------Coding--------->
  
:*[[Developers]] of OpenTTD
+
*[[Developers]] of OpenTTD
:*[[Coding_style|Coding Style]] - How to code for OpenTTD
+
*[[Coding_style|Coding Style]] - How to code for OpenTTD
:*[[GUI_Style|GUI Style guide]] - Look and feel of the interface.
+
*[[GUI_Style|GUI Style guide]] - Look and feel of the interface.
:*[[Coding Tools]] to build and debug OpenTTD
+
*[[Coding Tools]] to build and debug OpenTTD
:*[[Todo list]] - Collection of discussion results on not yet implemented improvements
+
*[[Todo list]] - Collection of discussion results on not yet implemented improvements
:*[[Roadmap]] - See what's planned for future versions.
+
*[[Roadmap]] - See what's planned for future versions.
:*[http://docs.openttd.org Doxygen] - Documentation overview of the code
+
*[http://docs.openttd.org Doxygen] - Documentation overview of the code
:*[[Patch Checklist|Checklist for Patches]]
+
*[[Patch Checklist|Checklist for Patches]]
:*[http://bugs.openttd.org/ Bug tracker]
+
*[http://bugs.openttd.org/ Bug tracker]
  
 
|width="33%"|
 
|width="33%"|
 
<font size="3">'''Subprojects'''</font> <!-----------------------Subprojects--------->
 
<font size="3">'''Subprojects'''</font> <!-----------------------Subprojects--------->
  
:*[[Graphics Development]] - Find out everything about 32bpp graphics, newGrfs, Graphics replacement etc.
+
*[[Graphics Development]] - Find out everything about 32bpp graphics, newGrfs, Graphics replacement etc.
:*[[AI:Main_Page|NoAI]] - a new framework for user-made AIs
+
*[[AI:Main_Page|NoAI]] - a new framework for user-made AIs
:*[[Sound Effects Replacement]] - Creating a set of replacement sound effects for the game
+
*[[Sound Effects Replacement]] - Creating a set of replacement sound effects for the game
:*[[Passenger and cargo destinations]] - A new way of handling cargo and passengers allowing specific destinations
+
*[[Passenger and cargo destinations]] - A new way of handling cargo and passengers allowing specific destinations
:*[[Passenger and cargo distribution]] - A new and better way of handling cargo and passengers allowing specific destinations
+
*[[Passenger and cargo distribution]] - A new and better way of handling cargo and passengers allowing specific destinations
 
|}  <!------------- 3th part ------------->
 
|}  <!------------- 3th part ------------->
 
{| cellspacing="3" class="mainpagetable" align="center" style="background-color: #E7EBFF; border: 1px solid #c7c8fe; margin:0; border-top:none; padding: 1em 1em 0em 1em; margin-bottom:2em"
 
{| cellspacing="3" class="mainpagetable" align="center" style="background-color: #E7EBFF; border: 1px solid #c7c8fe; margin:0; border-top:none; padding: 1em 1em 0em 1em; margin-bottom:2em"
Line 69: Line 69:
 
<font size="3">'''Development documentation'''</font>  <!---------Development documentation--------->
 
<font size="3">'''Development documentation'''</font>  <!---------Development documentation--------->
  
:*[[Development Documentation]]
+
*[[Development Documentation]]
:*[[To do for releases]]
+
*[[To do for releases]]
:*[[Nightly builds]]
+
*[[Nightly builds]]
:*[[Compile Farm]]
+
*[[Compile Farm]]
:*[[:Category:Compiling_OpenTTD|Compiling OpenTTD]]
+
*[[:Category:Compiling_OpenTTD|Compiling OpenTTD]]
:*[[OpenTTD Release History]]
+
*[[OpenTTD Release History]]
  
 
|width="33%"|
 
|width="33%"|
Line 80: Line 80:
  
 
In the list below are some tips, and helpful tidbits to help you code/debug and get your patches to be accepted swiftly and without problems to the source
 
In the list below are some tips, and helpful tidbits to help you code/debug and get your patches to be accepted swiftly and without problems to the source
:*[[Coding guidelines]] - to keep a coherent feel of the code, we ask you to code your patches in the following style
+
*[[Coding guidelines]] - to keep a coherent feel of the code, we ask you to code your patches in the following style
:*[[Debugging]]
+
*[[Debugging]]
:*[[Strings]] - with the string system being not too userfriendly, this might help you on your way
+
*[[Strings]] - with the string system being not too userfriendly, this might help you on your way
  
 
|width="33%"|
 
|width="33%"|
 
<font size="3">'''Miscellaneous'''</font>  <!------------- Miscellaneous ------------->
 
<font size="3">'''Miscellaneous'''</font>  <!------------- Miscellaneous ------------->
  
:* [http://www.openttd.org OpenTTD website]
+
* [http://www.openttd.org OpenTTD website]
:* [http://www.tt-forums.net/viewforum.php?f=55 OpenTTD forum]
+
* [http://www.tt-forums.net/viewforum.php?f=55 OpenTTD forum]
:* [http://cia.vc/stats/project/OpenTTD CIA Stats]
+
* [http://cia.vc/stats/project/OpenTTD CIA Stats]
:* [[Requested features]]
+
* [[Requested features]]
:* [[Rejected features|Rejected features]]
+
* [[Rejected features|Rejected features]]
:* [[Miscellaneous suggestions]]
+
* [[Miscellaneous suggestions]]
 
|}
 
|}
  
  
 
[[Category:Development]]
 
[[Category:Development]]

Revision as of 14:51, 24 August 2010


BlackBook.png

OpenTTD Development Manual OpenTTD is an open source project, published under the GPL. You can view the sourcecode online or download the latest tree using SVN. If you modify the source you can submit a diff file with your changes to the Patch tracker.

Development

Objectives - OpenTTD's long term objectives, these are mission statements that should help define the boundaries of OpenTTD development into the future.

Recent and Current Developments shows the developments in trunk since the last major release as well as the purpose of the branches in our SVN repository.

The latest changes to the OpenTTD SVN tree are on the cia.navi.cx service (RSS feed also avaible)

Coding

Subprojects

Development documentation

Help with coding

In the list below are some tips, and helpful tidbits to help you code/debug and get your patches to be accepted swiftly and without problems to the source

  • Coding guidelines - to keep a coherent feel of the code, we ask you to code your patches in the following style
  • Debugging
  • Strings - with the string system being not too userfriendly, this might help you on your way

Miscellaneous

Personal tools