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

Bug 168984

Summary: javascript editor unhelpful with member functions
Product: z_Archived Reporter: benson margulies <bimargulies>
Component: Webtools.WST.JavascriptAssignee: David Williams <david_williams>
Status: RESOLVED WONTFIX QA Contact: Larry Dunnell <ledunnel>
Severity: enhancement    
Priority: P3 CC: robinpelgrim, thatnitind
Version: unspecifiedKeywords: helpwanted
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description benson margulies CLA 2006-12-23 15:14:24 EST
Build ID: Build id: M20060921-0945

Steps To Reproduce:
The javascript editor and outline view are not informative with the following pattern of object-oriented javascript.


function BTRNMName() {
	this._data = 0;
	this._entityType = 0;
	this._entityUID = 0;
	this._extra = 0;
	this._language = 0;
	this._primary = 0;
	this._script = 0;
	this._transliterations = [];
	this._uid = 0;
}
BTRNMName.prototype.getData = function(){ return this._data; }
BTRNMName.prototype.setData = function(val){ this._data = val; }

More information:
Comment 1 David Williams CLA 2007-01-06 01:09:18 EST
Yes, unfortunately we do not (and never intended to) support OO Javascript. 

It would be great to do so, but unfortunately we have no people to do so and no plans to. I'll count this as an enhancement request instead of a bug per se. 
Comment 2 Robin CLA 2007-02-22 02:30:41 EST
It should support ECMAScript syntax. So it's definitely a bug and not an enhancement.
Comment 3 Nitin Dahyabhai CLA 2007-09-13 04:30:24 EDT
Setting aside the severity debate, we just don't have people to work on this now.  We would accept high quality patches, though.
Comment 4 David Williams CLA 2007-12-17 01:59:19 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.