Current ToDo

Clean up the core-code [2/11]

[ ] Error-Checking!
[ ] Clean up unit_base.h
[ ] Clean up terrain.h
[ ] Use the game_settings class
[X] Clean up area.h
[X] Clean up scene.h
[ ] Add more informations to scene.h

(Like changed states etc.)

[ ] get_damage_percent shouldn’t have to parse the damagetable

after each call

[ ] Just do the output on a debug-build
[ ] Can pass should be located in aw::map
[ ] beaten in player_utilities.h shoud be located in aw::game

Fog of War [0/4]

[ ] Determite the visible range for different units
[ ] Implement in Core
[ ] Implement in Qt-Gui
[ ] Implement in Cocoa-Gui

Customizable CO’s

Ideas

Some sliders to assign a number of points to certain attributes (Stronger land-units, stronger range-units and so…)

Correct pathfinding

Weather [0/2]

[ ] Collect informations about weather in Advance Wars
[ ] Implement in Core

Make Configurable

Extend the config-api

Make Qt configurable [0/2]

[ ] Build a settings-window
[ ] Make a setting for the animation-types (Type, duration etc.)

Make CoreAnimation-Animations configurable [0/3]

[ ] Examine Cocoa-Config-Apis
[ ] Use configurations in the source
[ ] Add config window

Use defaults for initial-funds and funds-per-building [3/3]

[X] Add to config.xml
[X] Use in Qt
[X] Use in Cocoa

Qt-Gui

(Maybe) Use QGraphicsView [4/4]

[X] Build UnitGraphicsItem
[X] Make MapWidget a QGraphicsView
[X] Put everything together
[X] Clean up the code

Implement animations (Possible through QGraphicsView)

Later

Drafts about networking

Online-Games like old-school Go Send an email after each player’s move so that you can play a game over a greater range of days
Show games on a webserver
How should the protocol look like? (XML/JSON/Binary)?
Logic on server&client or just on client?
Should the scene sended? Or just the changed parts?