File browser right click inconsistencies (IEP 3.2b)

[GoogleCodeExporter]

1. Displays docstrings for files but not for functions, even though both are 
listed.
2. As a result, does not display docstrings for main() functions.
3. Problematic display of multi-line docstrings: Sometime does not show beyond 
a certain word limit (seems like a word limit, rather than a line limit), but 
will still show comments in the following lines.
4. Does not show a right-click menu for files, unless dragged (clicked and held 
while moved).

I assume the docstring pop-up was supposed to be time-based and the right-click 
menu click-based.

Original issue reported on code.google.com by zaha...@gmail.com on 9 Mar 2013 at 3:51

[GoogleCodeExporter]

> 1. Displays docstrings for files but not for functions, even though both are 
listed.

The idea of the file browser is to get a quick high level peek into the module. 
Docstring and toplevel functions/classes. To see docstrings of the latter, you 
should just double-click the item to open the module at the right location...

Nevertheless, I can see how the current behavior might make the user *expect* 
to be able to get the docstring of a function. 

I removed that clicking on a Python module showed the docstring as a tooltip. 
Instead, expanding a module item will give the first line of the docstring as 
an item, and clicking on *that* item will yield the full docstring:
https://code.google.com/p/iep/source/detail?r=7f7b1a2da979ba64dbf99406a04071cbd9
fc36e9

> 3. Problematic display of multi-line docstrings: ...
Docstrings are now only line-limited (by 16 lines)

> but will still show comments in the following lines.
Can you be more precise?

> 4. Does not show a right-click menu for files, unless dragged (clicked and 
held while moved).

This would be a bug. (which I cannot reproduce). Now that the context menu and 
tooltip dont get into each-others way, perhaps it is now fixed?

Original comment by almar.klein@gmail.com on 10 Mar 2013 at 9:51

[GoogleCodeExporter]

Original comment by almar.klein@gmail.com on 10 Mar 2013 at 9:51

• Added labels: Milestone-Release3.2

[GoogleCodeExporter]

1. Interesting. I'm curious to see how that will work.
3. Examples:

"""One-year debt payment calculator using bisection search. Receives the 
following variables:
balance=(non-negative number)
annualInterestRate=(decimal)"""
# Python 2.7.3
This one is displayed up "non-negative number)" and is then cut.

"""Composite interest rate calculator"""
#Python 2.7.3
#balance=4842
#annualInterestRate=0.2
#monthlyPaymentRate=0.04
This one is displayed in its entirety + an ellipsis.

4. Might just be, yes - will have to test later. On my IEP it's pretty 
consisten, and interestingly enough - the right click is registered upon 
release, so it's the end-location of the dragging motion that determines for 
which item the menu opens, not the start location.

Original comment by zaha...@gmail.com on 11 Mar 2013 at 12:03

[GoogleCodeExporter]

I fixed the erroneous docstring. At least the second example. I cannot see what 
went wrong with the first. PLease let me know if the first example still fails.

Original comment by almar.klein@gmail.com on 11 Mar 2013 at 1:01

• Changed state: Started

[GoogleCodeExporter]

Both examples now behave as expected.

Right-click now behaves as expected on both filed and folders.

Tooltip now appears only on left-click on docstrings.

Several suggestions:
1. Tooltips should appear on hover (after 50-500ms), like tooltips usually do.
2. Docstrings should be displayed so, instead of inline.
3. And should display for functions and classes as well.
Rational: The file browser is a list of functional items - that is, items that 
you can actually do something with. Any additional information (such as 
docstrings) should be available to the user in a manner that both complements 
the list and is transparent to the user; that is - appears around the list, and 
is connected to it, and does not require any special actions by the user. 
Tooltips upon hover fill both of these requirements.

Original comment by zaha...@gmail.com on 21 Mar 2013 at 1:10

[GoogleCodeExporter]

As part of migrating our code repositories from Googlecode
to Bitbucket, all IEP issues are now tracked at 
https://bitbucket.org/iep-project/iep/issues

To view this issue, use this link (with X replaced by the issue number):
https://bitbucket.org/iep-project/iep/issue/X

Issues on Bitbucket can be created by anyone. Commenting on issues requires 
login via Bitbucket, Google, Twitter or Github.

Original comment by almar.klein@gmail.com on 11 Jun 2013 at 2:40

• Changed state: Moved