Discussion
Continuing my study of Papyrix's pivotal "Reader" UI state... How does it render its different substates? And perhaps I'll discuss substate event handling too?
To render the current page it retrieves the file's filetype & the current theme, clears the screen to the theme's background colour, checks if we're on the 1st page of the 1st "spine" in which case it should render cover image if any, considers a configurable double-refresh, ...
1/?
To render pages for ePub, Txt, Markdown, FB2, or HTML ebooks Papyrix's "Reader" UI state has a method which retrieves the current theme, ebook's filetype, & the display's viewport before validating we haven't finished the ePub or FB2 ebook, stopping the background caching, possibly resetting the parser, initializing caching if necessary, renders & caches the page itself (via couple helpers, ultimately dispatching to the appropriate class) possibly displaying a progress or error message, ...
3/?
... clears the display again, loads the page from that cache, clears cache upon failure, loads the configured font, asks (via a helper) the page to render itself with the configured page & font, retrieves (via another helper) data for a status bar & asks external code to render it, refreshes display in one of 5 different ways (3 via a helper), if rendering anti-aliased text rerenders a few different times combining results, & logs what it has done.
4/5?
As for the method to render pages of XTC ebooks... It defers to an XtcRenderer before refreshing the displaying or rendering the appropriate error message.
I'll leave it there for today, with how much effort they put into their program's core task of rendering pages of an ebook... This thread has gotten long enough!
4.5/4.5 Fin for today! Tomorrow: The other substates with their rendering & user-input handling!
Install bonfire.cafe
Get the full app experience
... branches over the filetype to render the actual page in one of 2 ways, possibly starts background caching, & marks the display as dirty. To render the cover page where relevant a helper logs what its doing, asks the ebook's class to render the cover, if successful retrieves the frame's viewport, & renders that image there. If there was no cover the current page renderer updates its properties to something valid.
XTC renders pages specially, but otherwise...
2/?