[Sugar-devel] Hypothetical sugar-0.90 material, draft 1.

[Lucian Branescu]

Folding hulahop into this abstraction layer could possibly make sense.
Let me finish it first, though. Hulahop has a lot of weird code and a
lot of XPCOM magic.

Both pywebkitgtk and hulahop have very similar WebView classes. My
wrapper now offers some extra methods for engine-specific bits and a
few utility functions, but very little is added to the base WebView
classes.

On 10 June 2010 01:11, Bernie Innocenti <bernie at codewiz.org> wrote:
> El Wed, 09-06-2010 a las 13:30 +0100, Lucian Branescu escribió:
>
>> After some debate on what exactly I should be doing, I've decided that
>> it's both prudent and relatively easy to make that abstraction layer
>> after all. Since I last used it, pywebkitgtk's API has grown much
>> closer to hulahop's, so a snippet similar to this one
>> http://wiki.laptop.org/go/Sugar_Code_Snippets#WebView already works
>> for both hulahop and pywebkitgtk.
>
> To simplify our dependencies, couldn't you also fold hulahop into
> WebView, or vice-versa?
>
> As far as I know, Browse is still the only hulahop user on this planet,
> so it's not like we need to keep it around for API compatibility.
>
> --
>   // Bernie Innocenti - http://codewiz.org/
>  \X/  Sugar Labs       - http://sugarlabs.org/
>
>