Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M7 - GUI Coding
Requirements:
We saved the best for last (well, almost last). Now code the remainder of the graphical UI portion. All the M6 functionality should now be available through a user interface.
Criteria
- 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
Code:
M7.st
Recommendations:
- Take time to think about what kind of GUI you would want for your project, don't just jump into making it. In case you jump into making a GUI immediately, you will eventually realize that what you are creating is not what you and your teammates want to make.
- Use the prototypes you previously stated in M5
- When you have finished with your GUI, ask a friend or someone who is not a CS/CM major to try out your GUI, this can help you find errors in design.
This where M6 UI MockUps come In Handy:
- Having a visual to work off of, really helps when designing your UI in smalltalk. Although you don't have to necessarily program where you want the buttons and other widgets to go, if you are quickly adding random buttons using the Cincom's built in UI editor just so you can get to the functionality of the application, not only will your UI look terrible, but you will confuse yourself when trying to figure what each widget in particular should be doing pro grammatically.
- This is where those M6 UI MockUPs come in very handy. If you have a visual to go off of, the UI design and functionality becomes a little bit easier to flesh out. The key is: the more planning you do, the better.
Sample ScreenShots of Our Oregon Trail UI:
Link to this Page