56 * Implement preferences/options in the Android port, basically allow the existing preferences options from the desktop version to the port using Android shared preferences. |
56 * Implement preferences/options in the Android port, basically allow the existing preferences options from the desktop version to the port using Android shared preferences. |
57 * Sometimes you exit the game for a mistake and that's sad! Add a quick resume button to the game configuration for both local and network games. |
57 * Sometimes you exit the game for a mistake and that's sad! Add a quick resume button to the game configuration for both local and network games. |
58 * Turn savefiles compatible between iOS and desktop format. This involves getting familiar with engine protocol and keybind interaction. |
58 * Turn savefiles compatible between iOS and desktop format. This involves getting familiar with engine protocol and keybind interaction. |
59 * When you download something from our DLC page, you usually have to restart the game to load the new contents. Propagate the right signals so that it gets loaded automatically and don't have to restart the game. |
59 * When you download something from our DLC page, you usually have to restart the game to load the new contents. Propagate the right signals so that it gets loaded automatically and don't have to restart the game. |
60 * Drop a shadow effect to every widget in our frontend. This will help you: http://doc.qt.nokia.com/stable/qgraphicsdropshadoweffect.html |
60 * Drop a shadow effect to every widget in our frontend. This will help you: http://doc.qt.nokia.com/stable/qgraphicsdropshadoweffect.html |
61 * Notify players about room name change. |
61 * Notify players about room name change: there should be a new message type added to the protocol. ("ROOM", "RENAME", "oldName", "newname"). A possible implementation could be to pdate the Qt-Frontend that it accepts messages of the format posted below at that it updates the room list; after accepting the message the user interface should reflect the name change. So room list gets updated and if player is in that room s/he'll see a notice message in chat about the room name. |
62 * Write a simple shell script (bash, ruby, perl, python, awk...) to update the localization strings and propagate the diff to all the localized files. This task doesn't require coding or having an i-Device, just basic shell scripting. |
62 * Write a simple shell script (bash, ruby, perl, python, awk...) to update the localization strings and propagate the diff to all the localized files. This task doesn't require coding or having an i-Device, just basic shell scripting. |
63 * Enable some commands while in engine chat, for example /quit to exit. |
63 * Enable some commands while in engine chat, for example /quit to exit (you may want to just stop the game brutally with chForceQuit), /fullscreen to set the max window dimensions, /pause to pause the game, /bind for binding keys, /finish which would just have the game end by teleporting all hedgehogs out, then showing statistics (see chFinish ) . |
64 * Make a cross-platform tool (for instance a script) that identifies new phrases in our mission, traning and gameplay scripts and adds them (marked untranslated) into our lua locaization files. |
64 * Make a cross-platform tool (for instance a script) that identifies new phrases in our mission, traning and gameplay scripts and adds them (marked untranslated) into our lua locaization files. |
65 * Enable some commands while in frontend: fpr example /leave ( = /part - for leaving room), /quit ( - disconnects from server ), /exit ( - closes hedgewars), /addFriend, /removeFriend, /ignore, /unignore |
65 * Enable some commands while in frontend: fpr example /leave ( = /part - for leaving room), /quit ( - disconnects from server ), /exit ( - closes hedgewars), /addFriend, /removeFriend, /ignore, /unignore |
66 |
66 |
67 = Q/A = |
67 = Q/A = |
68 |
68 |
71 * Add an expandable testing module so that we can trigger main frontend functions and check their return value, enabling us to identify GUI bugs. |
71 * Add an expandable testing module so that we can trigger main frontend functions and check their return value, enabling us to identify GUI bugs. |
72 * Add an expandable testing module so that we can trigger main engine functions and check their return value, enabling us to identify in game bugs. |
72 * Add an expandable testing module so that we can trigger main engine functions and check their return value, enabling us to identify in game bugs. |
73 |
73 |
74 == Other tests == |
74 == Other tests == |
75 * Prepare a waterfall (eg. http://buildbot.libsdl.org/waterfall ) so that we are able to catch warning and compile failures early on. |
75 * Prepare a waterfall (eg. http://buildbot.libsdl.org/waterfall ) so that we are able to catch warning and compile failures early on. |
76 * Run valgrind on engine, report the leaderboard of most used functions and optimise two of them so that their usage is reduce. |
76 * Run valgrind on engine, report the leaderboard of most used functions and optimise them so that performance increases. |
77 |
77 |
78 = Translation = |
78 = Translation = |
79 |
79 |
80 Pick a language of your choise! There is certainly need of an update or a revision or even a completely new language. |
80 Pick a language of your choise! There is certainly need of an update or a revision or even a completely new language. |
81 |
81 |