User:Douglas Wall
Douglas Wall (Talk | contribs) |
Douglas Wall (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | [[image:Inmate.jpg|frame|left|[[With apologies to the late great Douglas Adams.]]]] | + | [[image:Inmate.jpg|frame|left|[[With apologies to the late great Douglas Adams.]]]] |
| − | |||
Coming soon, some sort of design project decision, for the mean time I shall consider the cards problem. | Coming soon, some sort of design project decision, for the mean time I shall consider the cards problem. | ||
| + | <br><br><br><br><br><br><br><br><br><br><br><br><br><br><br> | ||
| + | |||
| + | == Cards as a minor design study (project warm-up) == | ||
| + | Someone asked me this question after they were asked it in a job interview: "Can you draw a UML diagram for a deck of cards including the Jokers". Sounds simple right? Well after my mind imploded while trying to deal with the Joker (no pun intended), which complicates everything, I have resolved to try and crack that nut in an OO manner. I have a loose context for the design, that being that it must be reasonably extendible/reusable and easily maintained. It should feature no game specific behaviour, and I will probably ignore graphic representation entirely. | ||
| + | |||
| + | Naturally, the solution could be as simple, yet horrific as this: (Insert basic image here) | ||
| + | |||
| + | To start with I have constructed an inheritance monster: (attempt 1). | ||
Revision as of 01:18, 4 August 2009
Coming soon, some sort of design project decision, for the mean time I shall consider the cards problem.
Cards as a minor design study (project warm-up)
Someone asked me this question after they were asked it in a job interview: "Can you draw a UML diagram for a deck of cards including the Jokers". Sounds simple right? Well after my mind imploded while trying to deal with the Joker (no pun intended), which complicates everything, I have resolved to try and crack that nut in an OO manner. I have a loose context for the design, that being that it must be reasonably extendible/reusable and easily maintained. It should feature no game specific behaviour, and I will probably ignore graphic representation entirely.
Naturally, the solution could be as simple, yet horrific as this: (Insert basic image here)
To start with I have constructed an inheritance monster: (attempt 1).
