TODO LIST: After 1.0
Posted: 25 Nov 2009, 15:24
A list of things that can be implemented, but are not that important or just too big of a change to put into the 1.0 release.
[ ] Split up themes into a "layout" file and a "theme" file, the layout will define the positions of the objects and the size of the play area and chat.
The theme will define the appearance of the object (bg, color, button layout, etc)
This way, one could define a layout for say, 1-2 people, another for 3-4, etc, so you wont need to load all the graphics again when you switch to a different layout (which is now inside the theme). This makes it easier to share layouts and themes seperately with your playgroup.
[ ] Support for "Special" formats like Planechase or Vanguard (this would require some kind of second library for Planes)
[ ] Being able to host Draft- and Sealed-Tournaments, though choosing Swiss or Elimination and OPT automatically calculates the matchups and keeps track of them (similar to what MTGO does)
[ ] Move active player/team control to the server. Makes it easier to handle players leaving the game and prevents the 'end turn twice' bug.
[ ] Lay the groundworks for a game definition file. Start with the naming of zones and text for actions such as moving cards from one zone to another.
[ ] Allow the start of a non-winston draft without the table being completely filled. First the owner needs to close entries and then activate it.
[ ] Allow the start of a non-teamed regular game witout the table being completely filled. First the owner needs to closee entries and then activate it.
[ ] Allow for a 1 player table to be created, no "lobby" would be required, the table will show instantly. This is needed because with moving game states etc, to the server, solitaire mode may not work correctly anymore. Users could just launch a server, connect to it and start a single player game. One would also have to define the number of "dummy players", else you would not be able to load decks for them.
[ ] Look into the window resize bug for dual screen systems, possibly windows7 required.
[ ] Split up themes into a "layout" file and a "theme" file, the layout will define the positions of the objects and the size of the play area and chat.
The theme will define the appearance of the object (bg, color, button layout, etc)
This way, one could define a layout for say, 1-2 people, another for 3-4, etc, so you wont need to load all the graphics again when you switch to a different layout (which is now inside the theme). This makes it easier to share layouts and themes seperately with your playgroup.
[ ] Support for "Special" formats like Planechase or Vanguard (this would require some kind of second library for Planes)
[ ] Being able to host Draft- and Sealed-Tournaments, though choosing Swiss or Elimination and OPT automatically calculates the matchups and keeps track of them (similar to what MTGO does)
[ ] Move active player/team control to the server. Makes it easier to handle players leaving the game and prevents the 'end turn twice' bug.
[ ] Lay the groundworks for a game definition file. Start with the naming of zones and text for actions such as moving cards from one zone to another.
[ ] Allow the start of a non-winston draft without the table being completely filled. First the owner needs to close entries and then activate it.
[ ] Allow the start of a non-teamed regular game witout the table being completely filled. First the owner needs to closee entries and then activate it.
[ ] Allow for a 1 player table to be created, no "lobby" would be required, the table will show instantly. This is needed because with moving game states etc, to the server, solitaire mode may not work correctly anymore. Users could just launch a server, connect to it and start a single player game. One would also have to define the number of "dummy players", else you would not be able to load decks for them.
[ ] Look into the window resize bug for dual screen systems, possibly windows7 required.