I just wanted to post back for anyone who comes across this thread.
Considering the fact that I've now spent close to an hour just trying
to find JSDT documentation, and given the fact that this post has been
up for several days with no response, I think it is safe to say that
JSDT has no documentation whatsoever (beyond the extreme basics
provided on the Eclipse wiki).
But, there is hope for JS development in Eclipse. First, there's
Fireclipse, which is extremely cool in that it attempts to build on
the work of Firebug (as opposed to JSDT, which tries to "reinvent the
wheel" by basically re-building Firebug inside Eclipse).
Unfortunately however, Fireclipse is even less "primetime ready" than
JSDT: the Eclipse part of it doesn't even have a binarty (it still has
to be compiled from source) :-(
But far more importantly (for now at least) there is JSEclipse (from
Adobe). When I was at the Eclipse developers day, I got to meet the
lead developer for JSEclipse, and the guy made the very bold claim
that (paraphrasing; my memory sucks) "JSEclipse is so primitive, and
it can't do half of what JSDT can". That guy is living in a fantasy
world, and clearly has never tried using the two side-by-side; if
anything, the exact opposite is true.
Here's the key difference that made be abandon JSDT in favor of
Eclipse: JSDT will label any function that isn't defined in the
current file as an "error" (red squiggly underline). In other words,
if you use multiple JS files that reference each other, they will all
appear to be full of errors in JSDT. To get rid of this, you're
somehow supposed to write a ton of JSDoc (to specify variable types,
method signatures, and other things that have no place in JS), then
create a JSDT library. But there's no documentation anywhere on how
to do this.
In contrast, JSEclipse simply doesn't mark these functions as errors;
revolutionary! ;-)
(For the record, I do think JSEclipse might have a similar library
mechanism, and it may be just as un-documented; however, never having
need to use it, I wouldn't know.)
You can get JSEclipse by adding this update site in Eclipse:
http://download.macromedia.com/pub/labs/jseclipse/autoinstall/
I've also heard many positive things about an extensions called (I
think) Aptana, but I haven't played with it (or if I did, it was a
long time ago and it wasn't very impressive back then), so I can't
really speak to it.
Jeremy