Read ETexts Activity

Edward Cherlin echerlin at
Thu Feb 14 15:36:27 EST 2008

Will it include Text-to-Speech, for the purposes we have discussed on
this list? If so, could we get some sort of cursor or coloring effect
to show the illiterate or semi-literate where they are in the text?

On Thu, Feb 14, 2008 at 12:22 PM, James Simmons
<jim.simmons at> wrote:
> 1. Project name             : Read ETexts Activity
>  2. Existing website, if any : None
>  3. One-line description     : A simple Python Activity for reading Gutenberg etexts
>  4. Longer description       : This will be a fairly trivial activity that allows
>                             : paging through Gutenberg etexts.  It will support
>                             : reading text files (loaded from a USB device) or
>                             : Zip files containing a single text file (which is
>                             : the easiest format to download to the Journal using
>                             : the Browse activity).  It will have a user interface
>                             : quite similar to the Read activity, and will support
>                             : most of the functions of that activity except it
>                             : will support plain text files instead of PDFs.
>  5. URLs of similar projects :
>  6. Committer list
>    Please list the maintainer (lead developer) as the first entry. Only list
>    developers who need to be given accounts so that they can commit to your
>    project's code repository, or push their own. There is no need to list
>    non-committer developers.
>       Username   Full name             SSH2 key URL                    E-mail
>       --------   ---------             ------------                    ------
>    #1 jdsimmons  James Simmons         ?                               ja.simmons at
>    #2
>    #3
>       ...
>    If any developers don't have their SSH2 keys on the web, please attach them
>    to the application e-mail.
>  7. Preferred development model
>    [X] Central tree. Every developer can push his changes directly to the
>        project's git tree. This is the standard model that will be familiar to
>        CVS and Subversion users, and that tends to work well for most projects.
>    [ ] Maintainer-owned tree. Every developer creates his own git tree, or
>        multiple git trees. He periodically asks the maintainer to look at one
>        or more of these trees, and merge changes into the maintainer-owned,
>        "main" tree. This is the model used by the Linux kernel, and is
>        well-suited to projects wishing to maintain a tighter control on code
>        entering the main tree.
>    If you choose the maintainer-owned tree model, but wish to set up some
>    shared trees where all of your project's committers can commit directly,
>    as might be the case with a "discussion" tree, or a tree for an individual
>    feature, you may send us such a request by e-mail, and we will set up the
>    tree for you.
>  8. Set up a project mailing list:
>    [ ] Yes, named after our project name
>    [ ] Yes, named ______________________
>    [X] No
>    When your project is just getting off the ground, we suggest you eschew
>    a separate mailing list and instead keep discussion about your project
>    on the main OLPC development list. This will give you more input and
>    potentially attract more developers to your project; when the volume of
>    messages related to your project reaches some critical mass, we can
>    trivially create a separate mailing list for you.
>    If you need multiple lists, let us know. We discourage having many
>    mailing lists for smaller projects, as this tends to
>    stunt the growth of your project community. You can always add more lists
>    later.
>  9. Commit notifications
>    [ ] Notification of commits to the main tree should be e-mailed to the list
>        we chose to create above
>    [ ] A separate mailing list, <projectname>-git, should be created for commit
>        notifications
>    [X] No commit notifications, please
>  10. Shell accounts
>    As a general rule, we don't provide shell accounts to developers unless
>    there's a demonstrated need. If you have one, please explain here, and
>    list the usernames of the committers above needing shell access.
>  11. Translation
>    [X] Set up the Pootle server to allow translation commits to be made
>    [ ] Translation arrangements have already been made at _______________
>  12. Notes/comments:  Since the toolbar will be adapted from the Read toolbar I should
>    be able to use the same translations.  Also, since the activity will be simple
>    and entirely in Python it might be good sample code for new Activity developers
>    to look at.  The memory requirements of the Activity will be very low, because
>    I'm building a list of pointers to where each page begins rather than storing
>    the document in memory.
>  _______________________________________________
>  Devel mailing list
>  Devel at

Edward Cherlin
End Poverty at a Profit by teaching children business
"The best way to predict the future is to invent it."--Alan Kay

More information about the Devel mailing list