Book reader: Difference between revisions

From OLPC
Jump to navigation Jump to search
(..)
 
(stub)
Line 1: Line 1:
''For a feature discussion, see [[Book reader feature set]].'' [[User:Sj|Sj]] [[User talk:Sj|<font color="fc9"><small>talk</small></font>]] 11:51, 5 May 2007 (EDT)
''For a feature discussion, see [[Book reader feature set]].''

There are many ways to read texts on a laptop; using the browser, using a document editor (abiword or wiki), or with a read activity (pdf/djvu [say with xbook] or html/crossmark, [with a browser-based or javascript-based [http://ejohn.org/apps/ebook/ reader]).


== Reading experience ==
All readers should support setting zoom and flow, paging and scrolling, text selection, linking, basic search.

== Long pages ==
We want to be able to parse long pages and render subsets of them without waiting to render everything. Gecko is pretty good at this; Evince isn't quite perfect at guessing how to focus on rendering only the page being looked at. Some subsets of reading/display/commentary we want to handle:
* Display collections of images and text quickly, before the whole page has loaded

== Other ==
* Nuanced use of keystrokes in handheld mode to allow a few dozen interpretations
* Offer interactive options to the reader when loading plaintext, long, or complex documents
* Early rendering of images or media before the entire thing has loaded

== Interface specification ==
This can be done somewhat independently of implementation.

* <tt>/usr/share/activities</tt> : the webview toolbar and embedded browser could use some updates to reflect interface ideas

Revision as of 03:04, 6 May 2007

For a feature discussion, see Book reader feature set.

There are many ways to read texts on a laptop; using the browser, using a document editor (abiword or wiki), or with a read activity (pdf/djvu [say with xbook] or html/crossmark, [with a browser-based or javascript-based reader).


Reading experience

All readers should support setting zoom and flow, paging and scrolling, text selection, linking, basic search.

Long pages

We want to be able to parse long pages and render subsets of them without waiting to render everything. Gecko is pretty good at this; Evince isn't quite perfect at guessing how to focus on rendering only the page being looked at. Some subsets of reading/display/commentary we want to handle:

  • Display collections of images and text quickly, before the whole page has loaded

Other

  • Nuanced use of keystrokes in handheld mode to allow a few dozen interpretations
  • Offer interactive options to the reader when loading plaintext, long, or complex documents
  • Early rendering of images or media before the entire thing has loaded

Interface specification

This can be done somewhat independently of implementation.

  • /usr/share/activities : the webview toolbar and embedded browser could use some updates to reflect interface ideas