| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
There is little point maintaining QVariantDataSet and proxy when we
have QAbstractItemModel based proxy, so removed it and related classes.
Moved and refactored those under rainfall as an example of custom proxy
implementation.
Change-Id: I3df8b50f1780b8a88c27d91a284ec3ed3e6095fb
Reviewed-by: Mika Salmela <mika.salmela@digia.com>
|
| |
|
|
|
|
|
| |
Rainfall example modified to demonstrate mapping.
Change-Id: I385e018524f4c9df5914c2cf4f8ae643f585f5c7
Reviewed-by: Mika Salmela <mika.salmela@digia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Variant datasets are just lists of variant lists.
To use variant dataset, you need to provide mapping
between the chart elements and variant list indices.
E.g. in case of bar chart, one index maps for
row, another for column, and third for value.
The purpose of variant dataset is to make it possible
to have just one blob of data and parse different views
on it using different mappings.
Note that since variant datasets utilize variants,
they are not likely to be highly performant. However,
the impact is only felt once when the data is parsed
into format understood by datavis.
Change-Id: I0da39bd18528370afb5060368b0c3280e31e1cf7
Reviewed-by: Mika Salmela <mika.salmela@digia.com>
|
| |
|
|
|
| |
Change-Id: Iae4ce2f9d97c19a3337e87ad67da120b58cf71c7
Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
|
| |
|
|
|
|
|
| |
Also reorganized examples a bit; moved duplicate configs to examples.pri.
Change-Id: If518447ffa45e2b800fb3da9e6a7425d86209d35
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@digia.com>
|
| |
|
|
|
| |
Change-Id: Id65b353260e8d044903ece306a43cd3d8b3ec6bb
Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
|
|
|
Unnecessary subdirectory levels deleted from examples and src
Change-Id: I88892b4fc92784e706be2264eeb7d6208250a50f
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@digia.com>
Reviewed-by: Mika Salmela <mika.salmela@digia.com>
|
