Development

From OpenTTD
(Difference between revisions)
Jump to: navigation, search
(Added a link to new Server Admin Port development page)
m (Fixed a broken hyperlink.)
 
(One intermediate revision by one user not shown)
Line 4: Line 4:
 
|fi=Kehittäminen
 
|fi=Kehittäminen
 
|fr=Développement
 
|fr=Développement
 +
|ko=개발
 
|nl=Ontwikkelingen
 
|nl=Ontwikkelingen
 
|ro=Dezvoltare
 
|ro=Dezvoltare
Line 14: Line 15:
 
[[OpenTTD]] is an open source project, published under the [http://www.gnu.org/copyleft/gpl.html GPL]. You can [http://svn.openttd.org/ view the sourcecode online] or download the latest tree using [[SVN]]. If you modify the source you can submit a [[SVN#How_do_I_make_a_diff_file_to_share_my_changes_with_other_coders.3F|diff file]] with your changes to the [http://bugs.openttd.org Patch tracker].
 
[[OpenTTD]] is an open source project, published under the [http://www.gnu.org/copyleft/gpl.html GPL]. You can [http://svn.openttd.org/ view the sourcecode online] or download the latest tree using [[SVN]]. If you modify the source you can submit a [[SVN#How_do_I_make_a_diff_file_to_share_my_changes_with_other_coders.3F|diff file]] with your changes to the [http://bugs.openttd.org Patch tracker].
 
</div>
 
</div>
{| cellspacing="3" class="mainpagetable" align="center" cellpadding="10px" style="margin:0;"
+
{| cellspacing="3" class="mainpagetable" cellpadding="10px" style="margin:0;"
 
|- valign="top"
 
|- valign="top"
 
|width="33%" style="border: 1px solid #c7c8fe; border-bottom: none;"|
 
|width="33%" style="border: 1px solid #c7c8fe; border-bottom: none;"|
Line 49: Line 50:
 
*[[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" cellpadding="10px" style="background-color: #E7EBFF; border: 1px solid #c7c8fe; margin:0; border-top:none; padding:0; margin-bottom:2em"
+
{| cellspacing="3" class="mainpagetable" cellpadding="10px" style="background-color: #E7EBFF; border: 1px solid #c7c8fe; margin:0; border-top:none; padding:0; margin-bottom:2em"
 
|- valign="top"
 
|- valign="top"
 
|width="33%" style="border: 1px solid #c7c8fe;"|
 
|width="33%" style="border: 1px solid #c7c8fe;"|
Line 79: Line 80:
 
* [[Todo list]]
 
* [[Todo list]]
 
* List of [[Requested features|other patches]] (check also [http://www.tt-forums.net/viewforum.php?f=33 dev section of forums])
 
* List of [[Requested features|other patches]] (check also [http://www.tt-forums.net/viewforum.php?f=33 dev section of forums])
* [[Rejected features List|Rejected features]]
+
* [[Rejected features]]
 
* [[Miscellaneous suggestions]]
 
* [[Miscellaneous suggestions]]
 
* [[List of patches]]
 
* [[List of patches]]

Latest revision as of 13:41, 24 May 2015


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 Todo list contains tasks which require no detailed knowledge of then OpenTTD code base. Look here if you want to get involved with the development of OpenTTD, but are unsure with what task to get started.

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

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 style - 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