SVN directories?
Henri Yandell
acm - "Audio Content Management"
aos - "Audio Operating System & System Audio Files"
audiolibrary - "Online Audio Library"
authoring - "Authoring Tool"
schemas - "System Schemas"
virtualdevice - "Virtual Flash Version of Device?"
I've used the svn history to guess, but I don't really know what the
titles mean :)
Also whether they're historic or the latest code? Maybe I'm looking in
the wrong place as the most recent change was a year ago.
The code.google project has three groups of its own, but all seem dead.
Hen
Cliff Schmidt
It's great to have someone asking these questions and trying to get
actively involved. I'm sorry for my long delay in replying, but I
hope some of my replies will encourage other people to ask questions
and to get more involved. I've just been distracted while making
preparations for my upcoming trip to Ghana, later next week, when I
will work with our Ghana staff to expand our maternal/child health
program from 3 communities to 20. I'll answer the questions in this
email now and will do my best to respond to your earlier emails in the
next day or two. But please keep the questions coming!
See answers to your questions below:
On Sun, Mar 4, 2012 at 9:38 PM, Henri Yandell <he...@yandell.org> wrote:
> Could anyone explain what the following directories are?
>
> acm - "Audio Content Management"
This is one of our two active projects (the other one is 'device' --
the embedded code that runs the Talking Book device). The ACM is our
Java-based app that allows you to play, import, and export audio files
to/from your computer and also to/from any Talking Book. You can
learn more about it here:
http://www.literacybridge.org/talking-book/audio-content/ and here:
http://www.literacybridge.org/2011/07/21/helping-content-authors-create-more-effective-content/.
You should be able to download the ACM here and run it on any Windows
computer that has Java installed. Michael Busch led this project,
with a lot of great work coming other volunteers like Sven Schade,
Mathias Koehnke, and Chris Schmid.
> aos - "Audio Operating System & System Audio Files"
This was never used much. I've just removed it. The files we were
thinking would go here made more sense to be in
http://literacybridge.googlecode.com/svn/device/software/device/trunk/content/,
which is where we keep all the files that are loaded onto a Talking
Book.
> audiolibrary - "Online Audio Library"
This project was intended to allow us to find and host Talking Book
audio content in the cloud. Two long-time volunteers, Michael and
Tanya, worked on getting this project started, but put it on hold when
we didn't didn't think it was an immediate priority. It's now getting
to be a little bit of a higher priority, now that we are focused on
creating lots of content.
> authoring - "Authoring Tool"
Michael Busch also led work on this tool about three years ago, but
it's now still a lowish priority. The idea is that a Talking Book can
run apps. Any app you can imagine could be run on a Talking Book, as
long as you can imagine it without a display and a mouse or full
keyboard. The Author Tool was started to allow a non-programmer to
create apps -- multiple-choice quizzes, games,
choose-your-own-adventure stories, etc by connecting lots of separate
audio files together with a GUI. The tool would then generate XML
code that could be automatically converted to the control tracks that
run Talking Books. The reason it's not a big priority now is that we
are focusing most of our project work on simple recorded messages on
agriculture and health, and not so much on more interactive apps just
yet. But I'm sure we'll get to this one day soon.
> schemas - "System Schemas"
This is where we were storing the XML Schemas that was meant to define
the format of the Talking Book device control tracks. They were used
by the authoring tool (see above).
> virtualdevice - "Virtual Flash Version of Device?"
This is a very old (about 4 years old!) Flash app that simulated a
Talking Book. It was created by another volunteer to help us plan out
the Talking Book functionality. Michael Busch and I have been talking
about doing something kind of similar soon that we will need help
with. We'd like to create a port of the embedded C code for the
device that could run on a Windows machine and simulate a Talking
Book. This would allow more software volunteers to write code for a
Talking Book without needing to have a real one and the debugging
cables (due to costs).
Hope that helps.
Cliff
Henri Yandell
I'd checked code out from talkingbook.googlecode.com rather than
literacybridge.
What's with the other Google Code project? Is it dead?
Hen