Eric from Spket says he's working on a new version supporting Ext 4.x. So far (for ExtJS 2 & 3) Spket was in my opinion the best alternative.

PhpStorm/WebStorm has fantastic support for Ext and apparently it works well with version 4 too, but for some reason I couldn't get used to their strange way of implementing autosave in the IDE; basically your open files are always saved in the background, you can't discard changes except if you restore an old version from history... which is quite strange. I don't like the idea of not being able to control when/what/if I save in my IDE.

Eric from Spket says he's working on a new version supporting Ext 4.x. So far (for ExtJS 2 & 3) Spket was in my opinion the best alternative.

PhpStorm/WebStorm has fantastic support for Ext and apparently it works well with version 4 too, but for some reason I couldn't get used to their strange way of implementing autosave in the IDE; basically your open files are always saved in the background, you can't discard changes except if you restore an old version from history... which is quite strange. I don't like the idea of not being able to control when/what/if I save in my IDE.

If i remember exactly there's also a setting to increase/decrease the time between savings. Honestly, i really like the autosaving feature as i don't have to worry about loosing my code. If you want to revert, there's the awesome local history they have which is something like a mini versioning sistem

Using netbeans here also (for PHP with ZF support). I'm open to try other options as lately I'm doing more and more Extjs less and less PHP. Netbeans JS / ExtJs code completion is awfull remoteSave is great and easy to use.

Gonna try webstorm when 2.0 is release. Their UI is awfull but I can live with it if the rest is better then Netbeans.

Well, tried them.
Crikey, so slow, as are any desktop apps that use Java in my experience; gonna stick with Sublime I think... I like the fact with Sublime a project is not confined to a directory tree (something that's new to me and will be hard to let go of), so can have my source (across multiple repos), and the Ext source all in the same project, and be able to open any of the classes with a few typed chars

I'm pretty convinced that proper, correct Ext auto-completion (or even JavaScript for that matter) is impossible anyway.
It's such a free, unconstrained language, allowing you to extend or hack any object or function that takes your fancy, how on earth can anything actually offer completion for it without actually running the code, and analysing what is there after executing each line?

I'm pretty convinced that proper, correct Ext auto-completion (or even JavaScript for that matter) is impossible anyway.
It's such a free, unconstrained language, allowing you to extend or hack any object or function that takes your fancy, how on earth can anything actually offer completion for it without actually running the code, and analysing what is there after executing each line?

Spket makes extensive use of JSDoc attributes. I think this is a better approach for JavaScript than trying to do analysis on the code itself, especially if you're trying to support multiple frameworks each with their own inheritance mechanism. I can't speak for the other editors, though I would assume the ones with good code completion look at the JSDoc too.