Talk 2014-10-21: JSDT in Nodeclipse

[paulvi]

continued from #173

@nodeleaf said

My point was: I don't see how JSDT could be used instead of Nodeclipse's

not instead bu together

• when you are using Nodeclipse IDE. If it was installed as a 'stand alone' plugin then this is not Nodeclipse but JSDT issue.

Nodeclipse has JSDT as dependency. I don't understand the last sentence.

Now about ES3 in JSDT: this is old story I re-instantiated above to expose one serious limit of JSDT among many others. As far as I understand it, ES5 support in JSDT 3.6 was deferred therefore I am afraid there is not much to collaborate about this topic

Bug 223131 - [language support] Add ecmascript4 /JavaScript 2 compiler compliance level

— beside getting rid of JSDT in Nodeclipse but this is hardly an option don't you think?

there is no goal to get rid, because we have been looking for better tools.
Currently we use JSDT for Editor, it also has good JSDoc support (see angelozerr/tern.java#158)

Nodeclipse originally had no JSDT dependency, and you still can find TextEditor-based Editor as optional. But as you would see it fails behind JSDT-based Editor. Just because there is so much issues to take care of.

[paulvi]

closing as old