Object Oriented Design

Overall, I'm pretty happy with trying to keep with object-oriented principles when designing this app. However, in upgrading my interface, I did run into a problem that make my code look like spaghetti code.

Primarily, I have a problem with encapsulation and abstraction with how I'm handling characters from the main app controller. Right now, the general flow of launching the app and creating a new character is first to create a character data controller. When this data controller finishes loading, a character view controller is made and the data controller is passed into it. This view controller handles all the bindings and event processing.

The first problem with this is that I'm creating multiple view controllers. This solution works when you have multiple tabs with different views. However, when you don't have a set number or limit to the number of characters, the tab solution is a violation of GUI standards. A list based selection, such as a combo box, would be the proper way to go.

Now I have the problem with handling multiple data and one view. Ultimately, setting up bindings isn't hard, just tedious. However, currently the main app controller is dealing with the character data controller and the character view controller. I need to remake it so that the app controller is only dealing with a character controller now that encapsulates the data as well as the event handling.

So, in short, wish me luck.