I'm doing this GSoC project for Sugar Labs http://wiki.sugarlabs.org/go/Summer_of_Code/2010/AbstractBrowser
At the moment, Browse (the Sugar default browser) uses hulahop (http://git.sugarlabs.org/projects/hulahop). There have been many concerns about hulahop and pyxpcom maintainability. XPCOM itself has been rumoured to be deprecated for gecko 2. Also, xulrunner is becoming problematic in distros. As a result, there have been efforts to improve the situation. There is a partial port of Browse to pywebkitgtk, but the didn't get too far because of lack of development time. Also, there are some concerns that WebKit developers do not cooperate to merge gobject bindings. At the moment, pywebkigtk developers maintain a set of patches for that. I need to decide what to do: 1) go ahead with the abstraction layer 2) fully port Browse to pywebkitgtk 3) fix hulahop issues In order to decide I need to know more about the future of XPCOM, xulrunner and general gecko/xulrunner embeddability. _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
