Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of brian.leroux@gmail.com
 designates 209.85.214.175 as permitted sender)
MIME-Version: 1.0
Sender: brian.leroux@gmail.com
In-Reply-To: <4F0F2650.9080709@nokia.com>
References: <4F0E1D45.5090007@nokia.com>
	<4F0F2650.9080709@nokia.com>
Date: Thu, 12 Jan 2012 14:08:05 -0800
Message-ID: 
 <CADVgkyPSBPp_ySoh8-V1-J4r7w6Mh84opdgG-n7HJwoxRfO1mA@mail.gmail.com>
Subject: Re: [callback-qt] Qt 5, WebKit2 & Qt Quick
From: Brian LeRoux <b@brian.io>
To: callback-dev@incubator.apache.org
Cc: ext Viras <viras@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Quim, is this work going to be contributed back to the Apache Cordova
proj or is it a feature parity thing in Qt5 itself?

On Thu, Jan 12, 2012 at 10:28 AM, Quim Gil <quim.gil@nokia.com> wrote:
> The main developers of the PhoneGap for Qt 4 project believe that the wor=
k
> on Qt 5 should be simple. Let's see if I can explain why it's not based o=
n
> my own learnings - while the real WebKit and QtWebKit maintainers explain
> their views on the project.
>
> On 01/11/2012 10:51 PM, ext Viras wrote:
>> I'm not sure if there is really that much to do.
>
> I wish you are right =A0:) but at least the WebKit developers at Nokia be=
lieve
> that the change to Qt 5 is indeed significant.
>
> WebKit2 is basically a new API. The WebKit(1) API is being left behind.
>
> The API for QtWebKit(1) was based on QWidget, but QWidget is an optional
> module in Qt 5 and it may well be that mobile platforms don't ship it at
> all.
>
> Qt 4 has the convenient QtWebKit Bridge mechanism to connect WebKit/JS wi=
th
> C++ native objects. But QtWebKit Bridge is really tied to Qt 4 and is not
> making it as such to Qt 5.
>
> See
>
> http://trac.webkit.org/wiki/QtWebKitForQt5
> http://labs.qt.nokia.com/2011/08/31/an-oldnew-approach-to-qtwebkit-hybrid=
/
>
>
>> That way porting to Qt5 most probably will be the work of a few
>> afternoons (after all, I re-wrote the whole Qt4 code in a few days as a
>> single person).
>
> I don't know how many afternoons will it take to get the PhoneGap API ful=
ly
> covered in Qt 5.
>
> But I specially don't know how many extra afternoons will be needing to g=
et
> a release stable and with a good level of performance. It doesn't seem to=
 be
> a trivial task for the iOS, Android and Windows Phone ports, so I'm not
> expecting this to be trivial for Qt 5 either.
>
> --
> Quim