SummerOfCodeProposal gabba - Revision history

Esr: Hide historical references to Subversion from the wiki search function

2013-03-21T03:32:46Z

Hide historical references to Subversion from the wiki search function

← Older revision		Revision as of 03:32, 21 March 2013
Line 217:		Line 217:

	==== [player] vs [snapshot.player] ====		==== [player] vs [snapshot.player] ====
	<nowiki>My colleague mentions this distinction, but this has apparently been fixed by grantwu; in saves produced by the latest ~~svn~~ version I can't find a [player] tag in root, only [snapshot.player] or [replay_start.player]</nowiki>		<nowiki>My colleague mentions this distinction, but this has apparently been fixed by grantwu; in saves produced by the latest svn version I can't find a [player] tag in root, only [snapshot.player] or [replay_start.player]</nowiki>

	==== [snapshot.player] vs [replay_start.player] ====		==== [snapshot.player] vs [replay_start.player] ====

Esr: Hide historical references to Subversion from the wiki search function

2013-03-21T00:23:15Z

Hide historical references to Subversion from the wiki search function

← Older revision		Revision as of 00:23, 21 March 2013
Line 357:		Line 357:
	==Practical considerations==		==Practical considerations==

	I use ~~subversion~~ extensively for all my projects. C++ is my main programming language, which I used in all three of my major projects. I know Java rather well too. However I never used Python, but I delved in the source of some programs written in Python, such as Wrye Bash, a modding tool for Oblivion.		I use subversion extensively for all my projects. C++ is my main programming language, which I used in all three of my major projects. I know Java rather well too. However I never used Python, but I delved in the source of some programs written in Python, such as Wrye Bash, a modding tool for Oblivion.

	As far as IDEs go, my favorite C++ development tool is probably Netbeans, but I can be just as efficient under Visual Studio or Eclipse.		As far as IDEs go, my favorite C++ development tool is probably Netbeans, but I can be just as efficient under Visual Studio or Eclipse.

Gabba at 19:42, 20 April 2009

2009-04-20T19:42:01Z

← Older revision		Revision as of 19:42, 20 April 2009
Line 1:		Line 1:
	~~'''''Hot off the press! Go look at the Technical Details section, I've made a major update.'''''~~
	~~'''''Also look at the Open Source Involvement section, I've submitted a patch'''''~~

	==Introduction==		==Introduction==

	I'm a third year student in software engineering at École Polytechnique de Montréal (http://www.polymtl.ca), in Québec, Canada. I've always been passionate about games, and I'm a regular player of Battle for Wesnoth.

	~~'''''You can reach me at:''''' gabrielmorin _-AT-_ gmail _-DOT-_ com~~

	'''''IRC:''''' gabm		'''''IRC:''''' gabm

	'''''Wesnoth forums and GNA!:''''' gabba		'''''Wesnoth forums and GNA!:''''' gabba

	~~I also have a skype account for communicating with my mentor.~~

	I'm awake/available for the project roughly from UTC 14:00 to 22:00. When the SOC starts, I plan to be logged on to IRC most of that time, but I'll have to see with my mentor what's efficient. Until then I'll do my best to show up on IRC so people can get to know me, but university keeps me very busy!

	'''''Languages spoken:''''' French, English, Spanish		'''''Languages spoken:''''' French, English, Spanish
