kukulski/readifry

javascript speed-reading monocle, utilizing asymmetrical centering and hyphenation

readifry's Issues

show more context when paused

play with different tempos and subtempos

e.g: do headings display for an extra beat?
do tail-ends of hyphenated words only display for a half-beat?
do trivial words display for less time than real words?

add a blank between word displays

this might help to achieve faster pacing
AND this is needed to keep "row row row your boat" from rendering as
"row (pause) your boat", which, under the "adjust tempo for bold" hypotheses would read as "row! your boat"

tune up positioning via webcam recording

if eyeballs move less when everything is running well, an eye-tracker (or even a webcam) could be used to fine-tune the parameters of the system, possibly even on a per-user basis.

markdown support

update pre and post-hyphenation logic to use actual character widths

presently hyphenation is triggered and based on number of characters in the word, rather than its rendered width.

1. trigger hyphenation based on exceeding an n-width threshold
2. group hyphenated chunks using actual chunk widths

use local storage to set bookmarks

build out the microfiche exploration

synchronize with overview window

this is toward the random-access problem/opportunity -- done right this becomes spatio-temporal microfiche

test on tablet and phone

give option for hyphenation orphan control

is it better to do greedy hyphenation (housekeep-ing) or balanced hyphenation (house-keeping) ?

if we do greedy, and can identify the suffix as trivial, does that let us show it for a shorter beat?

make the code pretty

make it pretty

gesture support

switch to window.requestAnimationFrame

This will let me add a 'blank' time in-between words as well as implement half-beats and long-beats.

try 2-line fixations

Nice work + feedback

Hi,

I just wanted to say I gave this a spin and it works really nice - I tested it on chromium on debian 7 and xubuntu 13.10.

Here is my feedback:
-when the text reaches the end the reader should stop, not restart
-the reading speed setting should be remembered, not readjusted every time (this was a problem for me in gritz/spread0r but I found the setting in the code)
-gritz / spread0r had a feature that I miss here - every time a sentence or phrase would end (a dot would be reached), it would pause for just a fraction of a second - it was hard to notice it but it gave a better sense of form and understanding to the text

Thanks for this,
Iancu

grab the source text from readme.md