|
|
|
|
<html>
|
|
|
|
|
<head>
|
|
|
|
|
<link href="kjsembed.css" rel="stylesheet" type="text/css">
|
|
|
|
|
<title>KJSEmbed and TQSA</title>
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
<h1>KJSEmbed and TQSA</h1>
|
|
|
|
|
<hr>
|
|
|
|
|
|
|
|
|
|
<h3>Introduction</h3>
|
|
|
|
|
|
|
|
|
|
There are a lot of similarities between TQSA and KJSEmbed, and this has
|
|
|
|
|
led to some confusion. This document aims to shed some light on the
|
|
|
|
|
differences between the two libraries.
|
|
|
|
|
|
|
|
|
|
<h3>The Differences</h3>
|
|
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
<li>TQSA has a nice built in script editor which kjsembed does not,
|
|
|
|
|
but kjsembed can load designers ui files anyway and it would be easy
|
|
|
|
|
to add.</li>
|
|
|
|
|
|
|
|
|
|
<li>KJSEmbed has facilities for working with TDEActions and can even
|
|
|
|
|
load them from XML files.</li>
|
|
|
|
|
|
|
|
|
|
<li>KJSEmbed makes it easier to operate with Qt types than TQSA. Take
|
|
|
|
|
a look at the <a href="types.html">types documentation</a> for more details.</li>
|
|
|
|
|
|
|
|
|
|
<li>KJSEmbed has support for KDE specific types such as KURL. TQSA
|
|
|
|
|
does not support these types by default, but does provide facilities
|
|
|
|
|
for adding support yourself.</li>
|
|
|
|
|
|
|
|
|
|
<li>KJSEmbed can access the DOM from a TDEHTML part so it can work
|
|
|
|
|
nicely with HTML and XML documents. Note that this binding is only
|
|
|
|
|
available if the host application chooses to publish the DOM to the
|
|
|
|
|
interpreter.</li>
|
|
|
|
|
|
|
|
|
|
<li>KJSEmbed is LGPL while TQAS is GPL.</li>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<hr>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
