[webkit-dev] Announcing WebKit for Wayland

[Žan Doberšek]

On Wed, Dec 10, 2014 at 9:46 AM, Žan Doberšek <zandobersek at gmail.com> wrote:

> On Tue, Dec 9, 2014 at 5:52 PM, Gyuyoung Kim <gyuyoung.kim at webkit.org>
> wrote:
>
>> Hello,
>>
>> > Do you know what are the plans for GTK and EFL?
>>
>> As far as I know, EFL community has tried to support wayland. Thus some
>> folks of WebKit EFL port seem to plan to support the wayland based of EFL
>> support when it is ready.
>
>
> Basically same goes for the GTK+ port -- we mainly rely on the toolkit to
> properly support the Wayland protocol.
>
> Despite that we must deploy a few custom solutions for specific problems.
> For instance, in order to efficiently transfer the composited results from
> the WebProcess to the Wayland compositor we are planning to use a nested
> Wayland compositor in the UIProcess to relay that data to GTK+.
>
> First implementations of this approach ended up blitting the rendered data
> onto the Cairo surface of the relevant GtkWidget. To make things worse, the
> surface was using shared memory, and had its data invalidated completely
> whenever the GtkWidget had a redraw queued. This meant that
>

... a whole lot of data was being sent to the parent compositor for each
update of the widget, which obviously caused problems on weaker embedded
systems running in 1080p resolution.

Luckily in the last few months GTK+ finally received support for drawing
OpenGL content in GtkWidgets, so the final implementation will be much more
efficient.

Cheers,
Zan


