If you want to try it out on a PDF, I have implemented this in sioyek PDF reader: https://github.com/ahrm/sioyek You need to enable experimental features in `prefs_user.config` by adding `enable_experimental_features 1` and then enable this mode using `toggle_fastread` command within sioyek. I also experimented with more sophisticated algorithms, you can read about the experiment here: https://ahrm.github.io/jekyll/u…
(Developer of the Github repository in the post here) Is it possible for me to easily integrate with sioyek to provide PDF converting ability directly within the Chrome Extension? This would be useful for the following reasons: - For the times when you click on a link and it opens the PDF in Chrome - Many people I know use Chrome as their main "PDF Viewer" app. I believe this will be a great way for both our OSS proj…
A Chrome extension for bionic reading on any website
31–40 of 54 posts
Re: A Chrome extension for bionic reading on any website
#32Is there any actual research/study on the efficacy of bionic reading? If it improves reading speed / comprehension significantly then it's really a no-brainer.
Re: A Chrome extension for bionic reading on any website
#33Why is this popping up everywhere right now? This has been integrated in the Reeder RSS app for ages.
The trademarks and patents speak for themselves.
Re: A Chrome extension for bionic reading on any website
#34I saw the stories about Bionic Reading a few days ago and ended up going down the rabbit hole for a bit. What interested me was that it wasn't the weight of the letters that helped me read quicker but the shorter lines . The examples with and without Bionic Reading formatting were just as easy for me to read but where it fell apart was when I read something with more words per line. Put 12+ words on a line and the Bi…
Re: A Chrome extension for bionic reading on any website
#35If you want to try it out on a PDF, I have implemented this in sioyek PDF reader: https://github.com/ahrm/sioyek You need to enable experimental features in `prefs_user.config` by adding `enable_experimental_features 1` and then enable this mode using `toggle_fastread` command within sioyek. I also experimented with more sophisticated algorithms, you can read about the experiment here: https://ahrm.github.io/jekyll/u…
Re: A Chrome extension for bionic reading on any website
#36Earlier quoted context omitted.
(Developer of the Github repository in the post here) Is it possible for me to easily integrate with sioyek to provide PDF converting ability directly within the Chrome Extension? This would be useful for the following reasons: - For the times when you click on a link and it opens the PDF in Chrome - Many people I know use Chrome as their main "PDF Viewer" app. I believe this will be a great way for both our OSS proj…
I am not very familiar with chrome's PDF API (or lack thereof) but I doubt that it is possible.
Re: A Chrome extension for bionic reading on any website
#37Re: A Chrome extension for bionic reading on any website
#38Re: A Chrome extension for bionic reading on any website
#39I wrote an Objective C Mac OS app (which I normally never do, so that was quite a bit of messing with completely unfamiliar tools such as Xcode) and the rarely used 'services' menu so that I could select any text and fire up this app.
It worked wonders for prose. It doesn't work for highly specific technical reading, or anything where the formatting itself is important, as that is, naturally, obliterated.
A mac or two later and I don't really want to build it again.
But, does anyone know of an app or site that does this for you? Possibly with some nice advances such as:
* Give you a little more time on complicated words. * Possibly let you click a paragraph in e.g. a webpage and then just blast that paragraph past your eyes, letting you mix reading and looking at the layout. This sounds great for wikipedia, where there are images to look at, table data, paragraphs, etc.
If no such thing exists I might be tempted to write it as a browser extension.
Re: A Chrome extension for bionic reading on any website
#40I saw this on my twitter and was kind of surprised that this was patented and had an expensive API to go with it. I don't see why this couldn't be on-device processing. Why utilize a cloud API for an accessibility feature?