Thread: Kobo page fitting
View Single Post
Old 09-19-2013, 09:14 PM   #18
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 ShellShock View Post
I think you have over-stated your case. Kobo seems to be perfectly capable of adding new, peripheral, features that I personally have no interest in (social media etc), but ignore these enhancements that would greatly improve the core reading experience for a lot of people.
No, I think I am understating the case. But, we are also talking about two different things. Adding a separate feature like Pocked would have relatively little affect on the existing code. It will reuse libraries but most of the code written will be new. It might mean changes to the existing libraries, but can have surprisingly little impact on it.

Adding something like the desired options for the header and footer of the reading page is changing the existing code base. That need someone to go through the existing code, find all references to the current header and footer, make sure they use parameters, make sure that anything that interacts with them is handling that correctly, make sure that anything that interacts with this also works.
davidfor is offline   Reply With Quote