[MeeGo-dev] Browser EAL?
ab at samba.org
Tue Mar 16 03:36:24 CDT 2010
On Tue, Mar 16, 2010 at 9:22 AM, Tomasz Sterna <tomek at xiaoka.com> wrote:
> Will MeeGo keep the Browser UI and Web Engine Abstraction Layer
> separation of Maemo?
> I think it's worth keeping, since MeeGo is targeted for many
> manufacturers and this will allow them to select the browser engine they
> want to provide to the users.
> This will also allow users to replace the engine if the one provided
> does not fit her.
> There are already Gecko 1.9 EAL (MicroB) and WebKit EAL to choose
In order to do that, you have to have support for separated UI within
the EAL as well.
There are two different types of UI separation: in-process and out-of-process.
In Maemo 5 out-of-process UI separation is used, MicroB EAL runs in a
different process than UI.
Unfortunately, there is no common support for that in current Gecko
and WebKit implementations, they only support in-process EAL/UI
separation. There is ongoing work on Mozilla side to have something
similar to MicroB out-of-process separation (Electrolysis,
https://wiki.mozilla.org/Electrolysis). One particular reason why it
is relatively hard to do is due to use of the same event loop for both
UI and EAL event processing.
Again, I have not see any such work on WebKit side apart of
Chrome-specific implementation which is not easy to port over to other
/ Alexander Bokovoy
More information about the MeeGo-dev