View Single Post
Old 07-23-2013, 03:38 AM   #338
hawhill
Wizard
hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.
 
hawhill's Avatar
 
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
Koreader has its own widgets, fully coded in Lua. As BWinmill said, we just use CREngine to render some of the supported document formats (the "ebook" formats, as opposed to the "ready typeset" formats like PDF and DJVU). Koreader is thus a frontend to various document renderers. CoolReader is closely entangled with CREngine, but is also more or less a frontend to the CREngine, which works as a rendering backend there, too.

The file manager, which really really could use some programming love, is Koreader's own. KindlePDFviewer, a predecessor of Koreader, was a bit further in that regard. I guess Koreader will step up to that in the following 1-2 months. A bit bigger entries, icons, maybe title page display option, metadata - a lot could be done there. KPV even hat file manager capabilites like C&P, rename, deletion, ... What's needed in the end is some programmer time.
hawhill is offline   Reply With Quote