D8211: KDevelop/Documentation : support using QTextBrowser (WIP/PoC)
René J.V. Bertin
noreply at phabricator.kde.org
Sun Oct 8 23:38:32 UTC 2017
rjvbb added a comment.
I'm tempted to think that anything too complex to be rendered correctly is probably not really meant to be used in a simple embedded browser anyway.
Qt have considered QTextBrowser sufficient to be used as the default render backend in the Assistant. In practice, the only things in QtHelp documentation I've encountered that didn't render properly with QTB were the inline copies of source files.
If that's a concern, well, just use QWE or QWK instead of QTB...
BTW, don't the quick help tooltips use QTB?
Why did I bother? Because the idea of running what's essentially a full-blown webbrowser bothers me, knowing that KDevelop is already resource hungry enough as it is and that the documentation in question can be rendered well enough with QTB.
The implementation is indeed a bit more complicated than I thought it would be in the beginning but can probably be optimised. And as far as I'm concerned we could remove the QtWebKit support if this goes in.
To: rjvbb, #kdevelop
Cc: apol, kdevelop-devel, geetamc, Pilzschaf, akshaydeo, surgenight, arrowdodger
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel