Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M7 GUI Implementation
Requirements:
- Wagon Configuration Screens (setup, loading, setting pace etc)............10
- View Inventory and People ................................................05
- Taking a turn (move) .....................................................10
- Map/Location View ........................................................15
- Rest/Stop View ...........................................................05
- Trade Windows ............................................................05
- Game Status (current date, miles traveled, etc) ..........................05
- Ability to exercise admin functions (load/save, start/stop, end) .........05
- Hunting screen (does not have to be game for basic credit) ...............05
- River Crossing (options for crossing) ....................................05
- Random Event Displays ....................................................10
- SUnit tests (for any non-gui classes added)...............................10
- Good Smalltalk code and style.............................................10
M7 was the hardest milestone. First off, the GUI we planned from M5 was changed, partially because we found it was easier to use different elements. The VisualWorks GUI tool isn’t that good, although it is easy to use. It will crash randomly (well, not randomly, but it WILL crash.). Save often, and file out your package often as an extra backup.
What worked:
- Used the M2 as a reference to start, because forgot a lot of the GUI coding.
- Use the supplied documentation in the cincom/docs directory (GUIdevguide.pdf)
What didn’t work:
- Again, got started very late.
- Couldn’t get the map working, so think about that early.
- Couldn’t get loading/saving to work properly, also start thinking about that early.
Final Code base
- CS2340ATHF_Final.st
- Code is also on Cincom's smalltalk public repository STORE under "CS2340ATHF" bundle or "OregonTrailATHF" package.
Link to this Page