I have the first version of the CodeIntel2 ported from Komodo to Sublime Text 2 (Mac OS X only at the moment... maybe someone's willing to compile the needed modules for other platforms, let me know)

You need only to untar the file into Packages and that's it... as you start writing, you'll get "code intellisense" suggestions. I'l still working on finding out how to do the "Jump to symbol declaration"... and Sublime needs more flexible ways to display menus (with icons perhaps and different fonts)... as well as advanced tooltips, so that I can show function calls with parameters information and documentation.

The above links are now obsolete, get the latest from my github. Many improvements have been worked out (including the mouse click for jumping to symbol definitions) and it's now everything is working much much better. I'd say it's pretty much ready now

Full code intellisense, function tips and go to definitions in Sublime!

@paulstraw, Please pull the new version from github. This one logs errors and stuff to ~/.codeintel/codeintel.log. Please try it and post the logs somewhere if you feel you've found a problem. Thank you for your feedback.

The problem is that 'someFunction' exists though (I just changed the function name in that snippet).

After playing with it a bit more, it seems the problem may be that CodeIntel is having trouble/doesn't support traversing directories. In the attached example, I can't get usingObject.js to see things from someObject (inside someObject.js), but if I move it out of ./subfolder (and let the index rebuild), it works fine. The same problem seems to happen when someObject is inside ./subfolder and usingObject is outside.

@paulstraw, I have made some changes that fix some other edge problems so please pull the most recent code... But here, the problem is really not a problem, it's just a matter of misconfiguration... with javascript you just use files, and each file needs to be located somehow. Since it doesn't have an "import" command, it's impossible to know where the files are located by just guessing (files could be anywhere in your hard drive). So you *must* tell where all the directories containing javascript files are. You do this by creating a '.codeintel' folder and a configuration file called 'config' in either your home directory (~/.codeintel/config) or your project root directory (codeIntelTest/.codeintel/config) and adding the paths there:

Basically what that says is that for language "JavaScript", you want some additional paths to be added, that contain more javascript files that will be used, by setting "javascriptExtraPaths". It adds the project folder itself to the extra paths, as wel as some extra "subfolder" directories.

In this particular case, the file "config" is not really needed, as CodeIntel will search inside the project's root folder for *JavaScript* files in up to 10 levels... however, you *must* still flag the root of your project by adding an empty folder named ".codeintel". That alone should solve the problems you were having. For your example, simply create the directory called "codeIntelTest/.codeintel", and then it'll work as expected.