Replace references to pygtk by pygobject in docs.

anntzer · anntzer · commit 9d4616b58b74 · 2021-02-19T19:24:46.000+01:00
Also reorder mentioned backends by fallback order (which is effectively
our preference order), except that the OS-specific macos backend goes
last.

Capitalization follows the docs of each project.
diff --git a/examples/user_interfaces/README.txt b/examples/user_interfaces/README.txt
@@ -5,7 +5,7 @@ Embedding Matplotlib in graphical user interfaces
 
 You can embed Matplotlib directly into a user interface application by
 following the embedding_in_SOMEGUI.py examples here. Currently
-matplotlib supports wxpython, pygtk, tkinter and pyqt4/5.
+Matplotlib supports PyQt/PySide, PyGObject, Tkinter, and wxPython.
 
 When embedding Matplotlib in a GUI, you must use the Matplotlib API
 directly rather than the pylab/pyplot proceedural interface, so take a
diff --git a/tutorials/introductory/sample_plots.py b/tutorials/introductory/sample_plots.py
@@ -385,7 +385,7 @@
 EEG GUI
 =======
 
-You can embed Matplotlib into pygtk, wx, Tk, or Qt applications.
+You can embed Matplotlib into Qt, GTK, Tk, or wxWidgets applications.
 Here is a screenshot of an EEG viewer called `pbrain
 <https://github.com/nipy/pbrain>`__.
 
diff --git a/tutorials/introductory/usage.py b/tutorials/introductory/usage.py
@@ -271,7 +271,7 @@ def my_plotter(ax, data1, data2, param_dict):
 # plotting windows pop up when they type commands.  Some people run
 # `Jupyter <https://jupyter.org>`_ notebooks and draw inline plots for
 # quick data analysis. Others embed Matplotlib into graphical user
-# interfaces like wxpython or pygtk to build rich applications.  Some
+# interfaces like PyQt or PyGObject to build rich applications.  Some
 # people use Matplotlib in batch scripts to generate postscript images
 # from numerical simulations, and still others run web application
 # servers to dynamically serve up graphs.
@@ -281,8 +281,8 @@ def my_plotter(ax, data1, data2, param_dict):
 # "frontend" is the user facing code, i.e., the plotting code, whereas the
 # "backend" does all the hard work behind-the-scenes to make the figure.
 # There are two types of backends: user interface backends (for use in
-# pygtk, wxpython, tkinter, qt4, qt5, or macosx; also referred to as
-# "interactive backends") and hardcopy backends to make image files
+# PyQt/PySide, PyGObject, Tkinter, wxPython, or macOS/Cocoa); also referred to
+# as "interactive backends") and hardcopy backends to make image files
 # (PNG, SVG, PDF, PS; also referred to as "non-interactive backends").
 #
 # Selecting a backend
