This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hello, all! I'm trying to develop a swing-app, a dicegame(yatzy). Classes: Player, PlayField, Die, ScoreBoard, ThrowResult, HighScore, various JButtons, ResultComputer, PlayTable(JFrame), and GameController. I need a tip or two on how to take the best object-oriented approach. The tricky part is not the inheritance part or aggregation. The keyword seems, to me anyway, to be GameController. I mean, without it, you end up doing nothing but sending references here and there, back and forth. Anyway, the main question: Is it a good idea to let the GameController hold references to each object of interest to be able to setup and display the right ScoreBoard to the right player, send a ThrowResult to the ResultComputer, etc, etc. Hope I made myself understood??!! Would appreciate some hints and tips!!