mdee 
| resources: | Home Mailing List Installation Source Code Bugs Screenshots |
|---|
What's New
Other Stuff
- Status - Development
Mozilla Development Environment for Emacs (MDEE)
For the last few weeks I have been hard at work trying to get a working copy of NewsMonster (another Mozilla project I am working on) ready to be used by the masses. This means that all of the issues reported by users are going to need to be resolved which means I need solid Mozilla integration.
The only problem is that I am spoiled by the excellent IDE support within Emacs for Java thanks to the JDEE project . There really isn't a lot of support within Emacs for Mozilla technologies (Javascript, XPCOM, XUL, etc).
To that end the MDEE project has been created to develop integration within Emacs for Mozilla. When complete this will resemble a very advanced Smalltalk Environment and IDE with full debugging support, variable introspection, dynamic source evaluation, and class browsing.
Here is where we are:
- Full and seamless support for running and evaluating javascript from within Emacs.
- XPCOM support including the creating and use of components. (WORKING)
- Ability to use the javascript debugger. (WORKING for introspection)
- Ability to use network IO (There is currently a bug for this in Bugzilla. Help would be appreciated!)
- Ability to set breakpoints from within the editor and have them visible to the user with the new display capabilities available in Emacs 21. We should also potentially add support for lisp breakpoints if this is possible.
- Full semantic bovinator support for javascript files. (We need a bnf file for javascript support. I am REALLY hoping someone can help out here).
- Distribution of javascript-mode.el for users who don't have this available. (WORKING)
- Chrome editing support with completion of chrome:// URLs with transparent update of .jar files in the chrome dir.
- Ability to run standalone within a UNIX console and still function correctly with all the MDEE commands we need. (EASY)
- Full object browser support (and within ECB) of the the current scope and any object properties. (TESTING)
- Full ECB integration (This requires some change to the ECB that I am going to make in the near future)
- XEmacs and OSX support (OSX might be a problem because xpcshell creates a window and doesn't use stdin and stdout. We will need to get this fixed.)
- Full introspection support including the ability to "pretty print" a variable and all its properties. (WORKING)
- Ability to display the scope (WORKING)
- IDL docindex support so that users can resolve (with completion) symbols such as "nsIRequest" and have these map to the file automatically. (WORKING)
- comint mode support for a xpcshell console (WORKING)
- Ability to fully init Mozilla from XPCOM and play with the XUL environment. (I have no idea if this is even possible but it would be cool!)