I plan to use current hulahop/pywebkitgtk to start out since there's less to figure out. Since it's an abstraction layer, the backends can be switched later.
I need a lot of feedback on what the abstraction layer itself needs to do. Afaik, only Browse and Read use browser engines so far. And then again, there may not be enough time write a leakless enough abstraction to be used by anything other than Browse. On 27 April 2010 08:56, C. Scott Ananian <csc...@laptop.org> wrote: > On Mon, Apr 26, 2010 at 8:38 PM, Bobby Powers <bobbypow...@gmail.com> wrote: >> I wrote surf a while ago, and it was quite an easy port. In fact, the >> demo browser for pywebkitgtk was (at least at one point) based on >> browse. I did most of the work in a day and a half, but ran into >> problems with both webkit's packaging and the feature-completeness of >> pywebkitgtk (the ability to download files, for example), both of >> which seem to be solved now. >> >> There are also gir bindings for webkit (in webkit's trunk), so it >> might be worth investigating their completeness, especially since >> pywebkitgtk seems to be unmaintained, as Sayamindu pointed out. > > I believe we use the GIR bindings for webkit at litl. So you can > probably consider them well supported. > --scott > > -- > ( http://cscott.net/ ) > _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel