Update the UI when playing content (and provide a suitable menu structure)

[GoogleCodeExporter]

The current UI doesn't change when playing the content of audio. We need to 
provide a more relevant UI e.g. to pause, stop, go to the next and previous 
section, etc.  

We know we're not going to get the UI perfect on the first attempt, so 
we'll start with the following:

   * Up - go back to menu
   * Left - go to previous section
   * Right - go to next section
   * Center Touch - toggle play

Technically the program will need to create new activity when playing 
content. 

We'd like to allow more expressive gestures once we get the basics working.

Original issue reported on code.google.com by julianharty on 27 Nov 2009 at 6:57

[GoogleCodeExporter]

Jiayao has started making some modifications, but the current code needs to be 
restructured in order to pass the current 'book' object to the new activity. Of 
course, 
by the time we get to a clean working design, the design and implementation 
will 
probably change much further.

Original comment by julianharty on 27 Nov 2009 at 6:59

[GoogleCodeExporter]

Original comment by julianharty on 27 Nov 2009 at 7:05

[GoogleCodeExporter]

Implemented in r27:
* Left - go to previous section
* Right - go to next section
* Center Touch - toggle play

Original comment by Jiayao...@gmail.com on 1 Dec 2009 at 2:44

[GoogleCodeExporter]

With r193 the DaisyReader includes a functional user interface, including an 
initial menu, instructions on the gesture interface, visual feedback on the 
current section of the book, etc. So I'm marking this issue as fixed - Yay :)

Original comment by julianharty on 29 Dec 2010 at 12:06

• Changed state: Fixed