MP Server Ilor - Revision history

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

2013-03-21T01:12:40Z

Hide historical references to Subversion from the wiki search function

Ilor: /* Overview */

2009-08-25T16:38:40Z

‎Overview

Ilor: added overview

2009-08-25T16:36:04Z

added overview

Ilor: /* Summary */ fix wiki markup fail

2009-08-18T16:36:59Z

‎Summary: fix wiki markup fail

Ilor: end-of-project update

2009-08-18T16:36:28Z

end-of-project update

SkeletonCrew: /* Blockers */ Updated the bug status

2009-08-16T14:07:10Z

‎Blockers: Updated the bug status

Ilor at 21:32, 6 August 2009

2009-08-06T21:32:07Z

Ilor at 17:54, 6 August 2009

2009-08-06T17:54:04Z

Ilor: /* Goals */

2009-07-31T18:02:13Z

‎Goals

Ilor: /* Goals */

2009-07-28T22:10:23Z

‎Goals

@@ Line 325: / Line 325: @@
 ==Practical considerations==
-I have good knowledge of C++ (and STL), I'm moderately familiar with the Wesnoth codebase and I started to look into wesnothd sources. I learned C++ pretty much on my own, first by coding small problems for some local programming/algorithm contests. I even got to the country finals once, though I'm not a huge fan of 5-hour "reimplement the appropriate algorithm in each of the problems" events. At least this made me pay attention to computational etc. complexity issues. Later I got some more useful knowledge from various books and experimenting. I'm comfortable with Subversion and intent on finally trying git-svn. I develop mainly on windows on MSVC but can switch to linux if it turns out toying with wesnothd is problematic on windows.
+I have good knowledge of C++ (and STL), I'm moderately familiar with the Wesnoth codebase and I started to look into wesnothd sources. I learned C++ pretty much on my own, first by coding small problems for some local programming/algorithm contests. I even got to the country finals once, though I'm not a huge fan of 5-hour "reimplement the appropriate algorithm in each of the problems" events. At least this made me pay attention to computational etc. complexity issues. Later I got some more useful knowledge from various books and experimenting. I'm comfortable with Sub&shy;&shy;version and intent on finally trying git-s&shy;&shy;v&shy;&shy;n. I develop mainly on windows on MSVC but can switch to linux if it turns out toying with wesnothd is problematic on windows.
 I use MSVC mainly because it's a powerful and helpful tool, though not without defects. I also use a lightweight smart text editor (notepad++) for general editing. Cygwin, putty, wireshark are some useful tools I use quite often.

@@ Line 5: / Line 5: @@
 ** More chat space with new whisper/room interface
 ** More general flexibility -- many aspects can be changed in WML without having to rebuild
-* to add a room system to the Wesnoth server, similar to IRC channels. It is working, however only the experimental lobby has a convenient interface for it.
+* to add a room system to the Wesnoth server, similar to IRC channels. It is working, however only the experimental lobby has a convenient interface for it. See [[MultiplayerRooms]].
 * to offload some random number generation to the server to prevent cheating. Combats now rely on a random number provided by the server which is generated after the decision to attack has been made.
 * to simplify server moderation by allowing server mnods to isue commands without having the game launched. While less interesting for players, this too has been done (with a big "thanks" to Soliton) and is working fine.

← Older revision		Revision as of 16:36, 25 August 2009
Line 1:		Line 1:
−	~~Note~~: This project ~~was accepted into GSoC 2009~~.	+	==Overview==
		+	The "Multiplayer Improvements" Wesnoth project for Google Summer of Code has been completed. The main objectives of the project were:
		+	* to create a new lobby interface using the new widget toolkit being developed by Mordante. This new interface is functional, but still marked as experimental due to some unresolved issues. Improvements in the new lobby include:
		+	** More compact game list
		+	** More chat space with new whisper/room interface
		+	** More general flexibility -- many aspects can be changed in WML without having to rebuild
		+	* to add a room system to the Wesnoth server, similar to IRC channels. It is working, however only the experimental lobby has a convenient interface for it.
		+	* to offload some random number generation to the server to prevent cheating. Combats now rely on a random number provided by the server which is generated after the decision to attack has been made.
		+	* to simplify server moderation by allowing server mnods to isue commands without having the game launched. While less interesting for players, this too has been done (with a big "thanks" to Soliton) and is working fine.
		+
		+	The results of the project can be seen in Wesnoth 1.7.3, to see the new lobby the --new-widgets command line switch must be used. Once the new lobby is declared stable, it will replace the old one and the switch will not be needed.
		+	__TOC__

	==About me==		==About me==

