View this PageEdit this Page (locked)Attachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Fall 2003 M4: Give your Guide an interface

(Group, Due 10/21)


For this milestone you'll extend your Guide with a blended 2D and 3D interface. You'll embody your Guide by creating a 3D avatar that you can move around the screen and make refer to things, and you'll create a 2D interface that allows the user to communicate with the Guide and the Guide to communicate with the user.

Goals:


Questions on Fall 2003 Milestone 4

Requirements:

To embody your Guide, create a 3D character that you can programmatically move around the screen and cause to refer to things. Your Guide (referring now to the 3D character) must be able to:

Give your Guide 3 amusing idle behaviors. You should:

Clarification:
The goal is to create functionality that is analogous to the Office Assistant idle behaviors: whenever the user does not interact with the Guide for some specified amount of time, the Guide should execute one of its idle behaviors (randomly or in order). The Guide should then wait again until either the user interacts with the Guide or until the specified amount of time elapses again, at which point it executes another idle behavior and everything starts over again. If the user interacts with the Guide (including any part of the help system), the Guide resets the timeout (so the specified amount of time has to pass again without the user interacting with the Guide).

The methods should:


Create a 2D GUI that allows the user and Guide to communicate. This GUI could take the form, for example, of a text input box and "speech bubble" that follow the Guide around. Your GUI should:

You should structure your code so that executing Guide new causes the 3D character and 2D interface for your Guide to appear. Note that your design must expose the methods for controlling the 3D character and its idle behaviors so that we can test them.

IT IS WORTH YOUR WHILE TO MAKE SURE THAT YOUR TA CAN USE YOUR SOFTWARE! Demoing for your TA is a good way to do this (plus it allows you to get feedback on your design.



Turn-in your code using the Fall 2003 Turnin Information with the code 'M4'. Turn in your design in class.

Grading:


Note: If the TAs can't figure out how to do these things, they don't have to give you the points. The UI must be usable.


Links to this Page