Quote:
Originally Posted by frostschutz
You can simulate the tap too, only problem is, the button appears at different coordinate for every device so you have to provide a config file where users can set the coordinate that works unless you want to somehow detect it by looking at the frame buffer itself (I attempted such a thing in my screensaver mod with scanline but it's not a great solution).
Or you could let the user tap the first time and then just replay the same tap in the future, that would work until a firmware update slightly moves the dialog. Then you still have to deal with this popup appearing only after some unknown delay...
It would be nice to find a simpler way, but I don't know of one. I think even the browser just runs an update for the specific book and not search for other ones.
|
That's really interesting. I know how I can take screenshots - but how do you simulate taps? That would seem to be a key component here...
Quote:
Originally Posted by davidfor
You can download a book using the browser. This will add the book to the database.
|
That is not an option: I am running a program in the background and have no way to trigger the web browser. This is the approach taken by
the Chabotsi tutorial, but only as a last resort. I don't like it so much: it means you can't actually use the browser for anything else anymore...
Quote:
Originally Posted by kido.resuri
Currently, as far as I know, the only way for nickel to add new books is to connect to usb, safely disconnect, then nickel processes the content.
|
That is what I observed as well, but I was hoping people would prove me wrong.
Quote:
Originally Posted by kido.resuri
Or maybe you have to "hack" the Kobo database, which has the potential risk of corrupting it and loosing your library. I'm also working on a project that can send content (books) to the Kobo over wifi, I'm trying to hack the built-in Sync and the Bookstore, but that also requires the user to interact with Kobo to get the content. Which is not really bad I think.
|
Yeah, I'm not going to touch the DB directly, except maybe to read metadata, but never write. Too risky and I don't want to rewrite the whole Kobo software, just add to it.
So far I'm using the "wait for tap" approach. It's not so bad, because the process is actually interactive: the user needs to cycle the Wifi connection to trigger the sync anyways, so it's expected that *something* will show up..
Keep the suggestions coming, I'll update the OP with changes...