SoC Ideas Savegame - Revision history

Yogi Bear: /* Proposal contents */

2009-03-25T22:02:37Z

‎Proposal contents

Yogi Bear: /* Proposal contents */

2009-03-25T21:57:08Z

‎Proposal contents

Yogi Bear: /* Proposal contents */

2009-03-25T21:56:22Z

‎Proposal contents

Yogi Bear: /* Proposal contents (under construction) */

2009-03-25T21:29:31Z

‎Proposal contents (under construction)

Yogi Bear: /* Proposal contents (under construction) */

2009-03-25T20:02:49Z

‎Proposal contents (under construction)

Yogi Bear: /* Proposal contents (under construction) */

2009-03-25T20:01:48Z

‎Proposal contents (under construction)

Yogi Bear: /* Proposal contents (under construction) */

2009-03-25T19:34:57Z

‎Proposal contents (under construction)

Yogi Bear: /* Proposal contents (under construction) */

2009-03-25T19:28:34Z

‎Proposal contents (under construction)

Yogi Bear: /* Proposal contents (under construction) */

2009-03-25T19:25:46Z

‎Proposal contents (under construction)

Yogi Bear: /* Proposal contents (under construction) */

2009-03-25T19:23:58Z

‎Proposal contents (under construction)

@@ Line 50: / Line 50: @@
 .
-The <i>player_info</i> struct and the <i>team</i> class share some information (for example units that belong to a certain side). Do you think it is a feasible idea to mold those two into one? And what are your reasons?
+The <i>player_info</i> struct and the <i>team</i> class share some information (for example units that belong to a certain side). Do you think it is feasible to mold those two into one? And what are your reasons?
 .

@@ Line 36: / Line 36: @@
 However, there is some preparation you can do by now already. You should also add your thoughts about this to the proposal you are giving us. If you get accepted, this will serve as a starting point for further fleshing out things.
-Don't hesitate to seek for help, if you have difficulties with some of the questions. I (YogiHH) will be on IRC most of the time in the evening (GMT+1) hours. You can also reach me by mail (joerg.hinrichs@alice-dsl.de) if that is not sufficient. Also keep in mind, that this is not a typical test with &quot;right and wrong&quot;. It is clear that being new you won't be able to make the &quot;perfect proposal&quot; right out of the box. We are more interested in how you approach this task, how you communicate and if you can focus on the relevant stuff without losing yourself into details. So know what you are talking about, be innovative and take initiative.
+Don't hesitate to seek for help, if you have difficulties with some of the questions. I (YogiHH) will be on IRC most of the time in the evening (GMT+1) hours. You can also reach me by mail (joerg.hinrichs@alice-dsl.de) if that is not sufficient. Also keep in mind, that this is not a typical test with &quot;right and wrong&quot;. It is clear that being new you won't be able to provide the &quot;perfect proposal&quot; right out of the box. We are more interested in how you approach this task, how you communicate and if you can focus on the relevant stuff without losing yourself into details. So know what you are talking about, be innovative and take initiative.
 The following two links are meant to give you further information for that:<br>

@@ Line 34: / Line 34: @@
 === Proposal contents ===
 Here are some questions and ideas to help you dive into the topic. They are meant to help you get a better idea of what this project is going to be about. They are also meant to show us, how much you made yourself familiar with wesnoth's code, as this is very important to us. We are mostly ambitious and passionate ourselves, and we seek for students that are alike. Other (wesnoth) projects provide the opportunity to present prototypes, which won't be working here. Therefore it is even more important, that you implement some patches to show us your coding skills.<br>
-However, there is some preparation you can do by now already. You should also add your thoughts about this to the proposal you are giving us. If you get accepted, this will surve as a starting point for further fleshing out things.
+However, there is some preparation you can do by now already. You should also add your thoughts about this to the proposal you are giving us. If you get accepted, this will serve as a starting point for further fleshing out things.
 Don't hesitate to seek for help, if you have difficulties with some of the questions. I (YogiHH) will be on IRC most of the time in the evening (GMT+1) hours. You can also reach me by mail (joerg.hinrichs@alice-dsl.de) if that is not sufficient. Also keep in mind, that this is not a typical test with &quot;right and wrong&quot;. It is clear that being new you won't be able to make the &quot;perfect proposal&quot; right out of the box. We are more interested in how you approach this task, how you communicate and if you can focus on the relevant stuff without losing yourself into details. So know what you are talking about, be innovative and take initiative.

@@ Line 32: / Line 32: @@
 * ''Implementing :'' It is hard to give detailed information about the content of this phase. But basically it will be implementing the roadmap steps one by one.
-=== Proposal contents (under construction) ===
+=== Proposal contents ===
 Here are some questions and ideas to help you dive into the topic. They are meant to help you get a better idea of what this project is going to be about. They are also meant to show us, how much you made yourself familiar with wesnoth's code, as this is very important to us. We are mostly ambitious and passionate ourselves, and we seek for students that are alike. Other (wesnoth) projects provide the opportunity to present prototypes, which won't be working here. Therefore it is even more important, that you implement some patches to show us your coding skills.<br>
 However, there is some preparation you can do by now already. You should also add your thoughts about this to the proposal you are giving us. If you get accepted, this will surve as a starting point for further fleshing out things.

@@ Line 39: / Line 39: @@
 The following two links are meant to give you further information for that:<br>
-[[Summer of Code:#SavegameCode|savegame code]] - Contains the pieces of codes that deal with savegames and where to find them<br>
+[[SavegameCode|savegame code]] - Contains the pieces of codes that deal with savegames and where to find them<br>
 [[Summer of Code:SavegameWMLMapping|WML - object mapping]] - A mapping table to show you which objects hold the information of the savegame WML content<br>