MobileRead Forums - View Single Post - iLiad xepdmgr - another approach to auto-refresh

ericshliao · 07-17-2009, 02:35 AM

5-secs to 2-secs? That's really awesome.

I want to clarify something. Based on my understanding, there should not be a 3-secs difference between using xepdmgr and erdm. The real difference between using xepdmgr and erdm should be only 1 sec. 3-secs is too much.
Take ipdf for example, we can get a page refresh in 2 seconds because ipdf preload the next page and write the data to framebuffer while we are reading the current page. Then, when we flip the pagebar, erdm will draw e-ink screen based on the data stored in framebuffer. That's the fast response we can expect for iLiad. Because contentlister does not have such preloading and prefetching mechanism, we get page refreshment in 5-secs. In my homebrew text viewer with xepdmgr, I managed to get next page dispalyed in 3 secs (with preloading but no write to framebuffer). If no preloading, the next page will be dispalyed in 5 secs. And I believe if I implement preloading next page and prefetching data to framebuffer in background in my text viewer, I can get a 2-secs refreshment just like ipdf.

So, based on my current understanding and conjecture, you can get FBReader display next page in 2-secs only if you implement both preloading next page and fetching data to framebuffer. That's quite a complicate job.

07-17-2009, 02:35 AM	#117
ericshliao Guru Posts: 976 Karma: 687 Join Date: Nov 2007 Device: Dell X51v; iLiad v2	5-secs to 2-secs? That's really awesome. I want to clarify something. Based on my understanding, there should not be a 3-secs difference between using xepdmgr and erdm. The real difference between using xepdmgr and erdm should be only 1 sec. 3-secs is too much. Take ipdf for example, we can get a page refresh in 2 seconds because ipdf preload the next page and write the data to framebuffer while we are reading the current page. Then, when we flip the pagebar, erdm will draw e-ink screen based on the data stored in framebuffer. That's the fast response we can expect for iLiad. Because contentlister does not have such preloading and prefetching mechanism, we get page refreshment in 5-secs. In my homebrew text viewer with xepdmgr, I managed to get next page dispalyed in 3 secs (with preloading but no write to framebuffer). If no preloading, the next page will be dispalyed in 5 secs. And I believe if I implement preloading next page and prefetching data to framebuffer in background in my text viewer, I can get a 2-secs refreshment just like ipdf. So, based on my current understanding and conjecture, you can get FBReader display next page in 2-secs only if you implement both preloading next page and fetching data to framebuffer. That's quite a complicate job. Last edited by ericshliao; 07-17-2009 at 02:42 AM.