Bug 88902 - Feature Request: More intelligent JS code outlining
Summary: Feature Request: More intelligent JS code outlining
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Webtools.WST.Javascript (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: David Williams CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-03-23 13:42 EST by Chris Tembreull CLA
Modified: 2010-03-03 11:35 EST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Tembreull CLA 2005-03-23 13:42:00 EST
As it stands, the Javascript editor (while useful) cannot properly outline
OO-style javascript, e.g.:

function foo(bar)
{
    this.baz = bar;
}

foo.prototype.buz(bletch)
{
    alert(this.baz + ": " + bletch);
}

The current JS outliner doesn't see much - it recognizes foo as a global
function, but does not show any of the arguments, members, or methods added to
that function's prototype or instance.

The Sourceforge JS editor (https://sourceforge.net/projects/jseditor/) actually
has a fairly good outlining system which includes some (not all) of this desired
functionality, but it would be really excellent to see this kind of thing make
it into the WTE.
Comment 1 Lars Juel Jensen CLA 2005-11-07 05:16:38 EST
I agree with you. This is something that I am very in need of since
some projects that I work on has large amounts of javascript OO code.
This will certainly speed-up development, and give a better understanding
of the code.

- Lars
Comment 2 Nitin Dahyabhai CLA 2007-09-13 04:09:44 EDT
This is a great idea, but we don't have people to work on this just now.  We would accept high quality patches, though (although you might understandably be more interested in contributing to JSDT).
Comment 3 David Williams CLA 2007-12-17 01:59:01 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.