- A regular chat client.
- A customized regular chat client.
- The Moderator's client within a Moderated open floor phase in a structured room.
- The Room Operator's client within a Moderated open floor phase in a structured room.
- A client within a phase of a structured room using an application-oriented protocol.
- Dynamic changes examples.
A regular chat client for an unstructured room or an open-floor phase in a structured room. The default client looks like any standard chat. It is important for people who are happy with such a basic tool.
This client can be customized both globally, by specifying interaction features when a phase is instantiated, and individually, through the Options Menu. The screenshot shows a customized configuration with an ‘Info Panel’ displaying unsolicited awareness messages (such as ‘mary joined the room’) and queries (e.g. ‘Roles’ button for requesting the current role list). The ‘Can you talk?’ and ‘Are you op?’ indicators are examples of individual customizations. Several other classical features are provided by default such as automatic URL recognition, and private session launching ('whispering').
New messages sent by other participants are only displayed on this client with the [MODERATE] label. The moderator uses the Publish window for choosing either to accept the message (which is broadcasted in the room), or to refuse it (starting a private chat session with an automatic notification to the author for comments).
The screenshot shows the client of a user playing the predefined Room Operator role available in all structured rooms. Next and Jump buttons allow him to instantiate the next phase or any other phase of the structured room. Other users have a standard client without these role-specific buttons. This exemplifies how user interfaces reflect predefined and protocol-specific roles.
The phase uses a non-predefined 'Explanation' protocol. Transition rules are enforced because users can only choose between a list of protocol permitted utterance types when they have the floor.
The screenshot illustrates different aspects of dynamic malleability. Jack (a teacher) is a Room Operator during a disorderly open-floor phase. At some point, Jack decides to kick off Peter (a student) for one minute (message 12). He decides also to change the current regular room into a moderated one for a better control of the contributions. All clients instantly reflect that change: message 13 was un-moderated while message 15 is now moderated. In addition, Jack decides to create a ‘Summarization Phase’ after the current phase with a circular floor passing protocol: this model evolution is performed interactively. Instantiation will be done later, when the phase instance will start (with the Next or Jump buttons).