[Sugar-devel] Did someone say Webkit?

[Lucian Branescu]

There already is a mostly complete pywebkitgtk activity, Surf.

There has been a lot of debate on whether webkit is better than gecko
for our purposes. I also plan to only support what is reasonably easy
to support and let the abstraction layer be leaky.

This way, the new Browse can much more easily be ported to another web
engine if needed. In fact, as the abstraction layer grows more
complete, Browse can be 'ported' to the rest of the abstraction layer
(as opposed to AbstractBrowser+hulahop events which would be the first
step).

On 26 April 2010 03:20, Bernie Innocenti <bernie at codewiz.org> wrote:
> On Sun, 2010-04-25 at 18:07 +0100, Lucian Branescu wrote:
>> My GSoC project involves building an abstraction layer above
>> pywebkitgtk/hulahop (wiki/AbstractBrowser).
>>
>> While the project itself isn't related, this abstraction layer and one
>> of it's lower layers (i.e. pywebkitgtk) would become a dependency of
>> the sugar toolkit.
>
> Very interesting. Would your work make it possible to switch the Browse
> activity from XPCOM to Webkit?
>
> If there were no loss of features, would it be easier for you to switch
> the Browse activty from hulahop to pywebkitgtk without developing an
> abstraction framework for both?
>
> --
>   // Bernie Innocenti - http://codewiz.org/
>  \X/  Sugar Labs       - http://sugarlabs.org/
>
>