TNH While I realize the parsing is necessary to accurately measure speed reading (an example is how Speed Reading III, which I really like good job!, appears to stall if fed a text w/ line feeds), I think this Application can be refined to get past that issue and expanded. It shouldn't take as long as it does to shoot a file through grep stripping the linefeeds and replacing them w/ single spaces. A word is just contiguous letters without whitespace. So if you detect whitespace of any kind as 'NOT A WORD' then you should have an appropriately fast application with all the speed it needs and no need to pre-convert files. I'm not saying this is a bad application. It's good. I hope you continue to develop it, but the runtime engine seems too slow for most people to give it a second look. The reason I mention the pyrite system is you can send a pdb straight into text and chain the filters (it's old, but it would work). I particularly like the way the placement and scrolling work in eBook LIbrary. Whether this is a better method of speed reading that static placement is probably up for grabs, but it more accurately approximates normal text placement so it's much more useful for people using non-digital source than any other speed reading applications I've seen. In short. Thanks, this is a good application and much appreciated. I would really like to see development continue. |