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