On Thursday 30 June 2011 22:21:43 Benjamin Poulain wrote:
Hi all,
Andreas and I have worked a couple of days on a ways to clean the
current mess of the WebKit 2 API. We would like some feedback before
going forward and upstreaming some of that :)
I has become visible that the current
A simple API based directly on WebCore could easily be done for that,
though it is not a priority for us and we would need to analyze the
use-cases well. It is an open source project and we will support
efforts like this.
Kenneth
On Sat, Jul 2, 2011 at 2:29 PM, Pierre pina...@pinaraf.info wrote:
On Jul 2, 2011, at 5:29 AM, ext Pierre wrote:
Some of problems we have are:
-the split QWKPage - QGraphicsWKView comes from the design of our
WebKit 1 APIs, and is just adding complexity (we do not want to support
multiple views, and we do not want to support a page without a view).
Does
Hi there,
On Thu, Jun 30, 2011 at 10:21 PM, Benjamin Poulain
benjamin.poul...@nokia.com wrote:
Hi all,
Andreas and I have worked a couple of days on a ways to clean the current
mess of the WebKit 2 API. We would like some feedback before going forward
and upstreaming some of that :)
Great
On 07/01/2011 11:46 AM, ext Kenneth Rohde Christiansen wrote:
We have been playing with the code, trying to break it in less monstruous
parts.
This is available here:
https://github.com/kling/webkit/tree/master/Source/WebKit2/UIProcess/API/qt
The goals:
-clarify the responsibilities of each
01.07.2011, 18:53, viatcheslav.ostape...@nokia.com:
-simplify APIs to something minimal: QMobileWebView (the viewport) +
QMobileWebPage (the view on the page) for mobile. QDesktopWebView as
the only view for mobile.
Mobile/Desktop - sounds odd. Who knows, where will be mobile or desktop
Hi all,
Andreas and I have worked a couple of days on a ways to clean the
current mess of the WebKit 2 API. We would like some feedback before
going forward and upstreaming some of that :)
I has become visible that the current design of the UI layer of WebKit 2
is not maintainable. The code
