Development

From OpenTTD
(Difference between revisions)
Jump to: navigation, search
m
(Remove some hopelessly outdated links)
Line 24: Line 24:
  
 
:*[[Developers]] of OpenTTD
 
:*[[Developers]] of OpenTTD
:*[[WhoWorksOnWhat]] - A list of Developers/Volunteers projects
 
 
:*[[Coding_style|Coding Style]] - How to code for OpenTTD
 
:*[[Coding_style|Coding Style]] - How to code for OpenTTD
 
:*[[Coding Tools]] to build and debug OpenTTD
 
:*[[Coding Tools]] to build and debug OpenTTD
Line 36: Line 35:
 
<font size="3">'''Subprojects'''</font>
 
<font size="3">'''Subprojects'''</font>
  
:*[[Network Protocol]] - Network protocol and its status
 
 
:*[[Graphics Development]] - Find out everything about 32bpp graphics, newGrfs, Graphics replacement etc.
 
:*[[Graphics Development]] - Find out everything about 32bpp graphics, newGrfs, Graphics replacement etc.
:*[[CentralisedAuthentication]] - a proposal for a central authentication system
 
 
:*[[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

Revision as of 02:01, 17 February 2009

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