Difference between revisions of "Game Programming Class9"
(→Homework) |
(→Review Midterm Games) |
||
Line 1: | Line 1: | ||
+ | http://research.microsoft.com/apps/video/default.aspx?id=145653 | ||
+ | |||
==Review Midterm Games== | ==Review Midterm Games== | ||
Inclass look @ 2d games | Inclass look @ 2d games |
Revision as of 18:50, 27 March 2011
http://research.microsoft.com/apps/video/default.aspx?id=145653
Contents
Review Midterm Games
Inclass look @ 2d games
- Functionality
- Game play
- Localization
- Overall stability
- Performance
- Usability and overall experience
Using a sprite manager to manage groups of sprites
Often times it's easier to manage groups of objects if they are contained in a class that manages them.
I often use this pattern when I have many objects that need to act a a group.
In class demo of https://iam.colum.edu:8443/svn/XNAProg/trunk/Jeff/IntroObserver/
Observer
Observer
- Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.
Observers
http://www.dofactory.com/Patterns/PatternObserver.aspx
Observer is a design pattern that is often used to publish (push) or subscribe (pull) changes in the stae of one object to other interested object. It encourages loose coupling of objects.
The object the get the data often called the subject then notifies the observing objects of the change. The observing object will often repond to the subject.
Here is a real example in c#. In this example a stock (the subject) notifies and investor (the observer) of a change in price.
http://iam.colum.edu/oop/gbrowser.php?file=/classsource/class13/Observer_j.cs
http://iam.colum.edu/oop/classsource/class13/Observer.aspx - source
Homework
Make a game testing report.