Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • I think the 2 states for seat object is fine, you can model the state for Game object (I think a more suitable object name is Table or GameTable object, since it's natural to think that a Table consists of 4 seats) as you mentioned and use Observer pattern for communication between seat and game. Game object will observe for any changes from any seats that it contains and decide its corresponding state and transition Commented May 7, 2015 at 6:44
  • If the logic for changing states is simple, and you only have two states (and don't expect more), then State Pattern might be overdesign. Consider the solution that's simple. It sounds as if you're looking for a problem to solve with a pattern, rather than the other way around. To use another analogy, just because you have a drill in your toolbox, don't go looking for places to put holes in your house. Commented May 7, 2015 at 14:40