View Single Post
Old Yesterday, 06:48 PM   #11
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 50,573
Karma: 178402706
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Aleron Ives View Post
I'm behind the times. When did Kobo switch from WebKit to Readium? Are there any pros/cons to the new engine?
When Kobo entered the Japanese market, they started with ACCESS' NetFront™ BookReader v1.0 EPUB Edition which was later modified to be WebKit based. In the meantime, ACCESS donated their PUBLUS™ Reader engine to the Readium project and their NetFront™ BookReader technology was integrated into the Readium EPUB 3 reference platform. Readium is based on WebKit (and by extension, Chromium/Blink).

The newest version is an evolution of the previous versions. I'm not sure which Readium SDK it is based on but most likely the Readium 2 Desktop SDK for Linux (basically, the same code base used for Thorium for Linux).
DNSB is offline   Reply With Quote