Open modular components | Yes.
We have implementations of:
|
User model | The model of possible user states is contained in the statechart of student interactions (see Student+sim.lisp). |
Task/domain models | The student and task models are combined in the statechart above. |
Pedagogy | NA |
Data store | NA |
Gui | We use the GCL TK/TCL extensions to create a mud client as well as graphical depiction of the state chart. |
Messages supported | We parse the MCP protocol. The statechart responds to messages that track the student, includeing connect, look, say, help, execute, and disconnect. |
Api | The only properties we depend on are the capability of the Mud to broadcast event descriptions using the MCP protocol. |