player
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| player [2017/02/08 21:03] – bil | player [2017/02/24 16:28] (current) – bil | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== The Player App ====== | ||
| + | |||
| The Player App will run on a Raspberry Pi that will physically be in the same box as the Braille cells and buttons. | The Player App will run on a Raspberry Pi that will physically be in the same box as the Braille cells and buttons. | ||
| Line 5: | Line 7: | ||
| **One of your main jobs in this phase is to design and document this format | **One of your main jobs in this phase is to design and document this format | ||
| ** | ** | ||
| + | |||
| + | ====== Official Simulator API ====== | ||
| + | |||
| + | You can access the official Simulator API and implementation [[https:// | ||
| + | |||
| + | The project contains javadoc as well. You can also access the Javadoc [[http:// | ||
| ====== To get started ====== | ====== To get started ====== | ||
| - | Take a look at the {{: | + | Take a look at this {{: |
| It will give you a pretty good idea of the kind of capabilities the Player app needs to have. | It will give you a pretty good idea of the kind of capabilities the Player app needs to have. | ||
| Line 21: | Line 29: | ||
| - Playing audio clips stored as files (either for speech or for sound fx) | - Playing audio clips stored as files (either for speech or for sound fx) | ||
| - | - Using a text to speech library to create audio on the fly | + | - Using a text to speech library to create audio on the fly. You should research available text to speech libraries online, and select one for your project. |
| + | |||
| + | ====== Player Submission Details ====== | ||
| + | |||
| + | Rubric posted under Evaluation. | ||
| + | |||
| + | Four grade components | ||
| + | |||
| + | - Requirements document | ||
| + | - Testing document | ||
| + | - Player File Format Documentation | ||
| + | - Implementation | ||
| + | |||
| + | ====== Player Submission Process ====== | ||
| + | |||
| + | 1. Create a .zip or .jar that contains the following: | ||
| + | |||
| + | - All grade components including the code | ||
| + | - A README.txt that | ||
| + | |||
| + | * Explains the contents of the zip file | ||
| + | * Provides a link to your github repository | ||
| + | |||
| + | 2. Email the zip file to bil@cse.yorku.ca by 11:59pm on Mar 7 | ||
| + | * Only one email per team | ||
| + | * Include your team number in the subject | ||
| + | 3. Each student must also send me a private email with an assessment of their teammates’ contributions | ||
player.1486587839.txt.gz · Last modified: 2017/02/08 21:03 by bil