View Single Post
Old 08-15-2016, 01:43 AM   #4
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
To start a Kindlet:
Code:
lipc-set-prop com.lab126.appmgrd start app://com.lab126.booklet.kindlet/mnt/us/path/to/kindlet.azw2
So I assume you do the same thing only with the lab126 reader framework for standard book types (but I am much too lazy to look it up right now before bed, sorry).

Not sure why anyone wants that though. KindleMenu uses it to launch Kindlets that are otherwise hidden from cluttering your library list. And KPVBooklet already handles alternative filetypes to be listed in the library list and opened through KOReader.


How much utility is gained from opening a catalog book straight through a KUAL extension, anyway? It is not like books are hard to find (but if they are, you might have bigger problems -- namely, organization).
eschwartz is offline   Reply With Quote