[sugar] [pyxpcom] PyXPCOM viability and OLPC

[edward baafi]

> We are locked into gtk widgets

Is this because it's been decided that sugar shouldn't have multiple
widget toolkits?
Is this the case even if mozilla can be built with a gtk/cairo backend?

Also, if the current browser activity is written with pygtkmozembed,
what is the meaning of: "Applications can also use xulrunner which
includes Javascript capability." from
http://wiki.laptop.org/go/Web_Browser

> 1 Write an embedding widget from scratch in Pyxpcom. It has been done
> for JavaXPCOM I think, so it's possible in theory.

Is this what you're talking about:
http://www.mozilla.org/projects/blackwood/webclient/ ?

> 2 Use gtkmozembed (written in C) but give access to the gtkmozembed
> nsIWebBrowser as a PyXPCOM object so that we can access the DOM document
> from python. It should be possible but I never investigated it much.

You said earlier that gtkmozembed exposes nsiWebBrowser.. Is the
problem that this is not exposed to the python gtkmozembed wrapper?
If that's the case, why not improve the wrapper and expose
nsiWebBrowser as a regular python, rather than pyxpcom object?