I like the free Komodo Edit app from ActiveState. It has it's own XML format for code completion and tips and whatnot, though the most recent Dojo version available only covers the 0.4 API ... I grew tired of using Dojo 1.0 with 0.4 API's popping up as I typed, so I ventured out to see if I could generate a CodeIntel XML (.cix) file for the new API, and it worked.

edit: i had an old version. there is a 0.9 version on the ActiveState community site

I typically don't use it, but now have basic code-completion for the entire dojo, dijit, and dojox API's at my fingertips, as I am coding. It doesn't alleviate the need to know a function name ahead of time, but can definitely be helpful in learning, and if you are at all like me, remembering the type of some expected argument, or some specific return type.

This was a partially selfish act in that I was strictly targeting Komodo editor, as it had a published schema, and seemed simple enough to implement. If you are interested, Komodo is free. If you have the inclination, modify the makeCix.php file to generate [your favorite editor]'s data format, and share it, or assist me in doing so. I'd love to see this kind of code-assistance appear in other editors, too.

In [12021], I checked in the PHP script being used to generate the .cix (XML) file, and thoughtfully request anyone interested in improving the accuracy of the found data should not hesitate to contact me ... it doesn't handle class inheritance very well (yet), and I was kind of wrestling the data to begin with, so getting it to this point was a small feat in itself. Any PHP or XML masters out there, I could definitely use some review.

The initial dojo.cix file generated is ~815k, and is based on the API in trunk (to become 1.1). I considered breaking it into dojo.cix, dijit.cix, and dojox.cix to more fit with the project setup, but opted to maintain only one file for now ... opinions are welcome.

Though the API has not changed (much) since 1.0, I can see a desire to have a 1.0 or 1.0.2-specific version of the .cix ... The inline-docs are the source of this data (for now), so back-releasing a 1.0.x version would probably have less info available, though the API would be "more accurate" ... They would be easy to generate, but might not be worth the effort?

I hope this helps someone, and welcome any/all participation in making it better, more accurate, or more portable.