Recent changes to feature-requests

simple javascript code format

2004-10-29T10:37:50Z

Simple javascript code format would be really useful.
(90% of the javascript editors on the market are not
able to do this)

It would be really easy to achieve:
- if I rename a JavaScript file to *.java, than
Eclipse format it very nice (so there is a function
already :) ).
- you should let the function in the menu (in the
JavaScript 'persepective', "format" menuitem does not
exist.
- call under the hood that function that formats *.java
files.
- voila, another cool feature :)

Ahmed.

more Highlight config

2004-10-29T10:28:33Z

It would be very nice if the configuration for the
highlight would have more opetions.
1. at least for the 4 token categories (that exist in
the config at the moment): Bold, italic, underlined,
striked-out, etc.
2. more token categories: at least: asigned functions
(so that one obsevers when his own defined functions
are typed correctly)

Ahemd.

synchronize outline selection from source

2004-10-29T09:27:21Z

At the moment there's only synchronize from outline 2
source (when the user clicks in the tree, in the sorce
the corresponding item is selected/jumped).

A very simple to implemnet and useful feature would be
"synchronize outline selection from source" :
- in the titlebar of the outline, sould be a toggle
button with with this operation.
- when the button is toggled, moving the caret in the
source, would change the outline selection too.

Ahmed.

autocomplete

2003-12-22T07:12:44Z

I think your javascript editor will become a greater
success, if you include some autocomplete feature.
Mispells is the number one reason why developers run
into basic bugs. also, a debugger. this are just
suggestions.

Tab Size

2003-07-31T06:54:21Z

The tab size is set to 4 and cannot be changed; and
there is no "insert spaces instead of tab character".
Though this doesn´t seem too important, it becomes very
annoying when developing.

Nice tool!!

Project view/JavaScript perspective

2003-06-25T03:40:24Z

The information derived from a single file for the
outline should be available from an entire project
through the workspace.

This should be the primary view of a JavaScript perspective

Breaking down public and private class methods/variables

2003-06-24T01:22:48Z

Greetings!

First off, I just want to say that this is a wickedly
cool plugin. There's always room for improvment, but
I've been using this plugin for ~2 months now and I
love it.

With that out of the way, =)

I've got a suggestion regarding the display of methods
and variables in the 'Outline' view in Eclipse. One of
the things I appreciated w/ the 0.0.2 release was the
addition of displaying public class methods that were
defined as:

function testClass() {

this.testFunc1 = function(){ alert("foo"); }

}

Somthing that would be really really nice to have,
would be for the outline view to be able to tell the
difference between public and private/protected
variables and methods.

For instance, take the following example:

function testClass() {

this.pubArray = [];
var privArray = [];

this.testFunc1 = function(){ alert("foo1"); }

function testFunc2(){ alert("foo2"); }

}

Only the method testFunk1() and the property pubArray
should be accessable from outside an instance of
testClass().

I know that support was just added for this for
prototyped methods and variables declared as
this.myProperty = null; to show up in the outline. This
is really awsome and I commend the hard work that was
put in to get this working! It would just be nice if it
worked the same way as I described in my test case as
well ;)

Cheers!