4 ms·

KHTML was hardly embeddable, portable, or language/toolkit agnostic at the time.

• lmm 10y ago
  It was absolutely embeddadble - the KPart was a first-class supported way of using it (widely used in other KDE applications) - and at least somewhat portable (KDE on windows predates WebKit).
  • gcp 10y ago
    But didn't KPart rely on KDE (libs)? That's hardly embeddable in any meaningful sense. Gecko was embeddable too if everything you wrote was XUL :-)
    • lmm 10y ago
      Kdeui was (and remains) a first-class toolkit for writing arbitrary applications (and widely used as such) in a way that XUL has never really been.
      • pcwalton 10y ago
        I think "embeddable" means at least "I have an arbitrary Charles Petzold-style Win32 app and I want to put KHTML in it without adopting my whole app to a framework". KParts was never really designed for this.