EBook-Reader

Application description from a users perspective

Scene 1: Splash image and 3 buttons:

.. Where I left off ... -- Opens the last book you read at the place you stopped.

.. Bookmarks ... -- opens a list of the books you have bookmarks in and lets you open them to there. -- previews 2 lines above and below bookmark.

... Library ... -- opens a scrollable page of "shelves" Each shelf has a label which is user defined, and each shelf presents the books on it as a coverflow. Books can be moved between shelves by dragging and dropping. Each shelf has a context menu to control order, title, author or user defined. If user defined menu will present shelf as a draggable list instead of a coverflow when you want to re-order books. backswipe returns to coverflow.

in either the bookmarks view, tapping a book takes you to either the bookmark or the title page. upswipe downswipe provide smooth scrolling. Left and right swipe provide page at a time scrolling. Back swipe in gesture offers to bookmark with a dialog and returns to the shelf you came from.

When on a book, top left menu presents presentation options, which can be set book by book or globally. Type face (if I can figure out how), size, leading, justification, colors etc..

Images default to no larger than 1/4 screen, but touch results in lightbox like zoom.

Menu at splash or library offers import, and delete of books. When in a shelf, books can be deleted by dragging them to the recycle.

Features Wish List

1. on-pc conversion of various formats to pre-compatible format -probably using plucker distiller. Should support
   1. html
   2. rde
   3. doc
   4. m4b
   5. pdb (palm-doc)
   6. pdb (isilo), prc (unencrypted mobipocket)
   7. prc (encrypted) # lots of people with a ton of fictionwise books want this
   8. epub [1]
   9. plain text
   10. plucker
2. on Pre conversion of html and text docs by download from the cloud.
3. Library supports user definable catagories for sorting and shelving

   Shelves can be user defined to hold any collection of books a reader cares to:

   • By author
   • By Genre
   • By Geography
   • By cover color
   • By Series # very useful to group books in a series together

   The user should define the sorting catagories. Shelf design can initially be a scroll list like the Contacts app.

4. Book display page is minimally invasive making the most space available to read on as possible
5. Typography is bifocal friendly. User definable print sizes, and if possible type faces.
6. user defined foreground/background colors for text.
   1. Sepia
   2. Night mode
   3. Adjust screen brightness
7. multiple bookmarks per doc.
8. shallow menus
9. smooth scrolling or page-at-a-time scrolling by gestures.
   1. plucker style button-based scrolling
   2. swipe gesture based scrolling
   3. auto-scrolling with user adjustable speed
      1. Pause auto-scrolling by tapping gesture area
10. support for covers.
11. coverflow view of shelves.
12. easy rapid sorting of books onto shelves.
13. Change text size
14. Possibly be able to add books over Wi-Fi
15. Copy & Paste words
    1. Dictionary search implemented

Data Structure

Table: Catalog

• Title: string
• Author: string
• Shelfguid:
• CoverImage: Filename
• guid: (globally unique ID - a system generated number)

Table: Bookmarks

• guid:
• Position: ( an integer, refering to the character in the file at the top of the screen.)

Table: Shelves

• guid:
• ShelfName:
• Shelving Order: (A, T, or U) Representing Author, Title or User Set

Table ShelfOrder

• Shelfguid:
• Bookguid:
• Position: (integer representing the position of this book on this shelf)

Table: BookText

• BookGuid:
• BookText:

Data Issues

• This structure does not provide for books stored as chapters. This structure presumes a book is a single document. That document might have internal chapter indicators, but this structure does not divide the book up.
• This structure makes no provision for the internal storage of images.
• Should we actually store the text of the book in the DB or do we leave the book on the file system and just store a link to it?

There is some point, therefore to consider if in booktext, we want to simply store a plucker file, which CAN contain images and text intermingled.

Book Format Issues

• Can javascript on the device natively parse/navigate all of the above list formats?
  • No.
• Can javascript on the device effectively parse/navigate the plucker format (if we settle on this one), or do we need our own format?
  • Perhaps. plucker decoding sources in JAVA at http://www.fbreader.org/downloads.php
• Once we settle on a format, will the device be powerful enough to convert other formats to this one, or will we need a PC app to do the converting?
  • on pc app