>
>
>>
>> Gyuyoung.
>>
>>
>> On Wednesday, December 10, 2014, Benjamin Poulain <benjamin at webkit.org>
>> wrote:
>>
>>> Hi Žan,
>>>
>>> Thanks for announcing this project here.
>>>
>>> Can you explain a bit why you decided to use the UIProcess directly
>>> inside the compositor?
>>>
>>> I am a bit concerned about the security of this model because the
>>> UIProcess becomes an attack vector for the compositor. Sharing the memory
>>> space with the compositor would prevent aggressive sandboxing.
>>>
>>> Great Wayland support seems like an important target for WebKit on
>>> Linux. Do you know what are the plans for GTK and EFL?
>>>
>>> Benjamin
>>>
>>>
>>> On 12/9/14 7:44 AM, Žan Doberšek wrote:
>>>
>>>> Hi,
>>>>
>>>> now with proper formatting, Igalia is happy to announce the Wayland port
>>>> of WebKit.
>>>>
>>>> This port avoids using traditional GUI toolkits in favor of directly
>>>> operating with the Wayland display protocol. Leveraging the WebKit2
>>>> multi-process architecture, the UIProcess is implemented as a shared
>>>> library and loaded by the Wayland compositor, enabling the WebProcess to
>>>> act as a direct client of the compositor while still being controlled by
>>>> the UIProcess.
>>>>
>>>> EGL, the Wayland EGL platform, and OpenGL ES are used for
>>>> hardware-accelerated compositing of the rendered Web content. GLib,
>>>> Libsoup and Cairo are used under the hood.
>>>>
>>>> The port serves as a good base for building systems and environments
>>>> that are mostly or completely relying on the Web platform technologies
>>>> for building the desired interface.
>>>>
>>>> Overall the port is still in its early days, with some basic
>>>> functionality (e.g. functional keyboard and mouse input support) and
>>>> many other Web platform features still not supported. But with Wayland
>>>> EGL support constantly growing in graphics drivers for different GPUs,
>>>> it can already be tested on devices like the Raspberry Pi or the Jetson
>>>> TK1 development board.
>>>>
>>>> In terms of supported Wayland compositors, for the moment we only
>>>> support Weston (the reference Wayland compositor implementation), which
>>>> is also used for development purposes. It's also used for running the
>>>> layout tests by again pushing WebKitTestRunner functionality into a
>>>> shared library, though all that is still in very early stages.
>>>>
>>>> The code is available on GitHub. There are also short instructions for
>>>> building the dependencies and the port, and how to run it.
>>>> https://github.com/WebKitForWayland/webkit
>>>>
>>>> There's also additional repositories there (for Cairo, Weston),
>>>> containing changes that haven't yet been pushed upstream. In the
>>>> following days we'll also be providing Buildroot configurations that can
>>>> be used for cross-compiling the whole software stack for the supported
>>>> hardware.
>>>>
>>>> We look forward to continuing evolving this work, enabling further
>>>> features and improving performance on the software side and adding
>>>> support for additional devices. As with all open-source projects,
>>>> contributions are welcome.
>>>>
>>>> Regards,
>>>> Zan Dobersek
>>>>
>>>>
>>>> On Tue, Dec 9, 2014 at 7:28 AM, Žan Doberšek <zandobersek at gmail.com
>>>> <mailto:zandobersek at gmail.com>> wrote:
>>>>
>>>>     Hi,
>>>>     Igalia is happy to announce the Wayland port of WebKit.
>>>>     This port avoids using traditional GUI toolkits in favor of directly
>>>>     operating with the Wayland display protocol. Leveraging the WebKit2
>>>>     multi-process architecture, the UIProcess is implemented as a shared
>>>>     library and loaded by the Wayland compositor, enabling the
>>>>     WebProcess to act as a direct client of the compositor while still
>>>>     being controlled by the UIProcess.
>>>>     EGL, the Wayland EGL platform, and OpenGL ES are used for
>>>>     hardware-accelerated compositing of the rendered Web content. GLib,
>>>>     Libsoup and Cairo are used under the hood.
>>>>     The port serves as a good base for building systems and environments
>>>>     that are mostly or completely relying on the Web platform
>>>>     technologies for building the desired interface.
>>>>     Overall the port is still in its early days, with some basic
>>>>     functionality (e.g. functional keyboard and mouse input support) and
>>>>     many other Web platform features still not supported. But with
>>>>     Wayland EGL support constantly growing in graphics drivers for
>>>>     different GPUs, it can already be tested on devices like the
>>>>     Raspberry Pi or the Jetson TK1 development board.
>>>>     In terms of supported Wayland compositors, for the moment we only
>>>>     support Weston (the reference Wayland compositor implementation),
>>>>     which is also used for development purposes. It's also used for
>>>>     running the layout tests by again pushing WebKitTestRunner
>>>>     functionality into a shared library, though all that is still in
>>>>     very early stages.
>>>>     The code is available on GitHub. There are also short instructions
>>>>     for building the dependencies and the port, and how to run
>>>>     it.https://github.com/WebKitForWayland/webkit
>>>>     There's also additional repositories there (for Cairo, Weston),
>>>>     containing changes that haven't yet been pushed upstream. In the
>>>>     following days we'll also be providing Buildroot configurations that
>>>>     can be used for cross-compiling the whole software stack for the
>>>>     supported hardware.
>>>>     We look forward to continuing evolving this work, enabling further
>>>>     features and improving performance on the software side and adding
>>>>     support for additional devices. As with all open-source projects,
>>>>     contributions are welcome.
>>>>     Regards,Zan Dobersek
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> webkit-dev mailing list
>>>> webkit-dev at lists.webkit.org
>>>> https://lists.webkit.org/mailman/listinfo/webkit-dev
>>>>
>>>>
>>> _______________________________________________
>>> webkit-dev mailing list
>>> webkit-dev at lists.webkit.org
>>> https://lists.webkit.org/mailman/listinfo/webkit-dev
>>>
>>
>>
>> --
>> Sent from Gyuyoung Iphone
>>
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> https://lists.webkit.org/mailman/listinfo/webkit-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-dev/attachments/20141210/7c965b81/attachment.html>