summaryrefslogtreecommitdiffstats
path: root/doc/src/examples-barmodelmapper.qdoc
diff options
context:
space:
mode:
authorTitta Heikkala <titta.heikkala@digia.com>2014-07-01 07:10:00 +0300
committerTitta Heikkala <titta.heikkala@theqtcompany.com>2014-10-14 13:04:52 +0300
commitc544258484ff4fd5d2b88402fbaa5d154b89a3a2 (patch)
tree7659625abb566dec55d3783ed820b928542d9b2b /doc/src/examples-barmodelmapper.qdoc
parent76339f714f088645e911cee65bdb66055fe029aa (diff)
Qt Charts project file structure change
Charts repository structure is changed to follow the structure of a Qt Add-On module. The task includes following changes: - All macros and definitions named 'commercial' have been renamed. - Compile errors related to QString and qSort usage have been fixed. - Old demos are moved under examples. The QML examples now support only Qt Quick 2.0, the support for Qt Quick 1 is removed. - The QML examples with multiple views are updated so that they are usable also with touch devices. - Unnecessary version checks are removed from examples. - The build stamp has been removed as it was only meant for Charts development purposes and it's no longer needed. Also development build related debug prints are removed as __DATE__ can't be used for all OS thus it doesn't make much sense. - Documentation structure has been updated based on the new module structure. The raw HTML files have been removed. Demos are combined to examples. - Unnecessary .qdocinc files are no longer needed. The content is moved to the corresponding .cpp files. - The Charts widget designer plugin is updated according to the module change. - The test cases updated according to the project structure change. Tests are added also for version 2.0. - cmake modules generation is not needed with Qt 5.4 and Qt Charts so it's disabled. - The new module name and version are updated to the plugin.qmltypes file. Task-number: QTRD-2844, QTRD-3217, QTRD-3218, QTRD-3277, QTRD-3228, QTRD-2526, QTRD-3233, QTRD-3222 Change-Id: Ib7fb26057cde710ffaf6bc780c8bf52a16f45160 Reviewed-by: Miikka Heikkinen <miikka.heikkinen@theqtcompany.com>
Diffstat (limited to 'doc/src/examples-barmodelmapper.qdoc')
-rw-r--r--doc/src/examples-barmodelmapper.qdoc57
1 files changed, 0 insertions, 57 deletions
diff --git a/doc/src/examples-barmodelmapper.qdoc b/doc/src/examples-barmodelmapper.qdoc
deleted file mode 100644
index 81c109df..00000000
--- a/doc/src/examples-barmodelmapper.qdoc
+++ /dev/null
@@ -1,57 +0,0 @@
-/*!
- \example examples/barmodelmapper
- \title BarModelMapper example
- \subtitle
-
- This example shows how to use QAbstractItemModel derived model as the data for the bar series.
-
- \image examples_barmodelmapper.png
-
- Let's start by creating an instance of CustomTableModel class.
- The CustomTableModel class is derived from QAbstractTableModel, and it was created for the purpose of this example.
- The constructor of this class populates the model's internal data store with the data required for our chart example.
-
- \snippet ../examples/barmodelmapper/tablewidget.cpp 1
-
- We now have a model with data that we would like to display both on the chart and in a QTableView.
- First, we create QTableView and tell it to use the model as a data source. To have the data presented nicely, the minimum width of the table view is set and its headers resize mode changed to stretch.
-
- \snippet ../examples/barmodelmapper/tablewidget.cpp 2
-
- Now we need a QChart instance to display the same data on the chart.
- We also enable animations. It makes it easier to see how a modification to the model's data affects the chart.
-
- \snippet ../examples/barmodelmapper/tablewidget.cpp 3
-
- The first line of the code below creates new bar series. Variables firstRow and rowCount are used to define a custom model mapping.
- Custom mapping allows to take only part of the data from the model. In this case data from 5 rows starting with the row with the index 3.
- The following three lines create an instance of the QVBarModelMapper class and specify that the data for the bar sets should be taken from the model's columns with indexes from 1 to 4 (inclusive).
- To create a connection between the series and the model we set both of those objects to QVBarModelMapper.
-
- Finally the series is added to the chart.
-
- \snippet ../examples/barmodelmapper/tablewidget.cpp 4
-
- To show in QTableView which data corresponds with which bar set, this example uses table coloring.
- When series is added to the chart, it is assigned a color based on the currently selected theme.
- Code below extracts that color from the series and uses it to create colored QTableView.
- Coloring of the view is not a part of the QChart functionality.
-
- \snippet ../examples/barmodelmapper/tablewidget.cpp 5
-
- We would like to have categories placed on the chart's axis that describe what the data means.
- Next snippet shows how to do that.
-
- \snippet ../examples/barmodelmapper/tablewidget.cpp 6
-
- To avoid setting up the QGraphicsScene we use the QChartView class that does it for us. The QChart object pointer is used as a parameter of the QChartView constructor.
- To make the render look nicer Antialiasing is turned on and the minimum size of the chartView widget is set.
-
- \snippet ../examples/barmodelmapper/tablewidget.cpp 7
-
- Finally, we place both widgets in a layout and use the layout as the application layout.
-
- \snippet ../examples/barmodelmapper/tablewidget.cpp 8
-
- The application is ready. Try modifying the data in the table view and see how it affects the chart.
-*/