View Single Post
Old 10-15-2013, 08:36 AM   #7
At_Libitum
Addict
At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.
 
Posts: 265
Karma: 724240
Join Date: Aug 2013
Device: KyBook
Quote:
Originally Posted by GRiker View Post
@At_libitum, the iOS reader applications plugin uses its own internal architecture independent of calibre. Any method beginning with an underscore is a local method. Methods beginning with a letter are required by calibre's plugin architecture.

_view_book() is a local method - you would need to replace it or modify it in your overlay.

G
That much I gathered, and that was what I did with _view_book(), including a local copy as the term 'overlay' had caused me to assume these same named methods were overriding the ones in device.py. Apparently I am mistaken. But then how do I make the code also actually use my version of _view_book() when pressing V in device view? Do I need to go up the chain and also include a local copy of view_book() ?

Last edited by At_Libitum; 10-15-2013 at 08:46 AM.
At_Libitum is offline   Reply With Quote