This post is kind of extension, to the idea described in the previous post, so if you have not seen it yet it’s better check it out. This idea is not only extension to the previous idea but it’s also an extension to a firefox :) Basically it’s a bespin backend implemented on the chrome side as an extension to the mozilla toolkit.
Not sure if you ever wrote some code for firefox or any other xulrunner application, but if you have this experience I’m sure you’ll agree that biggest problem with it is a lack of good tools. _(This doesn’t applies to the Emacs users :)_I think big potential in bespin to change all this, I will try to describe how.
Just imagine to open bespin inside firefox, with a project firefox inside. There you’ll be able to modify any file, which will actually modify the source of firefox, and changes will be available on the fly in the firefox where bespin wll be running :) So does this blows up you’re mind ? Not yet ? Ok then imagine being able to open a page source on view-source in bespin inside firefox instead of the regular source viewer window !! Hmmm still not enough ? Ok then imagine being able to set a breakpoints in the bespin inside firefox to the source of the firefox in order to debug it :D And remember it doesn’t really has to be you’re local firefox it can be even on a different machine on a different platform or planet as long as you have internet connection there :)
Hope I got you exited, as all this will be something I’m going to focus on as soon as JS port will be finished. Well debugging part won’t be as easy as the rest, but hope you are able to smell the future of xulrunner development using bespin!!