Due date: 3/2 : 11:59pm
Visualize the State of a Player
Task 1: [POINTS: 30] Your last task before spring break is to add
a module that helps you visualize a game graphically. First, change the
interface of player so that create-player consumes a second argument:
To accomplish this, you should use the model-view pattern (aka MVC). That is, your visualization code should be completely separated from your player code. Furthermore, it should be possible to use two distinct, unrelated graphical tool boxes to implement the visualization module. [Note: the pattern usually comes with the word "control". Since you are not implementing an interactive graphical user interface, you don't need a control.]
Your code should be able to display at least fours parts of the player's state:
Your code should be able to visualize at least two player actions:
The external design (i.e., the look and feel) of the graphical visualization is up to you. You are free to choose your favorite graphical toolbox and display medium. I have posted an example above, but you are not forced to follow this in any way.
For the internal design, you should follow the standard rules of programming you have encountered at Northeastern.
Task 2: [POINTS: 10] Read up on the Open Cable Application Platform (OCAP). Then write up one paragraph (at most 250 words, usual HTML format) comparing the 670 project to elements of OCAP programming.
|last updated on Tue Jun 9 22:03:19 EDT 2009||generated with PLT Scheme|