SummerOfCodeProposal Billynux - Revision history

Egallager: link cleanup

2023-05-03T04:17:58Z

link cleanup

Egallager: link cleanup

2023-04-18T06:19:05Z

link cleanup

Egallager: fix heading levels

2023-04-18T06:17:18Z

fix heading levels

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

2013-03-21T01:45:03Z

Hide historical references to Subversion from the wiki search function

Billynux at 18:46, 21 April 2010

2010-04-21T18:46:19Z

Billynux at 01:16, 21 April 2010

2010-04-21T01:16:06Z

Billynux at 01:14, 21 April 2010

2010-04-21T01:14:56Z

Billynux at 18:51, 19 April 2010

2010-04-19T18:51:16Z

Billynux at 00:37, 16 April 2010

2010-04-16T00:37:17Z

Billynux at 07:35, 15 April 2010

2010-04-15T07:35:59Z

@@ Line 22: / Line 22: @@
 <b>Revision 1</b> : April 13 - Added two sections:
-* [http://wiki.wesnoth.org/index.php?title=SummerOfCodeProposal_Billynux#Additional_Technical_Information Additional Technical Information] : Information about documentation procedures and tools of the different sub-projects.
+* [[SummerOfCodeProposal_Billynux#Additional_Technical_Information|Additional Technical Information]]: Information about documentation procedures and tools of the different sub-projects.
-* [http://wiki.wesnoth.org/index.php?title=SummerOfCodeProposal_Billynux#Technical_considerations_regarding_boost::asio Technical Considerations Regarding boost::asio] : Technical aspects relevant to implementing the network code using boost::asio.
+* [[SummerOfCodeProposal_Billynux#Technical_considerations_regarding_boost::asio|Technical Considerations Regarding boost::asio]]: Technical aspects relevant to implementing the network code using boost::asio.
-<b>Revision 2</b> : April 15 - Updated the [http://wiki.wesnoth.org/SummerOfCodeProposal_Billynux#4.4.29_Include_an_estimated_timeline_for_your_work_on_the_project._Don.27t_forget_to_mention_special_things_like_.22I_booked_holidays_between_A_and_B.22_and_.22I_got_an_exam_at_ABC_and_won.27t_be_doing_much_then.22. timeline] with milestones and added three sections:
+<b>Revision 2</b> : April 15 - Updated the [[SummerOfCodeProposal_Billynux#4.4.29_Include_an_estimated_timeline_for_your_work_on_the_project._Don.27t_forget_to_mention_special_things_like_.22I_booked_holidays_between_A_and_B.22_and_.22I_got_an_exam_at_ABC_and_won.27t_be_doing_much_then.22.|timeline]] with milestones and added three sections:
 * This Changelog.
-* [http://wiki.wesnoth.org/SummerOfCodeProposal_Billynux#Current_Network_Dynamics Current Network Dynamics] : Explaining how data is sent using the current network module and how will this change with the new implementation.
+* [[SummerOfCodeProposal_Billynux#Current_Network_Dynamics|Current Network Dynamics]]: Explaining how data is sent using the current network module and how will this change with the new implementation.
-* [http://wiki.wesnoth.org/SummerOfCodeProposal_Billynux#Compatibility_Issues Compatibility Issues] : Explaining why backwards compatibility won't be a problem.
+* [[SummerOfCodeProposal_Billynux#Compatibility_Issues|Compatibility Issues]]: Explaining why backwards compatibility won't be a problem.
 <b>Revision 3</b> : April 15 - After interview, Crab added a bug [http://svn.gna.org/viewcvs/wesnoth?view=rev&rev=42139 fix] as the result of it including code by me with a simple work-around.
-<b>Revision 4</b> : April 19 - Updated the [http://wiki.wesnoth.org/SummerOfCodeProposal_Billynux#2.6.29_If_you_have_contributed_any_patches_to_Wesnoth.2C_please_list_them_below._You_can_also_list_patches_that_have_been_submitted_but_not_committed_yet_and_patches_that_have_not_been_specifically_written_for_GSoC._If_you_have_gained_commit_access_to_our_SVN_.28during_the_evaluation_period_or_earlier.29_please_state_so. section] about contributions to Wesnoth.
+<b>Revision 4</b> : April 19 - Updated the [[SummerOfCodeProposal_Billynux#2.6.29_If_you_have_contributed_any_patches_to_Wesnoth.2C_please_list_them_below._You_can_also_list_patches_that_have_been_submitted_but_not_committed_yet_and_patches_that_have_not_been_specifically_written_for_GSoC._If_you_have_gained_commit_access_to_our_SVN_.28during_the_evaluation_period_or_earlier.29_please_state_so.|section]] about contributions to Wesnoth.
-<b>Revision 5</b> : April 20 - Included a [http://wiki.wesnoth.org/index.php?title=SummerOfCodeProposal_Billynux#The_Latest_Prototype section] describing the new [http://code.google.com/p/async-net-api/ prototype], it features an incomplete, simple and naive interface, an initial (and a bit buggy) implementation featuring boost::asio and a sample chat application that uses it.
+<b>Revision 5</b> : April 20 - Included a [[SummerOfCodeProposal_Billynux#The_Latest_Prototype|section]] describing the new [http://code.google.com/p/async-net-api/ prototype], it features an incomplete, simple and naive interface, an initial (and a bit buggy) implementation featuring boost::asio and a sample chat application that uses it.
 <b>Revision 6</b> : April 21 - Cleanup up the new [http://code.google.com/p/async-net-api/ prototype]. It now features simple interfaces for event handling.

@@ Line 213: / Line 213: @@
 <h4>4.5) Include as much technical detail about your implementation as you can</h4>
-See [http://wiki.wesnoth.org/SummerOfCodeProposal_Billynux#6.29_Answers answers] to the questions below.
+See [[SummerOfCodeProposal_Billynux#6.29_Answers|answers]] to the questions below.
 <h4>4.6) What do you expect to gain from this project?</h4>
@@ Line 364: / Line 364: @@
 <h4>The API's implementation documentation</h4>
-Documentation of this implementation will be that of a standard Doxygen project with many sources. I plan to use Wesnoth's coding [http://wiki.wesnoth.org/CodingStandards standards] both in the overall C++  implementation along with the style used throughout Doxygen.
+Documentation of this implementation will be that of a standard Doxygen project with many sources. I plan to use Wesnoth's coding [[CodingStandards|standards]] both in the overall C++  implementation along with the style used throughout Doxygen.
 <h4>The Wesnoth's network code documentation</h4>

@@ Line 2: / Line 2: @@
 [[Category:SoC Ideas Network Stack Rewrite]]
-= Description =
+== Description ==
 <h4> Billynux - Rewrite Wesnoth network stack using boost::asio </h4>
-email : billybiset@gmail.com
+* email : billybiset@gmail.com
-irc : billynux
+* irc : billynux
-gna.org : billynux
+* gna.org : billynux
 The project consists of developing a network framework in the form of an API and subsequently an implementation that can be distributed as a library for the development of client/server applications. This library will be used to implement Wesnoth's network stack.
-=IRC=
+==IRC==
 billynux
-=SoC Application=
+==SoC Application==
 [http://socghop.appspot.com/gsoc/student_proposal/review/google/gsoc2010/billynux/t127072324332 Rewriting Battle for Wesnoth network stack using boost::asio.]
-= Changelog =
+== Changelog ==
 <b>Revision 0</b> : April 9  - Initial Wiki page for application deadline.
@@ Line 38: / Line 38: @@
 <b>Revision 6</b> : April 21 - Cleanup up the new [http://code.google.com/p/async-net-api/ prototype]. It now features simple interfaces for event handling.
-= Questionnaire =
+== Questionnaire ==
 Crab uploaded a bug [http://svn.gna.org/viewcvs/wesnoth?view=rev&rev=42139 fix]
@@ Line 326: / Line 326: @@
 Also, a lot of testing must be carried out. However, testing code while playing doesn't sound so bad :)
-= Additional Technical Information =
+== Additional Technical Information ==
 <h3>Documentation</h3>
@@ Line 370: / Line 370: @@
 According to the aforementioned standards in current Wesnoth code.
-= Technical considerations regarding boost::asio =
+== Technical considerations regarding boost::asio ==
 <h3>Client Types</h3>
@@ Line 413: / Line 413: @@
 Any compression/decompression of data can be taken care both at the application level or the network level. Neither one will know if the other compressed its data, i.e. the application doesn't need to know if the sender will pack the data for sending and the sender won't know anything about the data it is to send. Both approaches should be considered.
-= Current Network Dynamics =
+== Current Network Dynamics ==
 In this section I give a brief explanation of the current dynamics of the network module while properly sending information to a connected component. Many details are omitted, but this overview should help understand its general current operation.
@@ Line 440: / Line 440: @@
 Many of these features can be seen functioning in my [http://code.google.com/p/fud/source/browse/#svn/trunk/sandbox/asio prototype].
-= Compatibility Issues =
+== Compatibility Issues ==
 It is a requirement of the implementation that there is backwards compatibility between both implementations of the network module. Luckily, this isn't a big issue, [http://sdl.beuc.net/sdl.wiki/SDLNet_Write32 SDLNet_Write32] just copies a uint32_t unsigned integer (defined in <stdint.h>) to a char buffer, this can be done with a C++ line as follows:
@@ Line 454: / Line 454: @@
 Overall, I see no issues in having backwards compatibility.
-= The Latest Prototype =
+== The Latest Prototype ==
 I uploaded a new [http://code.google.com/p/async-net-api/ prototype] to a GoogleCode repository. It is meant as a Proof Of Concept of the work that has to be done. It lacks several things, however it shows how easy it will be to implement simple Server/Client applications further on.

@@ Line 86: / Line 86: @@
 <h4>2.2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)</h4>
-Yes, right now the work on FuD involves about 15 people and I'm actually running the project. Without svn it couldn't be possible. The project with sipXtapi and asterisk involved many people (> 20).
+Yes, right now the work on FuD involves about 15 people and I'm actually running the project. Without s&shy;&shy;v&shy;&shy;n it couldn't be possible. The project with sipXtapi and asterisk involved many people (> 20).
 <h4>2.3) Have you participated to the Google Summer of Code before? As a mentor or a student? In what project? Were you successful? If not, why?</h4>
@@ Line 120: / Line 120: @@
 I have just started playing Wesnoth and gone through the tutorial and basic campaigns. I really prefer multiplayer for any game.
-<h4>2.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our SVN (during the evaluation period or earlier) please state so.</h4>
+<h4>2.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our S&shy;&shy;V&shy;&shy;N (during the evaluation period or earlier) please state so.</h4>
 After an interview with Crab, he added a bug [http://svn.gna.org/viewcvs/wesnoth?view=rev&rev=42139 fix] as the result of it, including code by me with a simple work-around.
@@ Line 226: / Line 226: @@
 <h4>5.1) Are you familiar with any of the following tools or languages?</h4>
-     * Subversion (used for all commits)
+     * Sub&shy;&shy;version (used for all commits)
 Yes. I use it daily.
      * C++ (language used for all the normal source code)

← Older revision		Revision as of 18:46, 21 April 2010
Line 35:		Line 35:

	<b>Revision 5</b> : April 20 - Included a [http://wiki.wesnoth.org/index.php?title=SummerOfCodeProposal_Billynux#The_Latest_Prototype section] describing the new [http://code.google.com/p/async-net-api/ prototype], it features an incomplete, simple and naive interface, an initial (and a bit buggy) implementation featuring boost::asio and a sample chat application that uses it.		<b>Revision 5</b> : April 20 - Included a [http://wiki.wesnoth.org/index.php?title=SummerOfCodeProposal_Billynux#The_Latest_Prototype section] describing the new [http://code.google.com/p/async-net-api/ prototype], it features an incomplete, simple and naive interface, an initial (and a bit buggy) implementation featuring boost::asio and a sample chat application that uses it.
		+
		+	<b>Revision 6</b> : April 21 - Cleanup up the new [http://code.google.com/p/async-net-api/ prototype]. It now features simple interfaces for event handling.

	= Questionnaire =		= Questionnaire =