Well, if you can find a nice separation of concerns that would be great. Keep in mind that the design has to work for the editor too though. Game and EditorGameBase are two balls of mud right now: they have too many responsibilities - I think the design would already improve if they could be split in a bunch of balls of mud with some less responsibilities and the original class would only contain those. Maybe a clearer design becomes apparent then.
What methods would you pull into the new class? -- https://code.launchpad.net/~widelands-dev/widelands/game_end_summary/+merge/176000 Your team Widelands Developers is subscribed to branch lp:~widelands-dev/widelands/game_end_summary. _______________________________________________ Mailing list: https://launchpad.net/~widelands-dev Post to : widelands-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~widelands-dev More help : https://help.launchpad.net/ListHelp
