Thread: Putting ebooks, NIT and big sales into the same sentence
View Single Post
attila77 is offline attila77
2009-05-20 , 20:12
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#19
Originally Posted by qole View Post
That's fairly defeatist! There has to be a way to feed the HTML renderer just enough to keep it from choking under the weight of the book. You could have the e-book app break the text up into page-sized chunks (the user can specify this, and/or it can be specified in the text), and then just have a page turning button or auto-load the next page as you approach the bottom of the current page.
...and that is almost perfectly describing what I'm doing now I keep the header/css and then try to split by paragraph/element. The problems are as follows:

- The html navigation gets broken
- Html formatting can be problematic if the original document had the text in a giant DIV or TABLE (if I loose the element, I'm loosing any style/formatting applied to it).

Also, in that case webkit is a bit of an overkill. If it's just static text, cut to manageable chunks, the 'goold old' QTextDocument will do just as fine (actually better, as it uses a lot less memory and does not need webkit installed).
 

The Following User Says Thank You to attila77 For This Useful Post: