MobileRead Forums - View Single Post - Detecting if book being read / home screen in nickel

NiLuJe · 09-21-2018, 01:08 AM

I'm obviously fairly biased here, but this sounds fairly more complicated than inotify monitoring for no real good reason?

Unless the reason is fun, in which case: break a leg, the more the merrier

.

In no particular order:

* There are three or four variants of touch protocols used on Kobos, and the original Touch trilogy is a fantastic mess to get right.

* Screen printing is easy enough (Hi!).

* As is screen scraping (Hi again!), but you kind of have to find something to match against. We went with solid strips of colors, because that's easy enough to do, and hopefully universal enough.

@frostschutz went with a full scanline here, which is trickier, especially if font rendering is involved (because your pattern will basically be device AND FW-specific, or nearly so).

* Actually playing nice with Nickel may be tricky, depending on how you end up running things and exactly how much control & safety you want to enforce (c.f., KFMon's teething pains in its infancy on that front).

----

I mentioned screen scraping, because getting anything interesting out of Nickel is pretty hard, so, that's one obvious solution.

The other is "simply" monkey patching Nickel at run-time to catch the relevant function calls, but in that case you can probably forget about anything else and just go with that

.
(c.f., a few random posts on that subject over here).

09-21-2018, 01:08 AM	#2
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	I'm obviously fairly biased here, but this sounds fairly more complicated than inotify monitoring for no real good reason? Unless the reason is fun, in which case: break a leg, the more the merrier . In no particular order: * There are three or four variants of touch protocols used on Kobos, and the original Touch trilogy is a fantastic mess to get right. * Screen printing is easy enough (Hi!). * As is screen scraping (Hi again!), but you kind of have to find something to match against. We went with solid strips of colors, because that's easy enough to do, and hopefully universal enough. @frostschutz went with a full scanline here, which is trickier, especially if font rendering is involved (because your pattern will basically be device AND FW-specific, or nearly so). * Actually playing nice with Nickel may be tricky, depending on how you end up running things and exactly how much control & safety you want to enforce (c.f., KFMon's teething pains in its infancy on that front). ---- I mentioned screen scraping, because getting anything interesting out of Nickel is pretty hard, so, that's one obvious solution. The other is "simply" monkey patching Nickel at run-time to catch the relevant function calls, but in that case you can probably forget about anything else and just go with that . (c.f., a few random posts on that subject over here). Last edited by NiLuJe; 09-21-2018 at 01:20 AM.