Book reader: Difference between revisions
(+Status box (activity?)) |
(deprecating for Read) |
||
Line 1: | Line 1: | ||
{{deprecated|<big><center><br>see: '''[[Read]]'''</center></big>}} |
|||
{{ Status box |
|||
| activity = Book reader <!-- Name of the activity --> |
|||
}} |
|||
<!-- | icon = --> <!-- file name.ext (sans [[Image:file name.ext]] --> |
|||
<!-- | status = --> <!-- Status of the activity --> |
|||
<!-- | version = --> <!-- Current/latest version available --> |
|||
<!-- | base = --> <!-- Yes/No if it's included in the OS images |
|||
/ Could be the first build number --> |
|||
<!-- | source = --> <!-- Repository / location of the source --> |
|||
<!-- | l10n = --> <!-- Repository / location of the l10n resources --> |
|||
<!-- | contributors = --> |
|||
''For a feature discussion, see [[Book reader feature set]].'' |
''For a feature discussion, see [[Book reader feature set]].'' |
||
Revision as of 15:45, 2 October 2007
see: Read 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 experienceAll readers should support setting zoom and flow, paging and scrolling, text selection, linking, basic search. Long pagesWe 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:
Other
Interface specificationThis can be done somewhat independently of implementation.
|