D8211: KDevelop/Documentation : implementation of a QTextBrowser-based viewer

Aaron Puchert noreply at phabricator.kde.org
Fri Oct 20 20:46:52 UTC 2017

aaronpuchert added a comment.

  The discussion is getting really nasty and I don't think it leads anywhere.
  In https://phabricator.kde.org/D8211#157277, @kossebau wrote:
  > KDevelop is by definition a "feature-full, **plugin extensible** IDE for C/C++ and many other programming languages."
  Maybe this is the way to go. Can't there be a documentation viewer interface, with multiple plugins implementing it, maybe some built by default, others if the necessary dependencies are available? Then some people can use a QWebKit-based viewer, others a QWebEngine-based viewer, and so on. I agree regarding the `#ifdef`s, this is really nasty and can't be the solution.
  The common denominator seems to be that we want access to documentation from our code. If different developers implement different variants for doing that, why not? But they shouldn't interfere with each other. Ideally, none of the implementations should need to be aware of any of the others. That is not the case here.
  If some implementation ends up being unmaintained for a long time, and nobody uses it anymore, then it may go the way of all obsolete code.

  R32 KDevelop


To: rjvbb, #kdevelop
Cc: kfunk, croick, kossebau, aaronpuchert, flherne, arichardson, apol, kdevelop-devel, geetamc, Pilzschaf, akshaydeo, surgenight, arrowdodger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20171020/762337ef/attachment.html>

More information about the KDevelop-devel mailing list