[1795] | 1 | |
---|
| 2 | This is the offical README file for the game project |
---|
| 3 | |
---|
| 4 | -------------------------------------------------------- |
---|
| 5 | orxOnox |
---|
| 6 | -------------------------------------------------------- |
---|
| 7 | |
---|
| 8 | |
---|
| 9 | |
---|
| 10 | |
---|
[1800] | 11 | 1.Preface: |
---|
[1795] | 12 | ---------- |
---|
| 13 | Orxonox is a open-source vertical scroller game programed |
---|
| 14 | in c++ and OpenGL. |
---|
| 15 | If we manage to be sober enough, this game shall definitly |
---|
[1855] | 16 | become _the_ open-source vertical scroller ever. |
---|
[1795] | 17 | |
---|
[1800] | 18 | 2.Manifesto: |
---|
| 19 | ------------ |
---|
| 20 | 1) Alien is a great film |
---|
| 21 | 2) Guiness is the most delicious beer |
---|
[1896] | 22 | 3) If you think there is anything missing: you can be shure it's an arcade game |
---|
[1795] | 23 | |
---|
[1800] | 24 | to be continoued... |
---|
| 25 | |
---|
| 26 | |
---|
| 27 | 3.Overview: |
---|
[1795] | 28 | --------- |
---|
[1800] | 29 | 1.Preface |
---|
| 30 | 2.Manifesto |
---|
| 31 | 3.Overview |
---|
[1795] | 32 | 3.Contributing To The Project |
---|
[1800] | 33 | 4.Howto C++ Programming |
---|
| 34 | 5.Howto SVN |
---|
[1855] | 35 | 6.Coding conventions |
---|
[1795] | 36 | |
---|
| 37 | |
---|
[1800] | 38 | 4.Contributing To The project: |
---|
[1795] | 39 | ------------------------------ |
---|
| 40 | People who want to help us working on orxonox are always |
---|
| 41 | welcome:) Feel free to chip in anything you like. Wine, beer, |
---|
| 42 | coffee... If you like to help us programming orxonox, you: |
---|
| 43 | - join the developer community mailing lists |
---|
| 44 | - read this README file |
---|
| 45 | then you have multiple ways to get started. |
---|
| 46 | a) Read the hole source code and choose a topic you like |
---|
| 47 | b) check the TODO file to get a knowledge of what we need |
---|
| 48 | c) ask us for more information |
---|
| 49 | To get more informations about programming and project specs |
---|
| 50 | read the programming sections below. |
---|
| 51 | |
---|
| 52 | To start programming on orxonox you first have to download the |
---|
| 53 | newest svn tree of orxonox. You can do this by enterning following |
---|
[1796] | 54 | lines in the linux console (ensure svn to be installed with ssl |
---|
| 55 | support enabled): |
---|
[1795] | 56 | |
---|
| 57 | svn co https://open.datacore.ch/pw/orxonox orxonox |
---|
| 58 | |
---|
[1796] | 59 | If you haven't got ssl support in you svn tool, recompile it |
---|
[1795] | 60 | ./configure --with-ssl |
---|
| 61 | make |
---|
| 62 | make install |
---|
| 63 | |
---|
| 64 | |
---|
[1800] | 65 | 5.Howto C++ Programming: |
---|
[1795] | 66 | ------------------------ |
---|
| 67 | If you are new to c/c++ programming, this project is probably |
---|
| 68 | not the best starting place to learn it. For you and the rest who |
---|
| 69 | need "refreshment" check out these guides: |
---|
| 70 | |
---|
| 71 | www.cplusplus.com/doc/tutorial |
---|
| 72 | www.4p8.com/eric.brasseur/cppcen.html |
---|
| 73 | |
---|
| 74 | |
---|
[1800] | 75 | 6.Howto SVN: |
---|
| 76 | ------------ |
---|
[1796] | 77 | For a more complete guide about this topic read the documentation |
---|
| 78 | avaiable at subversion.tigris.org. |
---|
[1795] | 79 | |
---|
[1796] | 80 | SVN (=subversion) is a version control program similar to CVS but |
---|
| 81 | newer. This program enables us to work all at the same program at |
---|
| 82 | the same time - tricky. |
---|
[1795] | 83 | |
---|
[1796] | 84 | subversion checkout https://open.datacore.ch/pw/orxonox orxonox |
---|
| 85 | same as: subversion co https://open.datacore.... |
---|
| 86 | |
---|
| 87 | this makes a directory orxonox at your current place in and gets |
---|
| 88 | the hole brand new source code from the server. |
---|
| 89 | |
---|
| 90 | now you can work. Remember to use 'svn copy instead of 'cp', |
---|
| 91 | 'svn mv' instead of 'mv', 'svn rm' instead of 'rm'... - you got it |
---|
| 92 | I think. |
---|
| 93 | After you have made your changes to the files enter |
---|
| 94 | svn status |
---|
| 95 | or with more details: svn status -vv |
---|
| 96 | which will show you the changes you did locally on your computer. |
---|
| 97 | svn diff |
---|
| 98 | is similar but shows you all the changes in detail. |
---|
| 99 | |
---|
| 100 | svn diff > patchfile |
---|
| 101 | the patchfile you can use later in conjunction with the patch program. |
---|
| 102 | You could, for example, email this patchfile to another developer for |
---|
| 103 | review or testing prior to commit. |
---|
| 104 | |
---|
| 105 | To add a new file type |
---|
| 106 | svn add <filename> |
---|
| 107 | and to publish all your changes type |
---|
[1800] | 108 | svn commit --message "Corrected number of chees slices." |
---|
| 109 | svn commit will send all of your changs to the repository. When you |
---|
| 110 | commit a change, you need to supply a log message, describing your |
---|
| 111 | change. The message can also be read from a file: |
---|
| 112 | svn commit --file logmsg |
---|
[1796] | 113 | |
---|
| 114 | If you accidently make a change you like to revert, you just can do this |
---|
| 115 | by typing: |
---|
| 116 | svn revert <filename> |
---|
| 117 | |
---|
[1800] | 118 | To keep track about the work that is running on the project use the |
---|
| 119 | command: svn log. This will show you a bref summary of all changes. |
---|
| 120 | |
---|
| 121 | |
---|
| 122 | Most of the programmer will do their work on a branch. A Branch is |
---|
| 123 | a line of development that exists independently of another line, yet |
---|
| 124 | still shares a common history. A branch always begins life as a copy |
---|
| 125 | of something, and moves on trom there, generating its own history. Later |
---|
| 126 | the two versions will merge. |
---|
| 127 | |
---|
| 128 | If you are working on orxonox you will have your own branch in which you |
---|
| 129 | will program, some sort of sand-box. If you finish your work on your |
---|
| 130 | topic, it will be revised by us and merged with the trunk |
---|
| 131 | |
---|
[1855] | 132 | 7.Coding Conventions |
---|
| 133 | -------------------- |
---|
| 134 | Read the File CODING-STANDARDS |
---|
[1800] | 135 | |
---|
| 136 | |
---|
| 137 | #EOF |
---|