Fosdem2011 - Revision history

Esr: Retroactively stop being SVN-specific to cut down on false positives in searches.

2013-03-20T17:43:47Z

Retroactively stop being SVN-specific to cut down on false positives in searches.

Ivanovic: /* Khalifate / New faction for mainline */

2011-02-07T19:06:04Z

‎Khalifate / New faction for mainline

Ivanovic: /* Discussions in sub groups */

2011-02-07T11:14:31Z

‎Discussions in sub groups

Crab: /* multiplayer chat log */

2011-02-07T11:08:52Z

‎multiplayer chat log

Crab: /* multiplayer chat log */

2011-02-07T11:07:59Z

‎multiplayer chat log

Crab: /* fendrin_pathfind branch */

2011-02-07T11:03:26Z

‎fendrin_pathfind branch

Crab: /* Discussions and Results */

2011-02-07T10:54:23Z

‎Discussions and Results

Ivanovic: /* Discussions in sub groups */

2011-02-07T10:49:03Z

‎Discussions in sub groups

Ivanovic: /* Discussions and Results */ add a "discussions in smaller groups" section

2011-02-07T10:31:36Z

‎Discussions and Results: add a "discussions in smaller groups" section

Espreon: /* Wesnoth 1.10 */

2011-02-07T10:26:08Z

‎Wesnoth 1.10

@@ Line 161: / Line 161: @@
 ==== fendrin_pathfind branch ====
 We wanted  fendrin_pathfind branch, containing a [tunnel] feature which allows to customize teleports, to be committed to trunk. but, before that could happen, we needed to benchmark the new pathfinding performance.
-It was done on AI0867's machine using Crab's batch ai testing script (written in python, present in svn in utils/ai_test) slightly modified from the original to log to file instead of logging to postgresql database. The results were:
+It was done on AI0867's machine using Crab's batch ai testing script (written in python, present in the repo in utils/ai_test) slightly modified from the original to log to file instead of logging to postgresql database. The results were:
   taking startup time into account

