Quote:
Originally Posted by Peter Blaise
|
Quote:
Originally Posted by Peter Blaise
Hey, Firefox and Opera work in Windows XP, Google Chrome brickwalling XP is whimsical.
|
Nice one. Let me draw your attention to a specific subsection of your own link.
https://doc.qt.io/qt-5/supported-pla...tml#exceptions
Quote:
|
Individual modules might be available only on some platforms, or they might not support all configurations. For example, as Qt WebEngine has Chromium as a third-party dependency, platform or configuration limitations upstream also apply to Qt WebEngine.
|
In fact, calibre uses webengine as its ebook-viewer base in addition to one or two things in the main program. If webengine is unusable on Windows 7 due to Google being unpleasant to work with, well, guess what? You ironically called it.
Qt formally documents webengine as not supported on Windows 7 "because Google said no".
But you can use workarounds to install it anyway, and just remember to not use certain parts lest it crash on you or manifest as a blank screen.
Your problem is literally Google Chrome.
...
Aside: the Google Chrome situation is a disaster. With everything wrong with the overreach of the modern web, Google Chrome is somehow even worse and we all suffer for it. Unfortunately, everyone seems to be making the truly disastrous decision to embed chromium into their program in order to "do web stuff".
It's the only viable, maintained Qt module, since webkit is constantly issueful and at best getting drips of life support. But even webkit is basically embedded chromium.
Electron uses it. Because clearly we need to make all apps by running a separate, new instance of chromium to eat batter, refuse to go to sleep, etc.
Unfortunately, it is what it is, and ebooks do need to use *a* browser engine, being they use HTML and all... pity that browser engine must be chromium.
If you have a solution to this, I'm sure lots of people would love to hear it. chrome/webengine is unavailable on various OSes for a mix of ethical and practical reasons -- upstream chromium won't support non-glibc targets on Linux thus locking out many Gentoo or Void Linux users and all Alpine users, won't support anything else other than Windows/macOS thus locking out the *BSDs, and FSDG distributions consider chromium to be proprietary/nonfree and blacklist it as bad for the user.
And even if you don't care about the ethical or practical reasons for not permitting it to be installed, again, it is painfully slow and bloated. Because it is a browser!
I eagerly await your masterful suggestions. In the meantime, try to avoid assuming the developer is just downright clueless about Windows 7 support.