diff options
Diffstat (limited to 'kjsembed/docs/kjsembed-qsa.html')
| -rw-r--r-- | kjsembed/docs/kjsembed-qsa.html | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/kjsembed/docs/kjsembed-qsa.html b/kjsembed/docs/kjsembed-qsa.html index 2de920d8..9355c268 100644 --- a/kjsembed/docs/kjsembed-qsa.html +++ b/kjsembed/docs/kjsembed-qsa.html @@ -1,32 +1,32 @@ <html> <head> <link href="kjsembed.css" rel="stylesheet" type="text/css"> -<title>KJSEmbed and QSA</title> +<title>KJSEmbed and TQSA</title> </head> <body> -<h1>KJSEmbed and QSA</h1> +<h1>KJSEmbed and TQSA</h1> <hr> <h3>Introduction</h3> -There are a lot of similarities between QSA and KJSEmbed, and this has +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>QSA has a nice built in script editor which kjsembed does not, + <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 KActions and can even load them from XML files.</li> - <li>KJSEmbed makes it easier to operate with Qt types than QSA. Take + <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. QSA + <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> @@ -35,7 +35,7 @@ differences between the two libraries. available if the host application chooses to publish the DOM to the interpreter.</li> - <li>KJSEmbed is LGPL while QAS is GPL.</li> + <li>KJSEmbed is LGPL while TQAS is GPL.</li> </ul> <hr> |