@@ Line 115: / Line 115: @@
 Users in IRC raised concerns regarding the balancing (mentioned above already, it won't be perfect at the start and has to improve over time, but requires lots of playtesting to do so), creation of the unit cfgs (should be done in about an hour, once we got the actual values!) as well as the Khalifate being too "real world" (are they really some "real world stuff"? Personally some Arabic/Mongolian themed stuff does fit nicely into a game like Wesnoth, too.
-Basic result of the discussion with the devs that were around at FOSEM was that it should be in trunk as soon as possible, so that it might be already available in the next dev release 1.9.5.
+Basic result of the discussion with the devs that were around at FOSEM was that it should be in trunk as soon as possible, so that it might be already available in the next dev release 1.9.5. Via IRC noy mentioned that final work for inclusion of this line is started and the initial unit stats might be ready for upload to trunk in about one or two weeks (rough estimate only!).
 ===Licensing problems===

← Older revision		Revision as of 11:14, 7 February 2011
Line 171:		Line 171:

	based on those results, the branch was committed to trunk.		based on those results, the branch was committed to trunk.
		+
		+	====Another 1.8.x release====
		+	Due to the release of 1.10 being "far off" deekay asked Ivanovic if it would be a good idea to release another 1.8.x release fixing the bugs that are at least "rather annoying". Ivanovic agreed that this would make sense, so once the stuff is backported/fixed, a 1.8.6 release is planned. This might be some time late in February or early in March and is not 100% scheduled so far. Ivanovic will also try to make sure that the translation teams as well as the other devs are aware of this planned stable release.

	====more discussions wanted====		====more discussions wanted====

@@ Line 157: / Line 157: @@
 ==== multiplayer chat log ====
-Dragonking has highlighted several problems in current 'chat log history' dialog (crashing, no color highlighting) which are important for MP players. The solution that we talked about is to rewrite 'chat log history' dialog gui2. Crab has quickly coded a prototype of that dialog, with proper coloring of nicknames. To avoid the 'crash' part, we need to add pagination support for this new dialog. It is intended that this dialog would be backported to 1.8, since the 1.10 is still too far away and it would be really nice to have this feature in MP.
+Dragonking has highlighted several problems in current 'chat log history' dialog (crashing, no color highlighting). Fixes for those are important for MP players. The solution that we talked about is to rewrite 'chat log history' dialog gui2. Crab has quickly coded a prototype of that dialog, with proper coloring of nicknames. To avoid the 'crash' part, we need to add pagination support for this new dialog. It is intended that this dialog would be backported to 1.8, since the 1.10 is still too far away and it would be really nice to have this feature in MP.
 ==== fendrin_pathfind branch ====

@@ Line 157: / Line 157: @@
 ==== multiplayer chat log ====
 ==== fendrin_pathfind branch ====
 We wanted  fendrin_pathfind branch, containing a [tunnel] feature which allows to customize teleports, to be committed to trunk. but, before that could happen, we needed to benchmark the new pathfinding performance.

← Older revision		Revision as of 10:54, 7 February 2011
Line 156:		Line 156:
	gnutoo (who is also around in IRC every now and then) visited us in the (Wesnoth) Hacking Room. With him he brought some Linux based mobile devices. One of the devices was a N900 with an 800x480 screen and specs rather similar to the OpenPandora (Ivanovic is creating packages for this device). Wesnoth seems to run nicely on this one, though the screen is even smaller (~3" on the N900 vs 4.3" on the OpenPandora) so using it (only with the touchscreen) is even more difficult. He also brought a phone with some "smaller" screen running some Wesnoth version that had rely on tinygui. It looked really tiny and had (again) severe graphic problems. Because it is de facto not supported by any dev and tends to break regularly (if things get fixed at all!) Ivanovic proposes the complete removal of tinygui. This would (for the moment) mean that support for any resolutions <800x480 would be gone (currently it is rather hackish anyway). Mordante mentioned that once everything is converted to GUI2 (no timeline available for this task!) it should be possible to do the whole gui stuff in a more sane way so that it does work nicely for "really small resolutions", too. Once we have some OpenGL support added (yeah, once we find someone to actually do the job, the move to OpenGL is still a plan) it should also be possible to implement some "better" zooming that helps modern day devices to increase/decrease size as it fits.		gnutoo (who is also around in IRC every now and then) visited us in the (Wesnoth) Hacking Room. With him he brought some Linux based mobile devices. One of the devices was a N900 with an 800x480 screen and specs rather similar to the OpenPandora (Ivanovic is creating packages for this device). Wesnoth seems to run nicely on this one, though the screen is even smaller (~3" on the N900 vs 4.3" on the OpenPandora) so using it (only with the touchscreen) is even more difficult. He also brought a phone with some "smaller" screen running some Wesnoth version that had rely on tinygui. It looked really tiny and had (again) severe graphic problems. Because it is de facto not supported by any dev and tends to break regularly (if things get fixed at all!) Ivanovic proposes the complete removal of tinygui. This would (for the moment) mean that support for any resolutions <800x480 would be gone (currently it is rather hackish anyway). Mordante mentioned that once everything is converted to GUI2 (no timeline available for this task!) it should be possible to do the whole gui stuff in a more sane way so that it does work nicely for "really small resolutions", too. Once we have some OpenGL support added (yeah, once we find someone to actually do the job, the move to OpenGL is still a plan) it should also be possible to implement some "better" zooming that helps modern day devices to increase/decrease size as it fits.

		+	==== multiplayer chat log ====
		+	==== fendrin_pathfind branch ====
	====more discussions wanted====		====more discussions wanted====

@@ Line 152: / Line 152: @@
 ====Easing the use of lazy loading/modding====
 Currently at game start a whole lot of content has to be parsed. For the campaigns we do rely on a system where we only parse the _main.cfg file and the rest later on when the campaign and the wanted difficulty level were selected. The idea is that adding a general config block (maybe some "manifest" file) would help to provide the basic list that should be fast to parse and keep in memory. This manifest file would work similar to the current _main.cfg files. It could provide some basic information that is always required, even if you don't start the stuff and it would include a type entry plus possibly dependencies on content. A later step could be offering some "module manager" where you select which things you do want to have active. So that you maybe don't want all the addons you downloaded available from the start. Or that you want to use a conversion of the ruleset to do some strange things. Part of this discussion were chrber, fendrin, Ivanovic, Mordante, YogiHH and possibly several others.
 ====more discussions wanted====

@@ Line 99: / Line 99: @@
 == Discussions and Results ==
-We usually discuss all sorts of things at FOSDEM, this section is basically a (really short) summary of things that were discussed including their results.
+We usually discuss all sorts of things at FOSDEM, this section is basically a (really short) summary of things that were discussed including their results. First are the discussions that were done "in plenum" with basically all attendees around. At the bottom is an area meant for discussions that were held in sub groups that not all devs might be aware of that were around.
 ===FOSDEM 2012===
@@ Line 148: / Line 148: @@
 ===Wesnoth 1.10===
 So far there was no decision when to release the next stable release. Since we want to participate in GSOC and students are meant to directly commit their work to trunk and it has to be open for "new stuff". After GSOC we also need some time to fix bugs and polish new things, so the current idea is the next stable should be created around Christmas. In general we cannot release 1.10 anytime close since it is not as stable as we would require it (just have a look at the amounts of bugs currently reported in the tracker!). So the next month should also be used for polishing as well as adding new stuff.
 == Group Picture ==