Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 100511

Summary:	JavaScript refactoring and better code complete
Product:	z_Archived	Reporter:	Rob Sanheim <rsanheim>
Component:	Webtools.WST.Javascript	Assignee:	David Williams <david_williams>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	apeller, asqueella, levik, thatnitind
Version:	unspecified	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Rob Sanheim

2005-06-17 01:09:09 EDT

JavaScript is becoming an increasingly important part of any web developers
toolkit.  Eclipse should extend its refactoring intelligence from Java to
JavaScript and also allow code complete for all parameters, functions, etc... 
IntelliJ Idea 5.0 is going to be very impressive in this regard (see:
http://www.jetbrains.com/idea/features/newfeatures.html#js ).

Comment 1 Lev Epshteyn

2005-08-12 11:42:34 EDT

I suggest you throw your support to Bug #99633 - no meaningful refactoring can
be done until the javascript being worked on is being interpreted in some sort
of an embedded js engine - this is due to the fact that unlike Java, a lot of
the js classes/methods/functions/types are not known until runtime.

Comment 2 Adam Peller

2005-09-07 21:04:03 EDT

Similarly, code completion is very difficult (or not very useful) since there
isn't much typing in JavaScript/ECMAScript, at least in the current versions
being used.  All arguments and return types are of unknown types and you'd
likely end up doing a lot of completions on "Object".

Comment 3 Nitin Dahyabhai

2007-09-13 04:01:07 EDT

It's an interesting idea, but we don't have people to work on this just now.  We would accept high quality patches, though.

Comment 4 David Williams

2007-12-17 01:59:14 EST

I'm doing a mass resolve of all open bugs in the wst.javascript component. 
Resolving to "won't fix". 

The reason is that the old wst.javascript component is being removed this release, and replaced by the wst.jsdt component. 

So ... if any owners of these wst.javascript bugs see the same problem in the wst.jsdt code, then please open a new bug on that component. 

Apologies we can't check each ourselves, but there's just too many (and too few people) so we'll need community help. Just glancing, I know for sure many will no longer be bugs but some may still be legitimate requests even in the new JSDT code.