<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Jaak,<br>
<br>
10.04 has got Qt 4.6.2. <br>
12.04 will supersede it soon and be supported for a longer time. <br>
<br>
Regards, mg<br>
<br>
Am 14.11.11 10:00, schrieb Jaak Ristioja:<br>
<blockquote type="cite">Hi!<br>
<br>
Yes, we should release at least one other 2.8.#. I'm not sure
whether<br>
changing the requirement from Qt 4.5 to 4.6 would be a good idea
for<br>
2.9.# right now. For later versions, it is no problem. What
version of<br>
Qt does Ubuntu 10.04 (LTS) have?<br>
<br>
Blessings,<br>
Jaak<br>
<br>
On 14.11.2011 09:40, Martin Gruner wrote:<br>
> Hi Gary,<br>
<br>
> very cool!<br>
> AFAIR, we currently require Qt 4.5, where such a "proxy"
class is needed<br>
> to create a bridge between C++ and JS. With Qt 4.6, this is
not required<br>
> any more. So if we decide to up the version, the code could
be changed<br>
> and simplified.<br>
<br>
> Regards, mg<br>
<br>
> Am 14.11.11 06:17, schrieb Gary Holmlund:<br>
>><br>
>> I fixed the problem with the Mag window not working with
newer<br>
>> versions of Qt (Qt 4.7.4 + QtWebKit 2.2 or later). The
current version<br>
>> shipping with Ubuntu 11.10 and Fedora 16 is broken
because of this<br>
>> issue. I know that we will soon release 2.9, but Ubuntu
has been<br>
>> reluctant to upgrade to feature releases. I am wondering
if we should<br>
>> create a 2.8.3 for this fix.<br>
>><br>
>><br>
>> Bug details<br>
>><br>
>> Each BibleTime window uses Qt WebKit classes to display
the page. We<br>
>> use javascript on the page to associate the mouse
coordinates with DOM<br>
>> elements and display the corresponding entry in the Mag
window. The<br>
>> javascript also handles drag/drop and a few other things.<br>
>><br>
>> There is a c++ class (BtHtmlJsObject) that is associated
with the<br>
>> javascript on a page in BibleTime. This class allows c++
to call<br>
>> javascript and javascript to call c++. With the latest
versions of Qt<br>
>> both the class instance and the javascript have a
"security origin".<br>
>> The first time the class instance is associated with the
javascript<br>
>> everything is ok. But when the next page with javascript
is loaded<br>
>> into the window and associated with the same class
instance, they have<br>
>> different security origins. WebKit is checking this and
throwing an<br>
>> cross site scripting error. The javascript does not run
correctly.<br>
>><br>
>> It took a lot of debugging down into Qt to figure this
out. Once I<br>
>> knew the issue I suspected I could fix it by associating
a new class<br>
>> instance with the javascript each time the page is
reloaded. This<br>
>> fixed the problem.<br>
>><br>
>> Gary<br>
</blockquote>
<span style="white-space: pre;">><br>
> _______________________________________________<br>
> bt-devel mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:bt-devel@crosswire.org">bt-devel@crosswire.org</a><br>
> <a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/bt-devel">http://www.crosswire.org/mailman/listinfo/bt-devel</a><br>
></span><br>
<br>
</body>
</html>