View Single Post
Old 07-05-2017, 12:30 AM   #6
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by GuyDoodles View Post
Okay, but how is "Safari" questionable? Wouldn't it just imply that the Kobo's expirimental browser borrows features from Safari?
That's probably what they are trying to imply. As it is based on WebKit, it might be justifiable, but I don't know. That's why I stated "questionable".
Quote:
And could somebody explain what nickel's "engine" is? Is it Linux? Qt? On side note, what are fickel and sickel?
nickel is a proprietary application written by Kobo to manage the books on the device. As such, it probably doesn't have an "engine". It uses a pile of libraries include Qt, the Adobe RMSDK and WebKit. The book display, at least for kepubs, uses WebKit.

"fickel" appears to be something with the WiFi. "sickel" is a monitor program that will restart the device if it considers something has hung. Again, both are written by Kobo.
davidfor is offline   Reply With Quote