Line 42:		Line 31:
	I got involved mostly in two open source projects: TA Spring and Battle for Wesnoth.		I got involved mostly in two open source projects: TA Spring and Battle for Wesnoth.

	TA Spring (http://spring.clan-sy.com): I became an active participant on the forums ~~(under the nickname 'gabba')~~ since the early days of the project. I contributed a lot of ideas, many of which were implemented; for instance the terrain map that determines regions of the map that hinder or accelerate unit movements. I also did one or two hacks to the source code and posted them on the forum, but I was not much involved with the coding.		TA Spring (http://spring.clan-sy.com): I became an active participant on the forums since the early days of the project. I contributed a lot of ideas, many of which were implemented; for instance the terrain map that determines regions of the map that hinder or accelerate unit movements. I also did one or two hacks to the source code and posted them on the forum, but I was not much involved with the coding.

	Battle for Wesnoth: I was active for a while on the forums ~~under the nickname 'gabba'~~, and again I mainly contributed ideas, especially in the domain of AMLA (units improving beyond their maximum XP level).		Battle for Wesnoth: I was active for a while on the forums, and again I mainly contributed ideas, especially in the domain of AMLA (units improving beyond their maximum XP level).

	'''''PATCH''''': I recently commited a small patch to add a new WML attribute (a tasked picked from the [[EasyCoding]] page). It's smallish and I'm not sure it shows anything about my abilities, but at least I managed to add a small feature in a clean way :). Please see https://gna.org/patch/index.php?1162		'''''PATCH''''': I recently commited a small patch to add a new WML attribute (a tasked picked from the [[EasyCoding]] page). It's smallish and I'm not sure it shows anything about my abilities, but at least I managed to add a small feature in a clean way :). Please see https://gna.org/patch/index.php?1162

	Irrlicht, Bullet: This is very light involvement, but I try to contribute back whatever I may need to fix in those open-source engines~~. For instance, I contributed a small patch (See: http://irrlicht.sourceforge.net/phpBB2/viewtopic.php?p=184440#184440) to Irrlicht to fix a bug in the Windows Mobile version~~.		Irrlicht, Bullet: This is very light involvement, but I try to contribute back whatever I may need to fix in those open-source engines.

	==Gaming experience==		==Gaming experience==

Gabba: /* Timeline */

2009-04-14T14:15:02Z

Timeline

← Older revision		Revision as of 14:15, 14 April 2009
Line 77:		Line 77:

	==Timeline==		==Timeline==
			''revised april 14th, 2009''

	I'll be working on this project from May 1st (or even possibly April 26th) to August 17st, for a total of 15 weeks. I may take one week off for vacations, but the exact date is to be determined.		I'll be working on this project from May 1st (or even possibly April 26th) to August 17st, for a total of 15 weeks. I may take one week off for vacations, but the exact date is to be determined.
Line 83:		Line 84:
	Here's the breakdown by week of how I plan the 15 weeks of this project:		Here's the breakdown by week of how I plan the 15 weeks of this project:

	'''''Week 1~~:''''' Setting up, compilation, technical problems. Explore the Wesnoth source code, hang out on forums and IRC to ask questions (which I'll keep doing the whole summer :P).~~		'''''Week 1-3:''''' Analysis and documentation of current save code. Getting in touch with all involved.
			*Deliverable: documented list of all save attributes
	~~'''''Weeks 2~~-3:''''' Analysis and documentation of current save code.

	'''''Weeks 4-6:''''' Design and prototypes; mid-term evaluation		'''''Weeks 4-6:''''' Design and prototypes; mid-term evaluation
			*Deliverable: detailed savegame format, and prototype of C++ refactoring

	'''''Weeks 7-10:''''' Implement Single ~~and multi~~-player using the new save code		'''''Weeks 7-10:''''' Implement Single-player using the new save code
			*Deliverable: saving/loading/replaying campaign scenarios works using the new save code
	~~'''''Weeks 11-14~~:~~''''' Implement campaigns and integrate everything.~~

	'''''~~Week 15~~:''''' ~~wrap up~~.		'''''Weeks 11-14:''''' Implement Multi-player using the new save code, and address side issues.
			*Deliverable: multiplayer campaigns and scenarios work using the new save code

			'''''Week 15:''''' Wrap up, write any missing documentation (but I'll document as I go).
			*Deliverable: final code and documentation

	==Technical Details==		==Technical Details==

Gabba at 08:35, 14 April 2009

2009-04-14T08:35:13Z

← Older revision		Revision as of 08:35, 14 April 2009
Line 1:		Line 1:
	'''''Hot off the press! Go look at the Technical Details section, I've made a major update.'''''		'''''Hot off the press! Go look at the Technical Details section, I've made a major update.'''''
			'''''Also look at the Open Source Involvement section, I've submitted a patch'''''

	==Introduction==		==Introduction==

Gabba at 08:34, 14 April 2009

2009-04-14T08:34:23Z

← Older revision		Revision as of 08:34, 14 April 2009
Line 38:		Line 38:

	==Open Source Involvement==		==Open Source Involvement==


	~~'''''EDIT: I plan to submit a patch, to solve the bug or implement the feature below; however, completing the technical proposal will take priority:'''''~~

	~~from EasyCoding:~~
	* fix bug #13268 (save corruption through undo/redo of recalls [https://gna.org/bugs/?13268]
	~~or the following from NotSoEasyCoding:~~
	* A change to allied healing - As proposed here: [http://www.wesnoth.org/forum/viewtopic.php?f=15&t=15880]
	~~'''''------------------------------------------------------------------------------'''''~~

	I got involved mostly in two open source projects: TA Spring and Battle for Wesnoth.		I got involved mostly in two open source projects: TA Spring and Battle for Wesnoth.
Line 53:		Line 44:

	Battle for Wesnoth: I was active for a while on the forums under the nickname 'gabba', and again I mainly contributed ideas, especially in the domain of AMLA (units improving beyond their maximum XP level).		Battle for Wesnoth: I was active for a while on the forums under the nickname 'gabba', and again I mainly contributed ideas, especially in the domain of AMLA (units improving beyond their maximum XP level).

			'''''PATCH''''': I recently commited a small patch to add a new WML attribute (a tasked picked from the [[EasyCoding]] page). It's smallish and I'm not sure it shows anything about my abilities, but at least I managed to add a small feature in a clean way :). Please see https://gna.org/patch/index.php?1162

	Irrlicht, Bullet: This is very light involvement, but I try to contribute back whatever I may need to fix in those open-source engines. For instance, I contributed a small patch (See: http://irrlicht.sourceforge.net/phpBB2/viewtopic.php?p=184440#184440) to Irrlicht to fix a bug in the Windows Mobile version.		Irrlicht, Bullet: This is very light involvement, but I try to contribute back whatever I may need to fix in those open-source engines. For instance, I contributed a small patch (See: http://irrlicht.sourceforge.net/phpBB2/viewtopic.php?p=184440#184440) to Irrlicht to fix a bug in the Windows Mobile version.

Gabba at 04:06, 14 April 2009

2009-04-14T04:06:39Z

← Older revision		Revision as of 04:06, 14 April 2009
Line 1:		Line 1:
	'''''~~Please note this is~~ a ~~work in progress~~. ~~I'll submit any changes before Monday, april 13th at 23:55 UTC~~'''''		'''''Hot off the press! Go look at the Technical Details section, I've made a major update.'''''

	==Introduction==		==Introduction==

Gabba: /* WML save format */

2009-04-14T04:05:14Z

WML save format

← Older revision		Revision as of 04:05, 14 April 2009
Line 356:		Line 356:
	# <nowiki>I don't know if a scenario or era can change in the course of a MP scenario; if so these tags would need to be in [start]/[snapshot] instead of [base]</nowiki>		# <nowiki>I don't know if a scenario or era can change in the course of a MP scenario; if so these tags would need to be in [start]/[snapshot] instead of [base]</nowiki>
	# <nowiki>[start]/[snapshot] would map well to the new merged </nowiki>''game_state ''<nowiki>object, but I'm not sure yet what [base] would map to.</nowiki>		# <nowiki>[start]/[snapshot] would map well to the new merged </nowiki>''game_state ''<nowiki>object, but I'm not sure yet what [base] would map to.</nowiki>
	# This whole structure is designed assuming the basic philosophy of duplicating everything that might change; it would be much more elegant and simple if we decided to store only information that changed compared to the base value. Early into the Summer of Code, I'll design an alternate outline using that method, so we ~~kind~~ look at both alternatives.		# This whole structure is designed assuming the basic philosophy of duplicating everything that might change; it would be much more elegant and simple if we decided to store only information that changed compared to the base value. Early into the Summer of Code, I'll design an alternate outline using that method, so we can look at both alternatives.

Gabba: /* WML save format */

2009-04-14T04:02:20Z

WML save format

← Older revision		Revision as of 04:02, 14 April 2009
Line 315:		Line 315:

	In the meanwhile however, here's what I have in mind for the general outline, taking as a base mordante's proposal. Note that his proposal includes using the savegame as the way of transmitting scenarios to other players in mp; I've removed some things related to this purpose, since I haven't had the time to study that aspect of the problem.		In the meanwhile however, here's what I have in mind for the general outline, taking as a base mordante's proposal. Note that his proposal includes using the savegame as the way of transmitting scenarios to other players in mp; I've removed some things related to this purpose, since I haven't had the time to study that aspect of the problem.


			<center><b>Proposed WML Savegame Structure</b></center>


Line 325:		Line 328:
	** ''<nowiki>[scenario]</nowiki>''		** ''<nowiki>[scenario]</nowiki>''
	*** in SP, contains, among other things:		*** in SP, contains, among other things:
	**** scenario_id		**** ''scenario_id''
	**** gold_min_start & gold_carryover_percent		**** ''gold_min_start'' & ''gold_carryover_percent''
	*** in MP, additionally contains the scenario data.		*** in MP, additionally contains the scenario data.
	** ''<nowiki>[campaign] </nowiki>''contains campaign settings that won't change, such as the attributes: campaign, campaign_type, campaign_define)		** ''<nowiki>[campaign] </nowiki>''contains campaign settings that won't change, such as the attributes: campaign, campaign_type, campaign_define)
Line 346:		Line 349:
	* ''<nowiki>[replay]</nowiki>'' same as current		* ''<nowiki>[replay]</nowiki>'' same as current
	* ''<nowiki>[statistics]</nowiki>'' same as current		* ''<nowiki>[statistics]</nowiki>'' same as current



	Notes:		Notes:

Gabba: /* Technical Details */

2009-04-14T03:58:15Z

Technical Details

Show changes