[bt-devel] General Book Navigation

[Matthew Talbert]

On Thu, Dec 2, 2010 at 1:20 PM, Greg Hellings <greg.hellings at gmail.com> wrote:
>
> On Thu, Dec 2, 2010 at 1:24 AM, Ben Morgan <benpmorgan at gmail.com> wrote:
> > On Thu, Dec 2, 2010 at 5:27 PM, Gary Holmlund <gary.holmlund at gmail.com>
> > wrote:
> >>
> >> I suspect that there are some large books that might be to big for
> >> performance and memory size reasons.
> >
> > Absolutely. Some of them are huge (early church fathers for example). What
> > we do in BPBible 0.5 is lazy loading (scroll up/down and you get new
> > content), which works reasonably well.
>
> From what I've read, BPBible uses wx and therefor probably the wxHTML
> widget?  The performance of wxHTML (and previously the BibleTime
> KHTML) widget is terrible.  The first time I tried to open one of
> these modules using a wxHTML widget it took upwards of 5 minutes,
> whereas Firefox was able to gobble it up in a few seconds.
>
> I would imagine QtWebKit to be more akin (and maybe faster) to
> Firefox's performance than wx's.  I'll give it a go and see how it
> turns out with Early Church Fathers.  Also, when you say "lazy
> loading" do you mean the user can scroll continuously through the
> entire work, and you just feed the widget more data as it is needed?
> Because that would be an equivalent Use Case with better
> under-the-hood performance.

I'd guess it doesn't really matter the widget you're using, when
you're trying to open 115+ MB of data...

Matthew