Please note that autocompletion is not the only reason to have static typing support or type hinting. When project size and number of developers grow, static typing becomes more and more preferable as it decreases the cognitive load needed to work with the codebase, reducing human errors.
3. JsDoc directive scanning
JsDoc class and namespace hints are especially needed when you are using something like RequireJS for defining your modules. This is because naive source code scanners have very hard time to determine module exports and classes from this kind of source code and as far as I know, no IDE supports RequreJS natively yet.
Note that personally I prefer superior JsDuck over JsDoc for actual HTML documentation generation.
4. TypeScript definitions and language
The less invasive approach is to provide type information in externally typed interface files (example .ts for jQuery).
Sublime Text 2 has a plugin to support TypeScript based autocompletions.
5. SublimeCodeIntel plug-in and OpenKomodo CodeIntel
OpenKomodo is a software repository for the open source parts of ActiveState’s Komodo Edit editor. It has a subsystem called CodeIntel for autocompletion and source code symbol scanning.
What makes CodeIntel interesting from the perspective of Sublime Text 2 is that CodeIntel is 1) open source 2) written in Python, making it easy to integrate with the Python based plug-in system of Sublime Text 2. Thus, there exist SublimeCodeIntel plug-in.
6. Sublime Text 2 and CTags
Exuberant CTags is a generic “tag” type information extractor backend for various programming languages. As the name implies, it was originally created to autocomplete C source code. Sublime Text 2 has support for CTags with a plug-in which is called CTags.
Subscribe to RSS feed Follow me on Twitter
Follow me on Facebook Follow me Google+