View Single Post
Old 05-13-2018, 04:36 PM   #11
nohandlebars
Member
nohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshesnohandlebars can read faster than his screen refreshes
 
Posts: 16
Karma: 14242
Join Date: Jan 2018
Device: None
Quote:
Originally Posted by FrustratedReader View Post
Sounds interesting.
TBH, "multitouch" is a a bit over-rated, very HW dependant and can be less intuitive. If basic single touch is good, then that would be fine.

I had to look up "KSM". Here is a thread on KSM 9

I think I'd want a 2nd working H2O, as I use my H2O too much to read stuff and proof my own writing.
I more want the mutitouch for right click functionality but this can probably be achieved with a long press somehow. I use my device as a reader on a daily basis still, the Debian system is not running all the time and all you have to do is restart it to get back to your "normal" ereader

Quote:
Originally Posted by markyisri View Post
I will give this a try. How much source code is being compiled, and do your scripts require the machine they're on to be online?
There isn't much to actually compile, just the framebuffer update binary and the custom touch driver. You can see this all in the "source" directory. Your Kobo does not need to be online to run the scripts, you do need internet to build them though.
nohandlebars is offline   Reply With Quote