Does Sigil need an epub e-reader component?
Does Sigil need its own e-reader component for reading/final layout checks?
Given Sigil and PageEdit both use QtWebengine (Chrome based) and the existence of projects like Readium Cloud Reader and futurepresses epub.js and epub.js-reader, I think it would be relatively painless to combine QtWebEngine with these pure javascript solutions to create a standalone desktop epub3 compliant e-reader with pagination, dual page spreads, and etc specifically for Desktop Windows, MacOS, and Linux.
Would this be of any value to Sigil epub devs? Or would it create just one more reading system to worry about?
I ask because both Readium and futurepress approaches work well with current browsers if local file restrictions and cross-site scripting restrictions are lifted. These restrictions are something we control in QtWebEngine.
And Chrome's removing/restricting extensions means that Chrome based versions of Readium via extensions may be an issue in the future.
In addition, if we build the app ourselves to work with local files, we can be assured that no geo, or tracking data is ever used or even generated.
I am personally getting quite tired of how much Mac Desktop app store code includes tracking modules (which they claim is specifically meant for program improvements). Many open source projects are being repackaged with tracking libraries in these app store versions. They are supposed to be safe according to the app store but I simply do not trust them in any way.
General thoughts? Useful or simply wasteful duplication?
KevinH
|