Show More
@@ -1117,20 +1117,8 b' GUI event loop support' | |||
|
1117 | 1117 | .. versionadded:: 0.11 |
|
1118 | 1118 | The ``%gui`` magic and :mod:`IPython.lib.inputhook`. |
|
1119 | 1119 | |
|
1120 | .. warning:: | |
|
1121 | ||
|
1122 | All GUI support with the ``%gui`` magic, described in this section, applies | |
|
1123 | only to the plain terminal IPython, *not* to the Qt console. The Qt console | |
|
1124 | currently only supports GUI interaction via the ``--pylab`` flag, as | |
|
1125 | explained :ref:`in the matplotlib section <matplotlib_support>`. | |
|
1126 | ||
|
1127 | We intend to correct this limitation as soon as possible, you can track our | |
|
1128 | progress at issue #643_. | |
|
1129 | ||
|
1130 | .. _643: https://github.com/ipython/ipython/issues/643 | |
|
1131 | ||
|
1132 | 1120 | IPython has excellent support for working interactively with Graphical User |
|
1133 | Interface (GUI) toolkits, such as wxPython, PyQt4, PyGTK and Tk. This is | |
|
1121 | Interface (GUI) toolkits, such as wxPython, PyQt4/PySide, PyGTK and Tk. This is | |
|
1134 | 1122 | implemented using Python's builtin ``PyOSInputHook`` hook. This implementation |
|
1135 | 1123 | is extremely robust compared to our previous thread-based version. The |
|
1136 | 1124 | advantages of this are: |
@@ -1147,7 +1135,7 b' For users, enabling GUI event loop integration is simple. You simple use the' | |||
|
1147 | 1135 | %gui [GUINAME] |
|
1148 | 1136 | |
|
1149 | 1137 | With no arguments, ``%gui`` removes all GUI support. Valid ``GUINAME`` |
|
1150 |
arguments are ``wx``, ``qt |
|
|
1138 | arguments are ``wx``, ``qt``, ``gtk`` and ``tk``. | |
|
1151 | 1139 | |
|
1152 | 1140 | Thus, to use wxPython interactively and create a running :class:`wx.App` |
|
1153 | 1141 | object, do:: |
@@ -1164,9 +1152,9 b' Interested developers should see the module docstrings for more information,' | |||
|
1164 | 1152 | but there are a few points that should be mentioned here. |
|
1165 | 1153 | |
|
1166 | 1154 | First, the ``PyOSInputHook`` approach only works in command line settings |
|
1167 |
where readline is activated. |
|
|
1168 | improving the integration of GUI event loops with the standalone kernel used by | |
|
1169 | the Qt console and other frontends (issue 643_). | |
|
1155 | where readline is activated. The integration with various eventloops | |
|
1156 | is handled somewhat differently (and more simply) when using the standalone | |
|
1157 | kernel, as in the qtconsole and notebook. | |
|
1170 | 1158 | |
|
1171 | 1159 | Second, when using the ``PyOSInputHook`` approach, a GUI application should |
|
1172 | 1160 | *not* start its event loop. Instead all of this is handled by the |
General Comments 0
You need to be logged in to leave comments.
Login now