Timeline for How to handle overlapping classes
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2015 at 18:20 | vote | accept | Evan Frisch | ||
| May 30, 2015 at 18:20 | comment | added | Evan Frisch | @DocBrown I'll have to take a look more into MVVM and MVP to pick one but that seems like exactly the kind of structure I'm looking for. Thanks a lot! | |
| May 30, 2015 at 18:03 | comment | added | Doc Brown | @Walker: you might transform this into a MVVM architecture (see en.wikipedia.org/wiki/Model_View_ViewModel). Model=GameState, View = your WPF classes, ViewModel=GameRunner, or an MVP architecture (Presenter=GameRunner). That way, your GameRunner depends only of an interface to the Presentation layer, which makes it easier to exchange the Presentation layer later. | |
| May 30, 2015 at 13:26 | comment | added | Evan Frisch | Thanks. That makes more sense of it that I could have. Since I'm thinking of having multiple ways of presenting the game, potentially a WPF app then possibly trying to host it online, does it make sense to have GameRunner focus on only one of those implementations and then later create a transformation layer to convert it to what the other presentation would need? | |
| May 30, 2015 at 1:03 | history | answered | Michael Brown | CC BY-SA 3.0 |