[JS] Outline View for Script tab

[MeRiZ]

Hi,

would be very nice to have "Outline View" ( tab beside Watch, Stack or Breakpoints ) for JS, so when I select "Script" tab.

In the Outline View should be all functionalities, which I have described in this picture ( in attachment is the same picture ):
http://yfrog.com/f1outlineview1p

What do you think about this enhancement ?

Have a nice day.

[John J Barton]

I think this is a great Firebug extension idea, please let us know if
you have problems in developing it.

jjb

>  outline-view_1.png
> 53KViewDownload
>
>  signature.asc
> < 1KViewDownload

[MeRiZ]

Hi John,

:) It's only idea, I will not implement/develop this feature.

[Lapu]

Hi John,

Does Firebug provide data for building such outline window? Extension
would need info about :
- all varabiables, functions ( nested vars and fn() )
- types of variables ( from jsdoc or other doc text - using js we dont
have variable type )
- private/public fn/var access ( scope info ? )

I know that command line provide function list ( can you breifly tell
how it works ? )

If i can use Firebug module to get functions list build otuline view
wont be difficult.

ak

>  signature.asc
> < 1KWyświetlPobierz

[John J Barton]

On Jul 27, 10:59 am, Lapu <kaniar...@gmail.com> wrote:
> Hi John,
>
> Does Firebug provide data for building such outline window? Extension
> would need info about :
> - all varabiables, functions ( nested vars and fn() )

Yes and no. If the variables and functions exist, yes, else not. So :
function foo()
{
var bar = 1;
debugger;
}
If you run the function foo() and hit the debugger stmt, then bar
exists. Else it does not.

> - types of variables ( from jsdoc or other doc text - using js we dont
> have variable type )

yes, typeof(varible). you will get object, function, etc. Not very
useful.

> - private/public fn/var access ( scope info ? )

Yes, as above, if you are in a scope you can see it all, else not.

>
> I know that command line provide function list ( can you breifly  tell
> how it works ? )

I guess you mean command completion? If you say
document.
then firebug evaluates "document" and lists the properties.

>
> If i can use Firebug module to get functions list build otuline view
> wont be difficult.

I think one can list the functions per source file, but objects per
source file will require Firefox features that have recent been
removed.

jjb

[Lapu]

Thank you for reply

On 27 Lip, 20:30, John J Barton <johnjbar...@johnjbarton.com> wrote:
> On Jul 27, 10:59 am, Lapu <kaniar...@gmail.com> wrote:
>
> > Hi John,
> > Does Firebug provide data for building such outline window? Extension
> > would need info about :
> > - all varabiables, functions ( nested vars and fn() )
> Yes and no. If the variables and functions exist, yes, else not. So :
> function foo()
> {
>   var bar = 1;
>   debugger;}
> If you run the function foo() and hit the debugger stmt, then bar
> exists. Else it does not.

Ok mayby not all variables but only config vars that are used in
objects and fn( if we use it to create new object instances )
and public/private functions.

>
> > - types of variables ( from jsdoc or other doc text - using js we dont
> > have variable type )
>
> yes, typeof(varible). you will get object, function, etc. Not very
> useful.

I was rather thinking about fn and method params types
( number,string,object )

> > - private/public fn/var access ( scope info ? )
>
> Yes, as above, if you are in a scope you can see it all, else not.

Dynamiclly created vars and fn should be seen in outline.

> > I know that command line provide function list ( can you breifly  tell
> > how it works ? )
>
> I guess you mean command completion? If you say
> document.
> then firebug evaluates "document" and lists the properties.

So to have access to all public fn,classes and vars FB evaluates
window object?

>
> > If i can use Firebug module to get functions list build otuline view
> > wont be difficult.
>
> I think one can list the functions per source file, but objects per
> source file will require Firefox features that have recent been
> removed.
>
> jjb
>

Good solution imho would be to build outline based on jsdoc.... but
not everyone used to document thier code.
Alternatively we can use some token based source code parser to get
all data we need ;)

ak