[Webkit-unassigned] [Bug 71355] [Qt] Merge QTouchWebView and QDesktopWebView into one class

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=71355





--- Comment #1 from Jocelyn Turcotte <jocelyn.turcotte at nokia.com>  2011-11-02 08:23:58 PST ---
We had a chat here are that's what came out.

1. From the point of view of the developer using the WebView it makes more sense to have only one API/documentation with platform specific behaviors defined and documented than having two classes, two documentations and only slight differences between them. Whether you have a desktop behavior or a mobile/touch behavior should be defined by the platform running the application or a compile-time flag.

2. From our point of view, we don't want to have to recompile to be able to switch views, we need a global runtime flag to enable desktop or mobile behavior to run tests or do development. It doesn't make sense to have both a desktop view and a mobile view running in an application at the same time anyway.

3. If we have two different QML API behaviors, this needs to be handled by the same C++ class, not two different C++ classes with somewhat the same methods that are fed to qmlRegisterType depending on the "behavior flag". This will help prevent a developer from running his mobile-aimed application on desktop and get a e.g. [Cannot assign to non-existent property "page"].

So the best way would be to have only one top-level WebView C++ class, that would check this either compile or runtime behavior flag, and would instanciate the proper modules and send the proper settings to the WebProcess (e.g. fixed layout and frame flatening).
Alexis had some plan to implement it I think.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.