Using JSDT #4 : Adding Third Party Library
I’m documenting my experiences using the Eclipse JSDT.
In this post I will add a 3rd party library. I will describe a success (mooTools) and a failure (jQuery).
Update: There is improved information in this post: Adding Third Party Library Redux.
Previously
Adding mooTools Library
MooTools is one JavaScript library I’ve been playing with lately.
First download the uncompressed version (mooTools-1.2.4-core-nc.js) and save it somewhere.
Now in Preferences, add the library. Make sure after adding the library, you also add the mooTools .js file you previously downloaded. It should look like this:
MooTools Content Assist
Now create a Static Web Project.
- Expand the project in Project Explorer and right click on JavaScript Resources and select Properties.
- From this dialog, you can add MooTools.
- Add JavaScript Library – User Library – Next – Select moo Library you already added. Finish.
You should see this in Explorer:
Content Assist
MooTools Problems
Supposedly, if your 3rd party library uses jsDoc, the editor functionality is more robust. MooTools does not seem to document with jsDoc.
jQuery Failure
Dojo? Prototype? YUI?
I’m wondering what experiences others have had adding 3rd party libraries or their own libraries.







[…] Using JSDT #4 : Adding Third Party Library […]
Hi,
I’ve been going through the same steps after installing Helios. I thought I’d give jsdt a try. So far I’ve been using the Spket over Aptana combo and it’s been working fine.
Adding Ext-js gives some result, but certainly not anything usable so far. I can see some of the classes in the JavaScript Resources, but only part of them.
Also content assist is either broken or uncomplete. For example typing “Ext.” gives no assist (whereas Ext is a “singleton” with some functions attached to it). Typing “var foo = new Ext.” does work though, and proposes all the classes under Ext AND under the namespaces it contains. Which would give a lot of entries if the parser got everything (but it didn’t).
So, either I’m doing something wrong, or this is still not usable enough 😦 I was hoping I could drop the aptana+spket combo but apparently not. Spket reads jsb files instead of js, and seems to pull classes without a problem.
Cheers,
J
[…] #4: Adding a 3rd party Library […]
[…] #4: Adding a 3rd party Library […]