code-google-com / editra-plugins

Automatically exported from code.google.com/p/editra-plugins
0 stars 0 forks source link

(Enhancement) Instance Variables (self) in Code Browser #201

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What Plugin does this relate to? What version of the Plugin?
Code Browser plugin

What steps will reproduce the problem?
1. Code browser plugin does not show instance variables (eg. self.x)

What is the expected output? What do you see instead?
Only Classes are displayed

What version of Editra are you using? On what operating system?
0.6.89

Please provide any additional information below.
If needed I could contribute to this.  I started to look into this but thought 
I would put a feature request in first before I start.  I was thinking the 
instance members could be shown underneath each function being used so it could 
be traced easier by a user.

Original issue reported on code.google.com by efeldma...@gmail.com on 18 Dec 2011 at 3:23

GoogleCodeExporter commented 9 years ago
I guess I am kind of 40/60 for/against enhancement right now.

I can see it as being nice to have additional information available in the 
browser but also can see it as a hindrance as well due to extra clutter in the 
outline.

Where would the variables be listed under the class or under the scope they are 
created in (i.e __init__)? Where would they link to in the document? Where they 
are first declared? How would you detect that for attributes that are not 
declared in the __init__ method?

However instead listing properties may be more interesting and useful in my 
opinion.

Either way I am not sure about what to think about it at this point in time. 
Having a patch to test it out would help decide one way or another.

Original comment by CodyPrec...@gmail.com on 18 Dec 2011 at 6:18

GoogleCodeExporter commented 9 years ago
Closing as WontFix - instance attributes are not displayed on purpose as to not 
clutter the outline.

For this to be reconsidered the following would need to be provided by an 
interested party:
1) Requirements on where to link the references to (i.e if defined in __init__ 
only, where ever exists, first time found in file, ect...)
2) Sample patch implementing it

Original comment by CodyPrec...@gmail.com on 22 May 2012 at 8:28