<br><br><div><span class="gmail_quote">On 6/28/06, <b class="gmail_sendername">Trent Mick</b> <<a href="mailto:trentm@activestate.com">trentm@activestate.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Brett Cannon wrote:<br>> The plan is to allow pure Python code to be embedded into web pages like<br>> JavaScript. ...<br><br>> ...Then again, Mark Hammond has already done a bunch of work for pyXPCOM, so getting Python compiled right into Firefox itself shouldn't be too bad.
<br>><br>> If this really takes off, will probably want both: get into Firefox, but have an extension for pre-existing installations.<br><br>You should really speak with Mark, if you haven't recently. He's gotten<br>
a lot further than just PyXPCOM. My understanding (I might be a bit off<br>on the branches and timing) is that his "DOM_AGNOSTIC" work on the<br>Mozilla code has mostly been checked into the trunk. This work is to do
<br>mostly what you are describing: Python as a client-side scripting<br>language along-side JavaScript.</blockquote><div><br>Handling the Firefox integration is next month, so I will be talking to him. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I can't recall what Mozilla's distribution plans are for this. Certainly<br>it wouldn't be before Firefox 3. Then again, default Firefox builds<br>would like not include Python by default.<br><br>It sounds to me that a restricted-execution/security-model story for
<br>Python would be important here.</blockquote><div><br>Yep. One of the reasons I am dealing with it. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Mark (and me a little bit) has been sketching out creating a "Python for<br>Mozilla/Firefox" extension for installing an embedded Python into an<br>existing Firefox installation on the pyxpcom list:<br><br><a href="http://aspn.activestate.com/ASPN/Mail/Message/pyxpcom/3167613">
http://aspn.activestate.com/ASPN/Mail/Message/pyxpcom/3167613</a><br><br>> The idea is that there be a separate Python interpreter per web browser page instance.<br><br>I think there may be scaling issues there. JavaScript isn't doing that
<br>is it, do you know? As well, that doesn't seem like it would translate<br>well to sharing execution between separate chrome windows in a<br>non-browser XUL/Mozilla-based app.</blockquote><div><br>I don't know how JavaScript is doing it yet. The critical thing for me for this month was trying to come up with a security model.
<br><br>And if you don't think it is going to scale, how do you think it should be done?<br><br>-Brett<br></div></div>