We discussed the use of a group pointer in a shared editor with a shared view. Consider the advantages and problems of using a group pointer when participants have different views. How do you show the pointer if it is outside part of the document you are working on? Think also about the issues when the system is a hypertext-based co-authoring system. Is there any use for a group pointer in this case?
The purpose of this exercise is to encourage
students to think of the various scenarios that can
arise during group editing and to encourage creative
interface thinking. Where suitable tools are available,
students can create mock-ups of their solution using
a drawing package, or even envisionments of specific
scenarios using HyperCard or a presentation tool.
Below are some ideas.
Arguably the group pointer is even more important when there are separate views than when the view is shared. With a shared view the participants can be assured that they are seeing the same thing and so can assume a shared context. With separate views the participants are likely to have various problems when they forget that the others' views are different. For example, they will have trouble with indexical expressions or with relative statements 'the thing at the top'. The presence of a group pointer can help the participants to gain a shared focus.
On the other hand, the very presence of the group pointer can encourage the participants in a false sense of shared context. One could therefore argue that when participants want to enter a period of shared focus and synchronous discussion, they also move to a shared view. However, for the rest of this answer we'll assume that the views stay different.
What do we do when the group pointer is outside of the view? For example, in Figure 19.8, your colleague might move the group pointer to the line starting 'More adaptable'. In this case, your screen cannot display the group pointer in its correct position. Various options suggest themselves.
One could have the hand icon appear at the very top of your display with the finger pointing straight upward, meaning 'see above'. Similarly, if the group pointer were below the screen the icon could appear at the bottom pointing down. If such icons were displayed then the user could scroll the screen upwards until the group focus was found. Alternatively, one could arrange that to click on the icon scrolled one to the correct position.
Instead of, or in addition to, these 'out of view' icons, one could use the scrollbar and display the group pointer's position in it, thus allowing the user to see where it is easily, and scroll there if appropriate.
In the hypertext case, the solutions depend very much on the particular style of the system. If the individual nodes are large, then even if two participants are acting on the same node they may have different views, in which case all the above measures become relevant. If the participants are looking at different nodes, then the first action of a group pointer should be to direct attention to the node of interest. In a hypertext where the node graph is shown, this can be achieved by displaying the group pointer on the node of interest. Alternatively, if the graph is not displayed, the presence of a group pointer could be shown by adding a 'go to the focus node' button, rather like the 'home' button in many HyperCard stacks.
Although it is not mentioned in the question, it is worth also considering the display of other people's insertion points. In Figure 19.8, although your insertion point is within your colleague's view, it is not displayed in any way. There is no reason why other people's insertion points should not be displayed (suitably identified) when they fall within your view and vice versa. In addition, one might want some indicator on your scrollbar to show where your colleague's current view is. Such indicators can enhance group awareness and be a focus for initiating direct communication.