MobileRead Forums - View Single Post

ah- · 01-05-2012, 12:34 AM

Hi,

I played around with my Kobo Touch a bit tonight and wonder if the plugin interface (https://github.com/kobolabs/Kobo-Rea...ginInterface.h) is supposed to work with it?

I set the development environment up as described on http://blog.ringerc.id.au/ and compiled the poker example, copied the .so to the reader but I can't get it to load. I noticed that the plugins are started depending on their mimetype and you can edit the sqlite-database such that you have a "book" that starts an application, by setting the mimetype of an entry in the content table to e.g. "application/x-games-Sudoku". While this works for sudoku, it doesn't for the poker example.
It seems the .so isn't even properly loaded as some debug output I added doesn't appear in the stdout of nickel.

Furthermore, I'm not able to restart nickel after killing it (http://blog.ringerc.id.au/2011/01/co...kobo-wifi.html). This causes the reader to lock up and resetting it all the time is rather annoying

And, if the plugin interface doesn't work, has anyone investigated other methods to extend the firmware? I guess locally serving webpages might also work for simple stuff.

01-05-2012, 12:34 AM	#1
ah- Connoisseur Posts: 64 Karma: 7786 Join Date: Jan 2012 Device: Kobo Touch	Kobo Touch Plugin Interface Hi, I played around with my Kobo Touch a bit tonight and wonder if the plugin interface (https://github.com/kobolabs/Kobo-Rea...ginInterface.h) is supposed to work with it? I set the development environment up as described on http://blog.ringerc.id.au/ and compiled the poker example, copied the .so to the reader but I can't get it to load. I noticed that the plugins are started depending on their mimetype and you can edit the sqlite-database such that you have a "book" that starts an application, by setting the mimetype of an entry in the content table to e.g. "application/x-games-Sudoku". While this works for sudoku, it doesn't for the poker example. It seems the .so isn't even properly loaded as some debug output I added doesn't appear in the stdout of nickel. Furthermore, I'm not able to restart nickel after killing it (http://blog.ringerc.id.au/2011/01/co...kobo-wifi.html). This causes the reader to lock up and resetting it all the time is rather annoying And, if the plugin interface doesn't work, has anyone investigated other methods to extend the firmware? I guess locally serving webpages might also work for simple stuff.