-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New tooltip for notebook #1509
New tooltip for notebook #1509
Conversation
@hadmack , I open a PR if you find some bugs.
Thanks, I'm writing this because I feel the need for this often, but I also lack JS background... And all the credit have to go to the dev team which made a great api and easy to modifie code. |
rebased on master and forced pushed. |
some cleaning and example on how to configure. rebased on master. @hadmack, you can execute this as a markdown cell of your nb :
And you'll have the pager on second keypress. |
@Carreau, sorry but this one has a conflict right now, no idea what caused it. Could you rebase it so we can start reviewing it and testing it? Hopefully now that we have the PR queue a bit more controlled, we can move more quickly on yours. |
@fperez rebased and forced push. recap of the changes :
[*] If you are ok with that behaviour, I can write that somewhere in the docs/ notebook example. [edit] for the record, conflicting commit was 0960f3b ~L23 , add of |
rebased and forced push to avoid conflict. |
more feature like -completion based on 2 sources : * introspection in kernel * context of current cell (complete with matching words) * each source has its color in the completer
adding 'use strict' in some place to be more agressive on the delaration of the variables. clean name and details here and there
pylab.l<tab><tab> would be replace by .l because of a bug in common start finding .l on the fifth position of pylab.start.
this structure (IPython.utils.keycodes) add some common keycodes like tab...etc and start modifying codecell.js to use it for better readability
if having problem with Tab Completion try to revese this commit
and modifies some file to use it
Completion source based on context is smarter and use codemirror token mecanisme to propose completions, instead of just plitting text at whitespace and before dots.
temporarly (or maybe not) use less css to produce the css for the tooltip.
don't forget to reenqble keyframe with a more recent less compiler
consecutives tab pressing with tooltip does : - fisrt : show it - second : expand it - third : make it sticky for 10s (typing wont dismiss it) - forth : send the content into the Pager
construct a completer only if the class exist otherwise print view won't load.
rebased and forced push to avoid conflict. |
I have refactored now the Kernel, Notebook and CodeCell work in this PR: #1697. That PR will conflict with this one. I think the best way of handling it is to merge that first, then rebase this on top of it. |
Let's try to merge #1697 first and then rebase/merge 1509 on top of On Fri, May 4, 2012 at 12:28 AM, Bussonnier Matthias
Brian E. Granger |
@Carreau I like this idea. Can you create that combined branch and push it as a branch in the ipython org so both of us can push to it. Once that happens I will pick up the work on it. |
@ellisonbg
I'll open a new PR... |
Closing as it is superseeded by #1711 |
This is an answer to fix #1498 (tooltip keyboard shortcuts (feature request)), that also contain all the code from #1417 (new completer) because it rely on some change made in it.
It introduces tooltip in it's own class, and allows differrent behaviour when you press several time. (see discusion in #1498). Plus some aesthetic change when trying to get a tooltip from the far right of the windows.
If you can test and give feedback on usability/ cross browser css compatibility, i'll focus on tidying/commenting the code later.
Invoking @fawce , to be sure he get the notification.