René J.V. Bertin
rjvbertin at gmail.com
Thu Sep 14 16:20:02 BST 2017
I recall that we discussed depending on <insert "abjective" here> QtWebEngine for displaying HTML-based documentation and that I wasn't the only one who thought that'd be overkill and that QTextBrowser should be good enough.
Yet I see it's now beginning to take over the documentation library (plugin?) without fallback on QTextBrowser or exposing the still existing QtWebKit support as a build option.
I don't know what others think, but I already have a Chrome webbrowser running all the time. Rather than bloating my IDE with another runtime copy of that monstrosity I'd prefer the option to hand off html docs to that external browser if I see they're too complex for QTextBrowser. That would also provide the doc in a proper external window that won't disappear if your focus ("follows mouse") changes and won't ever pop back up as a poltergeist the next time you launch the session.
More information about the KDevelop