Hi,
I'm really happy you liked the object inspector because it represents my
main contribution to the project. My comments to your suggestions are below.
El 26/03/12 15:23, vbgunz escribió:
I found Spyder today and am super excited about it for 2 reasons. The
first is "object inspector". The second is "online help". It's awesome
to add the fun back to programming with unknown or little known code.
After using Spyder for a bit and feeling great about it, I noticed
there are some things I wish Spyder could do quicker. This isn't
perhaps the best place to ask for features but I appreciate your time.
For one, the "object inspector" I hope provides enough ground work to
add a feature. Currently there is "Source: Console" and "Source:
Editor". Is it possible to add a "Source: Cursor" and how it works is,
it follows the cursor and is able to immediately, without any
interaction, etc, provide a helpful overview on objects currently
selected, highlighted or in which the cursor is over/before, (bonus
would be if it could update while in auto-completion and not wait for
an opening parenthesis)? In other words, it would be amazing to get
immediate inline help as you code and-use-the consoles without having
to interact in anyway with the "object inspector".
We have the keyboard shortcut CTRL + I that let let you send any object
on the editor or the console to the object inspector. Unfortunately it's
not well known but it works like this: if you write 'range' (for
example) and hit CTRL + I you will immediately get its docstring on the
object inspector. This also works if you put the cursor at the end of
the any object you want to inspect. If you have any doubts about how it
works, please let me know.
Second, I wish the "object inspector" had more links to "online help".
A good example, is "object inspector" knows I am using the os package.
When I call os.path.abspath, I get immediate help on the member *but*
what I am usually after is another member of *os.path*. It would be
super awesome at this point to simply have a link to os.path and os
from the "object inspector". What an excellent way to re/familiarize
oneself with well documented but unknown or foggy code.
I know exactly what you mean and there is definitely room for
improvement here. The idea is to show online help for standard lib
objects because their docstrings are not that good. I have some ideas on
how to do it, it's not going to be easy but I maybe I could have it
ready for 2.2.
I believe learning is an absolute and critical personal attribute to
writing better code. I just wish the learning part didn't take me out
of the fun or heat-of-the-moment coding. Spyder is very promising with
this and I love it for that very reason alone. I just hope it get's
better, more automatic, in sight but out of the way so I can code
right the very time every time. Damn, I hope someone is listening.
I totally agree with you and that's why I'm improving the object
inspector the best that I can. I have lots of ideas that I plan to
implement on the next two or three releases.
Cheers,
Carlos
Thanks
--
You received this message because you are subscribed to the Google
Groups "spyder" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/spyderlib/-/khR3Ipetj9kJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/spyderlib?hl=en.
--
You received this message because you are subscribed to the Google Groups
"spyder" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/spyderlib?hl=en.
