##// END OF EJS Templates
create menu bar on OSX with some action...
create menu bar on OSX with some action console_widget: modifie/create some QAction to be able to put it in menu bar -made print_action and export_action public -transform increase/decrease/rest front_size to QAction -create qaction for undo/redo MainWindow Create the menubar with the following structure And link each menu with its action in console Widget File |__Print |__Save as XML |__Select ALL Edit |__Undo |__Redo Font |__Increase font size |__Decresae font size |__Restet Font size Window |__Minimize |__Maximize |__Full Screen Magic |__Reset |__History |__Export History |__Who |__Whos |__Who_ls Help |_Open online Help The 'Magic' Menu, execute %magic after 'exit_keyboard' and pasting '%magic'. The 'Export History' menu prompt the user for a file name and a range before pasting `%save filename range`. This this also fix a bug in toggle full screen where Full Screen -> (try to) Minimizing -> Out Of Full Screen is broken (grey background for all screen), at least on OSX

File last commit:

r1334:049617d6
r5027:3bceb23d
Show More
test_exampleip.txt
30 lines | 816 B | text/plain | TextLexer
=================================
Tests in example form - IPython
=================================
You can write text files with examples that use IPython prompts (as long as you
use the nose ipython doctest plugin), but you can not mix and match prompt
styles in a single file. That is, you either use all ``>>>`` prompts or all
IPython-style prompts. Your test suite *can* have both types, you just need to
put each type of example in a separate. Using IPython prompts, you can paste
directly from your session::
In [5]: s="Hello World"
In [6]: s.upper()
Out[6]: 'HELLO WORLD'
Another example::
In [8]: 1+3
Out[8]: 4
Just like in IPython docstrings, you can use all IPython syntax and features::
In [9]: !echo "hello"
hello
In [10]: a='hi'
In [11]: !echo $a
hi