Assignment 1: A Distributed Whiteboard

On this page... (hide)

  1.   1.  Requirements
  2.   2.  Grading
  3.   3.  Constraints
  4.   4.  Bonus (5% each)
  5.   5.  Plagiarism/Code Sharing Policy

Many CSCW systems are designed such that multiple devices must interact together. For example, when you send email (e.g. from Thunderbird or your web browser), that email passes through multiple servers before being stored on the "destination server," and later retrieved by the recipient through another email client. Similarly, teleconferencing systems like Skype are designed to allow two clients to connect to one another (potentially through another server), exchanging video and audio information. The key is that multiple computing devices are interacting with one another.

The objective of this assignment is to experience and understand some of core issues in multi-device programming.

In this assignment, you will be implementing a shared visual workspace. A shared visual workspace is one that allows multiple people to connect (from different computers), and then to draw/interact together on the same virtual workspace—like on a virtual shared piece of paper.

1.  Requirements

  • The system should ultimately present itself as a GUI on multiple machines. When the user draws (either by dragging the mouse cursor across the window, or by using a finger touch), the system should replicate that mouse cursor on the remote machine.
  • You will need to specify the IP address of the different machines somehow: this can be done at the command line, in a dialog box, or in a configuration file. (It doesn't matter.)
  • You will use the iNetwork Toolkit and C# to build your system unless you have spoken to me specifically about using another platform.

2.  Grading

  • You will record a short video of the system running (submitted to Piazza), and submit source code via a private Piazza post. The recording should show two different computers connecting together, and have simultaneous (i.e. at the same time) drawing. (This means you will need a third person to record the drawing, or have the camera on a tripod.)
  • If everything works, you're done, and good.
  • If only some bits work, you will be graded with partial points as follows:
    • Individual machines respond to GUI events (registered mouseDown, mouseUp, mouseMove) (20%)
    • Networking code is able to establish a connection (20%)
    • Networking code is able to send and encode messages (20%)
    • Networking code is able to receive and decode messages (20%)
    • Clarity of the code (20%)

3.  Constraints

  • You may use any sort of toolkit/library for the user interface if it makes it easier.
  • You may write this as a centralized (clients all connect to a shared server) or decentralized (clients connect to one another) system.

4.  Bonus (5% each)

  • Support more than 2 clients (e.g. 3 or 4)
  • Support "notifications" so that clients know who else has connected/disconnected from the system.
  • Support identified telepointers (i.e. visual representations of the remote mice)-this supports gestures
  • Support the "late joiner" scenario: if I log in after some drawing has been done, allow for me to see everything that has already been drawn
  • Support visual objects (e.g. creation/manipulation of shapes such as boxes or circles, or text) rather than just raw paint events
  • Support an interesting client type, and the input semantics of that device (e.g. mobile device | large display | etc.)
  • Support the ability to replay a session.

5.  Plagiarism/Code Sharing Policy

  • Don't cheat.
  • Don't work with other people on this assignment. You may talk with them, but do not share code.
  • If you use code from other places (e.g. to do drawing), make sure to cite where it came from (a URL will do).