@@ Line 309: / Line 309: @@
 Regarding non-UI parts of the project:
- * the room system on the server works, but might need additional tests and tweaks as it gets used
+* the room system on the server works, but might need additional tests and tweaks as it gets used
- * basic server side RNG works, switching all MP random number generation to the server-based method is an objective for 1.8, as is some documentationa s to how the system actually works, which is sadly missing at the time. Expect it at [[Server RNG]].
+* basic server side RNG works, switching all MP random number generation to the server-based method is an objective for 1.8, as is some documentationa s to how the system actually works, which is sadly missing at the time. Expect it at [[Server RNG]].
- * wesnothd-less moderation (lobby bot improvements) turned out to require only adapting existing code to expose more features and use more of what irc offers
+* wesnothd-less moderation (lobby bot improvements) turned out to require only adapting existing code to expose more features and use more of what irc offers
 ==Practical considerations==

@@ Line 108: / Line 108: @@
 * August 15 (before final evaluations) - have a polished new lobby plus the game-less moderation feature.
 ====Goals====
 {| border="1"
 ! ID
@@ Line 271: / Line 272: @@
 | <p style="color:blue">OPTIONAL</p>
 | If the prototype is successful, wire all random numbers to use it, make it robust.
-| 20% groundwork laid
+| 20% groundwork laid, delayed
 |-
 | 20
@@ Line 277: / Line 278: @@
 | <p style="color:red">MANDATORY</p>
 | Touch up various areas of the code, especially make sure the gui behaves nicely.
-| 50%
+| done as far as feasible, ready for more testing
 |-
 | -
@@ Line 283: / Line 284: @@
 | <p style="color:green">MILESTONE</p>
 | Have the project in a working and polished state by August <strike>15</strike> 10.
-| looking good
+| done
 |}
@@ Line 294: / Line 295: @@
 ===Important===
-* [M/I] Vertical layout jumpiness (stuff changes size as more games appear and more chat lines are in the log)
+* [M/I] Vertical layout jumpiness (stuff changes size as more games appear and more chat lines are in the log). Alleviated somewhat, but not perfect.
 * [M] Tooltips don't work for icons inside a toggle panel
-* [I] Room system needs docs and testing
+* [I] Room system needs docs and testing [see [[MultiplayerRooms]] for the docs]
 ===Other===
 * [M] A wrapping widget container would allow some nice layout effects
-* [I/O] Some icons desperately need changing
+* [I/O] Some icons desperately need changing [done in 1.7.3]
 * [M] Buttons working inside a toggle panel would be nice
 * [M] Scrollbars can appear for no particular reason
 * [M/I] Not everything is tweakable in WML - color/formatting for friends, game status, some icons etc
 ==Practical considerations==

@@ Line 289: / Line 289: @@
 [M] - Mordante, [I] - Ilor, [O] - other people
 ===Blockers===
-* [M] The mouse focus dynamic cast fail (tm) discovered by Soliton. Confirmed and being worked on by Mordante
+* [M] The mouse focus dynamic cast fail (tm) discovered by Soliton. Confirmed and being worked on by Mordante [Fixed in 1.7.3]
-* [I/M] The log in to trunk, try logging into 1.7 server assert discovered by me, I need to get more info as it seems difficult to reproduce.
+* [I/M] The log in to trunk, try logging into 1.7 server assert discovered by me, I need to get more info as it seems difficult to reproduce. [Fixed in 1.7.3]
 * [M] Resizing is not reliable, resizing down can result in an exception and a drop to titlescreen if there's not enough space; resizing up can create garbage in the output (at least on winxp). Mordante notified and working on fix.
 ===Important===
 * [M/I] Vertical layout jumpiness (stuff changes size as more games appear and more chat lines are in the log)

@@ Line 1: / Line 1: @@
-Note: Theis project was accepted into GSoC 2009.
+Note: This project was accepted into GSoC 2009.
 ==About me==
@@ Line 287: / Line 287: @@
 ==Remaining issues==
 ===Blockers===
-* The mouse focus dynamic cast fail (tm) discovered by Soliton. Confirmed and being worked on by Mordante
+* [M] The mouse focus dynamic cast fail (tm) discovered by Soliton. Confirmed and being worked on by Mordante
-* The log in to trunk, try logging into 1.7 server assert discovered by me, I need to get more info as it seems difficult to reproduce.
+* [I/M] The log in to trunk, try logging into 1.7 server assert discovered by me, I need to get more info as it seems difficult to reproduce.
-* Resizing is not reliable, resizing down can result in an exception and a drop to titlescreen if there's not enough space; resizing up can create garbage in the output (at least on winxp). Mordante notified and working on fix.
+* [M] Resizing is not reliable, resizing down can result in an exception and a drop to titlescreen if there's not enough space; resizing up can create garbage in the output (at least on winxp). Mordante notified and working on fix.
 ===Important===
