Eclipse 3.4 just came out. There's a new JavaScript Development Tools plugin (JSDT).
The JavaScript Development Toolkit (JSDT) is a JavaScript development framework for Eclipse based on the Java Development Toolkit (JDT). The JSDT differs from other JavaScript IDEs as it accurately models JavaScript in real-time. This allows smart error detection and correction, flow analysis and content completion that's actually relevant to the user.
Not only is the JSDT more accurate then other JavaScript IDEs but in most instances its much faster too. And since the JSDT's foundation is in the JDT many of the rich editing features of the JDT carry over. The end result is a fast, feature packed JavaScript IDE and framework that's well suited for AJAX and other JavaScript development needs.
Has anyone figured out how to add the Dojo Library to JSDT. I've been googling for a while with little results.
-Arlo
Re:Eclipse 3.4 and the JSDT plugin
I am having the same problem as Arlo trying to use JSDT for Dojo editing. While the regular javascript editing seems fine, the Dojo class inference does not - although announced in the article http://www.ibm.com/developerworks/library/os-eclipse-jsdt/ , which also Arlo is referring to, I think. I would expect, with the correct setup, that e.g. JSDT autocomplete would offer me dojo.require when having typed dojo.r, which is not the case.
I have tried setting up a user lib in the global scope, containing dojo.js and dijit.js, but it didn't help. Documentation is also still poor. Did anybody manage to get autocomplete for the objects and methods available in a js lib in Eclipse JSDT?
-help highly appreciated. thanks.
solution found!
Okay, I've found at least one way how you can activate the dojo class inference: there is a screencast in this bugzilla bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=194047 that shows how it can be done with a JavaScript project and a separate js file. The precise link to the video attachment is https://bugs.eclipse.org/bugs/attachment.cgi?id=109012 (-> screencast.swf packed in a zip archive).
That solution worked for me, although I used a user lib for dojo and in the video the dojo lib was somehow preregistered on the same level as the browser libs. I wonder how that's been done... but for the rest, I think that's an acceptible way to proceed...
Bug reports - sometimes a good way of documenting features when offiicial docs are not out, yet ;-)