qiurui
/
qtdatavis3d
mirror of https://github.com/qt/qtdatavis3d.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
qtdatavis3d/examples/datavisualization/customproxy/variantdataset.h

58 lines
1.4 KiB
C
Raw Normal View History

Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
/****************************************************************************
**
Copyright header changes Copyright header changes for 5.5. Change-Id: I0361cfe1ebdb28955cb927700f14cf7b72694421 Reviewed-by: Miikka Heikkinen <miikka.heikkinen@theqtcompany.com>
2015-04-14 10:35:51 +00:00
** Copyright (C) 2015 The Qt Company Ltd
Copyright headers updated Task-number: QTRD-2112 Change-Id: I0dad7933af2dcd0386b8243f71bbd949f92aab8c Change-Id: I0dad7933af2dcd0386b8243f71bbd949f92aab8c Reviewed-by: Miikka Heikkinen <miikka.heikkinen@digia.com>
2013-08-13 08:08:56 +00:00
** All rights reserved.
Copyright header changes Copyright header changes for 5.5. Change-Id: I0361cfe1ebdb28955cb927700f14cf7b72694421 Reviewed-by: Miikka Heikkinen <miikka.heikkinen@theqtcompany.com>
2015-04-14 10:35:51 +00:00
** For any questions to The Qt Company, please use contact form at http://qt.io
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
**
Change copyright headers. Change-Id: I453438fee92f18c983c1bef04c68b24a7ff72cf9 Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com> Reviewed-by: Mika Salmela <mika.salmela@theqtcompany.com>
2014-11-07 08:07:00 +00:00
** This file is part of the Qt Data Visualization module.
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
**
Change copyright headers. Change-Id: I453438fee92f18c983c1bef04c68b24a7ff72cf9 Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com> Reviewed-by: Mika Salmela <mika.salmela@theqtcompany.com>
2014-11-07 08:07:00 +00:00
** Licensees holding valid commercial license for Qt may use this file in
** accordance with the Qt License Agreement provided with the Software
** or, alternatively, in accordance with the terms contained in a written
Copyright header changes Copyright header changes for 5.5. Change-Id: I0361cfe1ebdb28955cb927700f14cf7b72694421 Reviewed-by: Miikka Heikkinen <miikka.heikkinen@theqtcompany.com>
2015-04-14 10:35:51 +00:00
** agreement between you and The Qt Company.
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
**
Copyright headers updated Task-number: QTRD-2112 Change-Id: I0dad7933af2dcd0386b8243f71bbd949f92aab8c Change-Id: I0dad7933af2dcd0386b8243f71bbd949f92aab8c Reviewed-by: Miikka Heikkinen <miikka.heikkinen@digia.com>
2013-08-13 08:08:56 +00:00
** If you have questions regarding the use of this file, please use
Change copyright headers. Change-Id: I453438fee92f18c983c1bef04c68b24a7ff72cf9 Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com> Reviewed-by: Mika Salmela <mika.salmela@theqtcompany.com>
2014-11-07 08:07:00 +00:00
** contact form at http://qt.io
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
**
****************************************************************************/
Removed QVariantDataSet and related classes. 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>
2013-08-09 11:35:07 +00:00
#ifndef VARIANTDATASET_H
#define VARIANTDATASET_H
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
Clean up public API and includes usage Change-Id: I20ba0ffafa6bbe22d624a15fe3046ef2e33ab6d7 Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
2014-02-17 14:18:27 +00:00
#include <QtCore/QScopedPointer>
#include <QtCore/QVariantList>
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
Document customproxy example The screenshot needs to be retaken. Task-number: QTRD-2399 Change-Id: I216b082b9660ba756902a8c6bf9393039956f2f5 Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
2013-10-10 08:15:47 +00:00
//! [1]
Removed QVariantDataSet and related classes. 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>
2013-08-09 11:35:07 +00:00
typedef QVariantList VariantDataItem;
typedef QList<VariantDataItem *> VariantDataItemList;
Document customproxy example The screenshot needs to be retaken. Task-number: QTRD-2399 Change-Id: I216b082b9660ba756902a8c6bf9393039956f2f5 Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
2013-10-10 08:15:47 +00:00
//! [1]
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
Removed QVariantDataSet and related classes. 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>
2013-08-09 11:35:07 +00:00
class VariantDataSet : public QObject
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
{
Q_OBJECT
public:
Removed QVariantDataSet and related classes. 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>
2013-08-09 11:35:07 +00:00
explicit VariantDataSet();
~VariantDataSet();
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
Document customproxy example The screenshot needs to be retaken. Task-number: QTRD-2399 Change-Id: I216b082b9660ba756902a8c6bf9393039956f2f5 Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
2013-10-10 08:15:47 +00:00
//! [0]
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
void clear();
Removed QVariantDataSet and related classes. 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>
2013-08-09 11:35:07 +00:00
int addItem(VariantDataItem *item);
int addItems(VariantDataItemList *itemList);
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
Removed QVariantDataSet and related classes. 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>
2013-08-09 11:35:07 +00:00
const VariantDataItemList &itemList() const;
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
Fix building against 5.6 Apparently Qt modules are now required to use Q_SIGNALS and Q_SLOTS macros instead of 'signals' and 'slots' in headers. Change-Id: I4140b1fff4386d74bb371176919234366965e887 Reviewed-by: Mika Salmela <mika.salmela@theqtcompany.com>
2015-06-17 11:01:44 +00:00
Q_SIGNALS:
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
void itemsAdded(int index, int count);
void dataCleared();
Document customproxy example The screenshot needs to be retaken. Task-number: QTRD-2399 Change-Id: I216b082b9660ba756902a8c6bf9393039956f2f5 Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
2013-10-10 08:15:47 +00:00
//! [0]
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
private:
Removed QVariantDataSet and related classes. 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>
2013-08-09 11:35:07 +00:00
VariantDataItemList m_variantData;
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
Removed QVariantDataSet and related classes. 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>
2013-08-09 11:35:07 +00:00
Q_DISABLE_COPY(VariantDataSet)
Variant dataset support for bars 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>
2013-07-05 12:14:37 +00:00
};
#endif