I am trying a bit to figure this stuff out (xulrunner + python xpcom or whatever it is called). Most of the time my web searches are bringing up pyxpcomet or similiar things. Is py xpcom what is being used by the hulahop/xulrunner setup for pyjamas desktop?
Also, some of you may have seen the message by B. Holley """ don't know much about pyxpcom, but I imagine it being pretty analogous to XPConnect (our JS<->XPCOM bridge). XPConnect is probably the most notorious module in Gecko - it's complicated, scary, and easy to get wrong. We already sink a ton of engineering resources into it, and wouldn't if it weren't so fundamental to our entire architecture. More importantly, for a number of reasons the DOM is becoming more intimately tied to JS: we're removing the abstraction layer that sorta-kinda makes the DOM language-agnostic (it's too slow), and we're writing new custom DOM bindings. So if it isn't true already, pyxpcom won't be able to script the DOM anymore, which makes it significantly less useful. Reversing this course (and maintaining a separate set of python DOM bindings) is pretty much out of the question: it incurs a performance penalty for the Web that we don't want to pay, and it would take months and months of engineering """ My questions are whether or not the right ideas are being thought about. I don't know which parts of the code to dive into to check what the status is in the current development Mozilla code or if we can some how use the B2G project.