-* Vertical layout jumpiness (stuff changes size as more games appear and more chat lines are in the log)
+* [M/I] Vertical layout jumpiness (stuff changes size as more games appear and more chat lines are in the log)
-* Tooltips don't work for icons inside a toggle panel
+* [M] Tooltips don't work for icons inside a toggle panel
-* Room system needs docs and testing
+* [I] Room system needs docs and testing
 ===Other===
-* A wrapping widget container would allow some nice layout effects
+* [M] A wrapping widget container would allow some nice layout effects
-* Some icons desperately need changing
+* [I/O] Some icons desperately need changing
-* Buttons working inside a toggle panel would be nice
+* [M] Buttons working inside a toggle panel would be nice
-* Scrollbars can appear for no particular reason
+* [M] Scrollbars can appear for no particular reason
-* Not everything is tweakable in WML - color/formatting for friends, game status, some icons etc
+* [M/I] Not everything is tweakable in WML - color/formatting for friends, game status, some icons etc
 ==Practical considerations==

@@ Line 1: / Line 1: @@
-'''Updated''' on April 21st -- the project was accepted into GSoC 2009
+Note: Theis project was accepted into GSoC 2009.
 ==About me==
 My name is Tomasz Śniatowski, ilor on irc/gna/forums/wiki, I'm a third year software engineering student in the Wroclaw University of Technology in Poland. My preferred e-mail adress is kailoran(at]gmail.com
@@ Line 195: / Line 191: @@
 | <p style="color:red">MANDATORY</p>
 | Write the new game list as outlined in the proposal, with emphasis on being more space-efficient. No filters here.
-| done
+| done (two modes idea delayed for now)
 |-
 | 10
@@ Line 213: / Line 209: @@
 | <p style="color:blue">OPTIONAL</p>
 | Write more game list filters like filtering by era, filtering by eras the player has, text-matching for stuff beyond the game name etc. plus a fancy interface for it.
-| delayed, 20%
 |-
 | 12
@@ Line 267: / Line 265: @@
 | <p style="color:blue">OPTIONAL</p>
 | Write a proper bot or bot-like feature that will recognize moderators on IRC and allow them to moderate easily.
-| 50% (needs testing, posibly more logging)
+| done
 |-
 | 19
@@ Line 279: / Line 277: @@
 | <p style="color:red">MANDATORY</p>
 | Touch up various areas of the code, especially make sure the gui behaves nicely.
-| 5% (made a todo list)
+| 50%
 |-
 | -
 | <b>4th milestone (final)</b>
 | <p style="color:green">MILESTONE</p>
-| Have the project in a working and polished state by August 15.
+| Have the project in a working and polished state by August <strike>15</strike> 10.
 | looking good
 |}
 ==Practical considerations==

@@ Line 135: / Line 135: @@
 | <p style="color:blue">OPTIONAL</p>
 | Look into being able to show gui2 widgets as tooltips (i.e. not just text). Optional, since it'd be nice to have but nothing will rely heavily on it.
-| delayed
+| skipped
 |-
 | 3
@@ Line 213: / Line 213: @@
 | <p style="color:blue">OPTIONAL</p>
 | Write more game list filters like filtering by era, filtering by eras the player has, text-matching for stuff beyond the game name etc. plus a fancy interface for it.
-| 20%
+| delayed, 20%
 |-
 | 12
@@ Line 237: / Line 237: @@
 | <p style="color:blue">OPTIONAL</p>
 | Implement the swicthing between "more games, less chat" and "less games, more chat" idea.
-| none
+| 0%, delayed
 |-
 | 16
@@ Line 243: / Line 243: @@
 | <p style="color:red">MANDATORY</p>
 | Write a simple RNG service in wesnothd. Write a simple server-rng-using RNG in the client. Wire it up to do combats and test. If not feasible, write a descriription of the problems encountered.
-| 80% combats wired in, needs testing
+| done
 |-
 | 16.5
@@ Line 249: / Line 249: @@
 | <p style="color:blue">OPTIONAL</p>
 | Clean up what the server sends to the client esp. in regard to game info to avoid some pointless tricks
-| none
+| 0%, delayed
 |-
 | -
@@ Line 255: / Line 255: @@
 | <p style="color:green">MILESTONE</p>
 | Have the above done by July 26. There are a lot of "optional" features there -- at least one of those should be finished.
-| on track
+| done
 |-
 | 17