Development

From OpenTTD
(Difference between revisions)
Jump to: navigation, search
m
(update some links)
Line 15: Line 15:
 
[[Image:BlackBook.png|64px|left]]
 
[[Image:BlackBook.png|64px|left]]
 
<p style="font-size: 120%; font-weight:bold;">OpenTTD Development Manual</p>
 
<p style="font-size: 120%; font-weight:bold;">OpenTTD Development Manual</p>
[[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 [https://github.com/OpenTTD/OpenTTD view the repository online] and download a copy of the latest source code using [[Git]]. If you modify the source you can submit a [[Git#How_do_I_make_a_diff_file_to_share_my_changes_with_other_coders.3F|pull request]] with your changes to the repository.
 
|-
 
|-
 
| style="vertical-align:top;" |
 
| style="vertical-align:top;" |
Line 22: Line 22:
 
[[Objectives]] - OpenTTD's long term objectives,  these are mission statements that should help define the boundaries of OpenTTD development into the future.
 
[[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.
+
[[Recent and Current Developments]] shows the developments in trunk since the last major release as well as the purpose of the branches in our [[Git]] repository. [TODO: except it doesn't]
  
The latest changes to the OpenTTD [[SVN]] tree are on the [http://cia.navi.cx/stats/project/OpenTTD cia.navi.cx service] ([http://cia.navi.cx/stats/project/OpenTTD/.rss?ver=2&medium=unquoted&limit=15 RSS feed also available])
+
The latest changes to the OpenTTD [[Git]] repository can be seen on [https://github.com/OpenTTD/OpenTTD/commits GitHub] ([https://github.com/OpenTTD/OpenTTD/commits/master.atom RSS feed also available!])
 
| style="vertical-align:top;" |
 
| style="vertical-align:top;" |
 
<p style="font-size: 110%; font-weight:bold;">Coding</p>
 
<p style="font-size: 110%; font-weight:bold;">Coding</p>
Line 32: Line 32:
 
*[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]
+
*[https://github.com/OpenTTD/OpenTTD/issues Bug tracker]
 
|-
 
|-
 
| style="background-color:#c7c8fe; vertical-align:top;" |
 
| style="background-color:#c7c8fe; vertical-align:top;" |

Revision as of 22:01, 21 March 2019


BlackBook.png

OpenTTD Development Manual

OpenTTD is an open source project, published under the GPL. You can view the repository online and download a copy of the latest source code using Git. If you modify the source you can submit a pull request with your changes to the repository.

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 Git repository. [TODO: except it doesn't]

The latest changes to the OpenTTD Git repository can be seen on GitHub (RSS feed also available!)

Coding

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 user friendly, this might help you on your way
Personal tools