EECS2311

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== EECS 2311 Project ======

====== New requirements added on March 6! See below... ======


TalkBox is a device that helps anybody, who is unable to talk, communicate.
Each TalkBox has a number of buttons that the user can press to play pre-recorded audio files.
Some of the buttons on the TalkBox may be used to load different sets of audio files.

{{:talkbox.jpeg|TalkBox}}
We will develop two pieces of software to help family members configure a TalkBox device with audio appropriate for their situation.

**1. TalkBox Simulator**

A piece of software that simulates the behaviour of any TalkBox device.

Has a user interface similar to that of the device.

The number of buttons and their functionality is configurable.

Is fully tested to behave as the hardware device.

**2. TalkBox Configuration app**

A user-friendly GUI-based app that allows for the configuration of a TalkBox device with appropriate audio.

It will provide facilities to record audio, or select already pre-recorded audio files.

It will allow the user to associate audio files with buttons in an intuitive way.

It will store the configuration in a USB flash drive to be used with an actual TalkBox, or will launch the Talkbox Simulator to test.


The TalkBox Configuration app and the TalkBox simulator will communicate through the use of a TalkBoxConfiguration object that will be serialized 

**Important Requirement**: Your code must serialize and deserialize an object that implements the [[http://www.eecs.yorku.ca/~bil/2311/TalkBoxConfiguration.java|TalkBoxConfiguration]] interface.

The TalkBox Configuration app must create a directory called TalkBoxData that contains the serialized object (extension must be .tbc) and the audio files. It can then launch the TalkBox Simulator and provide the path to the TalkBoxData directory as a runtime argument. 

**New requirements added on March 6**

**New Simulator requirement**: If the user presses a button while an audio is playing, that audio stops before the audio corresponding to the button starts

You may have to look into naming, searching for, and stopping threads

**Second new requirement**: Your system must log all actions the user takes in both apps

What buttons they press, what menu options they select etc.

The Configuration app must have a way to visualize the Simulator logs

This will allow the caretaker to optimize the configuration 

You must also create **a third app**, called TBCLog, that visualizes the Configuration app logs 

The purpose of this app is for the research team to determine how users use the Configuration app


<html><!--

  To be posted.

--></html>