[Sugar-devel] Browse and the move to WebKit
Luke Kenneth Casson Leighton
luke.leighton at gmail.com
Thu Feb 16 23:31:20 EST 2012
ok, for a given definition of "success" :)
i had to comment out the js_push_context and js_pop_context
(could not be arsed to deal with those) - you might find that
you have to put in some #includes for spidermonkey, and if you
ask nicely on this bugreport you may get an answer:
please can i advise you to get onto that bugreport (728055) and
say thank you to josh matthews for kindly pointing out the existence
other changes i made include:
* removing calls to set up NS_XPCOM_COMPONENT_REGISTRY
* changing #include and reference to nsIDOMWindow2 to just nsIDOMWindow
other than that, it works! amazing. and this is with the standard
debian packaging for xulrunner-9.0-dev out of debian/testing as of
yesterday. yes, that _includes_ python-xpcom (aka pyxpcom).
can i strongly STRONGLY recommend that you cease the use of webkit and
return to using hulahop?
you are entirely free to completely ignore this advice, and to see how
far it gets you to be using webkit with gobject introspection.
actually, in some ways it would be incredibly useful an exercise because
you will then have a clear idea of the serious and fundamental flaws that
are inherent in webkit's gobject bindings. i will be more than happy to
help accelerate the OLPC projects' understanding of the situation, as long
as you agree to release a public and detailed technical description of the
issues encountered onto the webkit-dev mailing list.
preferably without mentioning where you got the advice from, because the
webkit developers will treat you like shit if you even mention my name.
More information about the Sugar-devel