[wpe-webkit] Fate of wpebackend-rd and WpeLauncher

Vanhauwaert Wouter W.Vanhauwaert at TELEVIC.com
Mon Sep 17 06:11:37 PDT 2018

> -----Original Message-----
> From: Munez Bn [mailto:munezbn.dev at gmail.com]
> Sent: maandag 17 september 2018 13:08
> To: Vanhauwaert Wouter
> Cc: aperez at igalia.com; webkit-wpe at lists.webkit.org
> Subject: Re: [wpe-webkit] Fate of wpebackend-rd and WpeLauncher
> On Mon, Sep 17, 2018 at 3:36 PM Vanhauwaert Wouter
> <W.Vanhauwaert at televic.com <mailto:W.Vanhauwaert at televic.com> >
> wrote:
> 	>       > wpebackend-fdo is added (doesn't have much idea on this)
> 	>
> 	>       The idea for the FDO backend is that the backend does not
> “talk”
> 	> directly to
> 	>       the display. Instead, it tries to be generic and provides a
> mechanism
> 	> to
> 	>       notify the launcher when a frame has been rendered. Then the
> 	> launcher can
> 	>       use the method it prefers to display the frames. In theory it
> should be
> 	>       possible to replace many backends with the FDO one, but not
> much
> 	> has been
> 	>       done on that front.
> 	>
> 	>
> 	>
> 	> Sorry , I couldnt get it.  Is FDO a replacement for rdk backend or
> supplement.
> 	> And also what if i don't want to use wayland. For example RPI uses
> 	> Dispmanx. Can I use FDO + Dispmanx ?
> 	> This was possible with wpebackend-rdk where I could use RPI port
> without
> 	> wayland. I also saw there are some BCM ports which uses nexus
> instead of
> 	> wayland.
> 	>
> 	>
> 	Hello,
> 	I also want to elaborate a bit on the wpebackend-rdk story. I also
> don't know what the future will be or what the intentions here are.
> 	A few weeks ago, I already made a pull request to adapt
> wpebackend-rdk to the new libwpe. It is able to run fine together, but it
> seemed nobody replied to my pull-request, and also it was not very clear
> what to use now, so I closed it again...
> https://github.com/WebPlatformForEmbedded/WPEBackend-rdk/pull/26
> 	I also don't use wayland, but using the egl vivante-backend (imx6)
> directly (just as bcm/rpi). It looks like all efforts go to wpebackend-fdo now?
> Great. So you have tried  libwpe + Wpebackend-rdk ( imx6) . Any code
> changes was required ?  And which launcher did you use ? COG or the
> WpeLauncher ? I would like to try it on  RPI 3.
> Anyway lets wait for someone to confim on  our questions.

Well, assuming you also make use of wpewebkit-2.21.91, you don't have to change code. You only have to adapt the libwpe change in wpebackend-rdk as I mentioned in my pull request. Wpewebkit-2.20.2 still makes use of wpebackend instead of libwpe and old api if I'm not mistaken, so no need to change there. That's what I meant that development really looks a bit fuzzy right now, for people not really involved in the roadmap... I think it will all lighten up when 2.22 is released and things can all move forward in one hop. I didn't try a launcher lately, I'm running from my application directly, using the gtk+-api

More information about the webkit-wpe mailing list