orange / docs / extend-widgets / rst / graphing.rst

Full commit

Graphing and Orange Widgets

The most fun widgets are of course those that include graphics. For this we either use Qt's :class:`QGraphicsScene` (widgets for tree and heat map visualizations, for instance, use this), or use a special control for drawing data plots as provided in Qwt library and :mod:`PyQwt` interface. Here we look at the latter, and extend our learning curve widget with a control that plots the curve.


Let us construct a widget with a following appearance:


There are two new elements from our previous incarnation of a learning curve widget: a control with a list of classifiers, and a graph with a plot of learning curves. From a list of classifiers we can select those to be displayed in the plot.

The widget still provides learning curve table, but this is now offered in a tabbed pane together with a graph. The code for definition of the tabbed pane, and initialization of the graph is

:class:`~OWGraph.OWGrap` is a convenience subclass of :class:`QwtPlot` and is imported from OWGraph module. For the graph, we use :func:`setAxisAutoScale` to request that the axis are automatically set in regard to the data that is plotted in the graph. We plot the graph in using the following code

This is simple. We store the curve returned from :obj:`addCurve` with a learner.


This is a very bad design. Please do not store widget specific data in the input objects.

In this way, each learner also stores the current scores, which is a list of numbers to be plotted in Qwt graph. The details on how the plot is set are dealt with in :obj:`setGraphStyle` function:

Notice that the color of the plot line that is specific to the learner is stored in its attribute :obj:`color` (:obj:`learner.color`). Who sets it and how? This we discuss in the following subsection.

Colors in Orange Widgets

Uniform assignment of colors across different widget is an important issue. When we plot the same data in different widgets, we expect that the color we used in a consistent way; for instance data instances of one class should be plotted in scatter plot and parallel axis plot using the same color. Developers are thus advised to use :obj:`ColorPaletteHSV`, which can be imported from :mod:`OWWidget` module. :obj:`ColorPaletteHSV` takes an integer as an parameter, and returns a list of corresponding number of colors. In our learning curve widget, we use it within a function that sets the list box with learners

The code above sets the items of the list box, where each item includes a learner and a small box in learner's color, which is in this widget also used as a sort of a legend for the graph. This box is returned by :obj:`ColorPixmap` function defined in :obj:``. Else, the classifier's list box control is defined in the initialization of the widget using

Now, what is this :obj:`blockSelectionChanges`? Any time user makes a selection change in list box of classifiers, we want to invoke the procedure called :func:`learnerSelectionChanged`. But we want to perform actions there when changes in the list box are invoked from clicking by a user, and not by changing list box items from a program. This is why, every time we want :func:`learnerSelectionChanged` not to perform its function, we set :obj:`self.blockSelectionChanges` to 1.

In our widget, :func:`learnerSelectionChanged` figures out if any curve should be removed from the graph (the user has just deselected the corresponding item in the list box) or added to the graph (the user just selected a learner)

The complete code of this widget is available :download:`here <>`. This is almost like a typical widget that is include in a standard Orange distribution, with a typical size just under 300 lines. Just some final cosmetics is needed to make this widget a standard one, including setting some graph properties (like line and point sizes, grid line control, etc.) and saving the graph to an output file.