Multi-Touch System

Due Date: 12/01/14 11:59pm

Due Date: 12/03/14 11:59pm

Build and modify a multi-system using existing components

The goal of this assignment is to use existing components to explore the differences between multi-touch and mouse point interaction.

In addition to building a system, you will demonstrate understanding of the system by modifying the components.

Task (~4 hours for each individual, plus 4 hours as a group)

  • Requirements for the system:
    • Options:
      • Easy: Extend the "advanced.drawing" fingerpaint program that comes as an example with MT4J with some interesting multi-touch feature that you clear with Prof Patterson first.
      • Hard: Create a bubble popping game that requires multi-touch input to pop some kinds of bubbles
      • Something else that interests you that is about Multi-touch (clear with Prof. Patterson)
      • It must run as a Java program compiled in Eclipse using MT4J
    • It must receive events from a TUIO server.
      • Programs that run using MT4J have a TUIO server built-in. No additional work is necessary. If you are trying to recreate the demos from class with the flash applications, then you need to run the TUIO server that comes with Community Core Vision.
    • It must receive multi-touch inputs from a live multi-touch device which you build. See Community Core Vision for software to do this from video.
      • I want you to build one using one of the techniques that we showed in class, or something else that you can think of.
      • I want you to do more than just download an app that sends multi-touch input (although you can do that for testing if you want)
  • Admin
    • This is a group assignment. Groups may be no bigger than 4 people.
      • A recommended breakdown of assignments is:
        • Multi-touch team: Responsible for delivering multi-touch events to the system
        • Java team: Responsible for writing code that responds to multi-touch inputs
        • Integrator team: Responsible for video and submission
  • Turn-in
    • Demonstrate the system by video-capturing the system in operation. Target length of video is 4 minutes.
    • Take some time to make a quality video. We aren't interested in snazzy transitions and music we are interested in clearly seeing you meet the learning objectives of this assignment. If we can't see that you have done the things we asked in the video, you won't get points for it. So think through the video storyboard first.
    • Turn in a link to a web-page which has:
      • The names of the people in your group and a description of the work they did.
      • A link to the video of the system
      • A 4-6 paragraph description of the components and architecture of your system including appropriate citations.
      • A link to the source code for your program.
    • Turn it in On EEE
  • Rough grading
    • To get a C
      • The video also fails to show anything happening
      • There are clear errors in the Java program
    • To get a B:
      • The system might use recorded video from CCV instead of live input
      • The system might have individual components that work but it doesn't work together
    • To get an A:
      • The java program must respond to multi-touch events in real-time.
      • Finger-painting (or alternative) must be compelling
      • Video must clearly demonstrate the system working
      • There must be a mutli-touch device
    • To get extra credit: The program must be impressive, the video must be compelling. For example: Space Hockey. This team works at Google NYC now. :)
  • Other links:
  • Test Videos
  • Demo #1 Resources:
  • Demo #2 Resources:
  • Demo #3 Resources:
  • Demo #4 Resources:
  • Demo #5 Resources:
  • Demo #6 Resources: