Comments on: open komodo and the code http://trentm.com/blog/archives/2007/09/06/open-komodo-and-the-code/ Thu, 20 Nov 2008 13:24:05 +0000 http://wordpress.org/?v=2.2.2 By: trentm http://trentm.com/blog/archives/2007/09/06/open-komodo-and-the-code/#comment-1804 trentm Tue, 11 Sep 2007 23:55:06 +0000 http://trentm.com/blog/archives/2007/09/06/open-komodo-and-the-code/#comment-1804 axel, Not out of the starting gates (because we want to have this working really quickly), but the plan is (1) To make Komodo a true XUL Runner app. Note that there are a lot of questions about how feasible it will be for XUL Runner apps to run with the generic XUL Runner base that a distro provides. Most current XUL Runner apps that I know about (those that get mentioned on planet.mozilla.org) tend to have their own patches against XUL Runner that haven't yet made it into the core sources to fix issues specific to their app. (2) Get Komodo working with more vanilla Python builds. On Linux, however, a *shared* build of Python is required and getting PyXPCOM to work in a running Mozilla instance is currently very finicky about placement of the relevant files. I don't know if the Linux distros tend to do shared Python builds or if they do static ones. axel,

Not out of the starting gates (because we want to have this working really quickly), but the plan is

(1) To make Komodo a true XUL Runner app. Note that there are a lot of questions about how feasible it will be for XUL Runner apps to run with the generic XUL Runner base that a distro provides. Most current XUL Runner apps that I know about (those that get mentioned on planet.mozilla.org) tend to have their own patches against XUL Runner that haven’t yet made it into the core sources to fix issues specific to their app.

(2) Get Komodo working with more vanilla Python builds. On Linux, however, a shared build of Python is required and getting PyXPCOM to work in a running Mozilla instance is currently very finicky about placement of the relevant files. I don’t know if the Linux distros tend to do shared Python builds or if they do static ones.

]]> By: axel http://trentm.com/blog/archives/2007/09/06/open-komodo-and-the-code/#comment-1803 axel Tue, 11 Sep 2007 23:32:45 +0000 http://trentm.com/blog/archives/2007/09/06/open-komodo-and-the-code/#comment-1803 # Get a slightly tweaked mozilla build (C++, JavaScript, XUL). # Get a slightly tweaked Python build (C). does this mean it won't run with the vanilla spidermonkey/xulrunner/python that most linux distributions ship? Get a slightly tweaked mozilla build (C++, JavaScript, XUL).

Get a slightly tweaked Python build (C).

does this mean it won’t run with the vanilla spidermonkey/xulrunner/python that most linux distributions ship?

]]> By: trentm http://trentm.com/blog/archives/2007/09/06/open-komodo-and-the-code/#comment-1789 trentm Fri, 07 Sep 2007 16:41:52 +0000 http://trentm.com/blog/archives/2007/09/06/open-komodo-and-the-code/#comment-1789 Steve, One of the important first things with Open Komodo will be in getting it all easy to build and dig into for others. We've struggled a lot to get all the Python build + Mozilla + PyXPCOM things working just right on all the platforms. One of the early things I hope we'll be able to do it make that all easier so that other unrelated XULRunner-based apps can follow suit. Agreed that all the building is still way too hard. Regarding debugging: we don't have a great story for debugging really. A long while back Mark Hammond, when he was working on Komodo directly, did have Komodo debugging Komodo, but we haven't pursued that in a while. I look forward to people getting that going again though! :) Python scripting currently is limited to PyXPCOM -- i.e. just for XPCOM components. Mark Hammond's current Mozilla work to make Python a first-class scripting lang in the browser along-side JavaScript (sometimes called pydom or nsdom) -- i.e. <script language="python">...</script> -- is not something we've yet played with. Mainly that is because the pydom work is on trunk (I believe) and Komodo is currently using the Mozilla 1.8 branch. As to security issues with pydom, I'd have to refer to the Mozilla dev docs on that. Steve,

One of the important first things with Open Komodo will be in getting it all easy to build and dig into for others. We’ve struggled a lot to get all the Python build + Mozilla + PyXPCOM things working just right on all the platforms. One of the early things I hope we’ll be able to do it make that all easier so that other unrelated XULRunner-based apps can follow suit.

Agreed that all the building is still way too hard.

Regarding debugging: we don’t have a great story for debugging really. A long while back Mark Hammond, when he was working on Komodo directly, did have Komodo debugging Komodo, but we haven’t pursued that in a while. I look forward to people getting that going again though! :)

Python scripting currently is limited to PyXPCOM — i.e. just for XPCOM components. Mark Hammond’s current Mozilla work to make Python a first-class scripting lang in the browser along-side JavaScript (sometimes called pydom or nsdom) — i.e. — is not something we’ve yet played with. Mainly that is because the pydom work is on trunk (I believe) and Komodo is currently using the Mozilla 1.8 branch. As to security issues with pydom, I’d have to refer to the Mozilla dev docs on that.

]]> By: Steve Lee http://trentm.com/blog/archives/2007/09/06/open-komodo-and-the-code/#comment-1788 Steve Lee Fri, 07 Sep 2007 16:24:30 +0000 http://trentm.com/blog/archives/2007/09/06/open-komodo-and-the-code/#comment-1788 It's great to see this information flowing out already. You make it sound easy but when I tried a while back to get a python enabled build of Mozilla going I hit so many problems with build/runtime python dependencies issues, largely due to using msvc 8 (the only free version). It appears from bugzilla that these issues may be resolved and perhaps I should have tried harder/longer. The other problem I hit was that lack of development tools such as debugger (venkman for python) and dom/css inspector etc. I guess that is sorted with Komodo too? I'm keeping a keen eye on developments as I would be interested in using XUL + SVG + python with DOM scripting and events. If you provide good docs and tools so it's easy to get going and pick up your experience you could have a real winner. The only other concern I have is that Python scripting on SVG/web pages needs to run in a sandbox and I'm not sure how safe rexec etc are in Python (in Martelli's Nutshell book he says there are holes). Do you only use javascript for this? (Oh I'm creating an Assistive technology that is more of a rich client than a web app but want SVG and oter standards web deployable) It’s great to see this information flowing out already. You make it sound easy but when I tried a while back to get a python enabled build of Mozilla going I hit so many problems with build/runtime python dependencies issues, largely due to using msvc 8 (the only free version). It appears from bugzilla that these issues may be resolved and perhaps I should have tried harder/longer. The other problem I hit was that lack of development tools such as debugger (venkman for python) and dom/css inspector etc. I guess that is sorted with Komodo too? I’m keeping a keen eye on developments as I would be interested in using XUL + SVG + python with DOM scripting and events. If you provide good docs and tools so it’s easy to get going and pick up your experience you could have a real winner. The only other concern I have is that Python scripting on SVG/web pages needs to run in a sandbox and I’m not sure how safe rexec etc are in Python (in Martelli’s Nutshell book he says there are holes). Do you only use javascript for this? (Oh I’m creating an Assistive technology that is more of a rich client than a web app but want SVG and oter standards web deployable)

]]>