subsurface/desktop-widgets/tab-widgets/TabBase.h

// SPDX-License-Identifier: GPL-2.0
#ifndef TAB_BASE_H
#define TAB_BASE_H

#include <QWidget>

struct dive;

class TabBase : public QWidget {
	Q_OBJECT

public:
	using QWidget::QWidget;
	virtual void updateData() = 0;
	virtual void clear() = 0;
	virtual void updateUi(QString titleColor);
};

#endif
Add SPDX header to desktop widgets Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2017-04-27 18:26:05 +00:00			`// SPDX-License-Identifier: GPL-2.0`
Break down MainTab into smaller classes Maintab is one of our most complex classes, and it's something I'm not actually proud of. But it currently works and the idea of splitting it was in my head for quite a while. This is the third or fourth tentative of splitting it, and this time I let the most complex part of it untouched, the Notes and Equipment tab are way too complex to untangle right now on my limited time. A new class 'TabBase' should be used for any new tab that we may create, and added on the MainTab (see the new lines on the MainTab constructor). Also, Extra Info, Information, Photos and Statistics where ported to this new way helping reduce the number of lines and functions on the MainTab quite a bit. Overall this is a step in the right direction for the future. Signed-off-by: Tomaz Canabrava <tcanabrava@kde.org> Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2017-04-04 17:21:30 +00:00			`#ifndef TAB_BASE_H`
			`#define TAB_BASE_H`

			`#include <QWidget>`

			`struct dive;`

			`class TabBase : public QWidget {`
			`Q_OBJECT`

			`public:`
cleanup: replace empty TabBase constructor by using directive Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at> 2022-03-11 19:48:46 +00:00			`using QWidget::QWidget;`
Break down MainTab into smaller classes Maintab is one of our most complex classes, and it's something I'm not actually proud of. But it currently works and the idea of splitting it was in my head for quite a while. This is the third or fourth tentative of splitting it, and this time I let the most complex part of it untouched, the Notes and Equipment tab are way too complex to untangle right now on my limited time. A new class 'TabBase' should be used for any new tab that we may create, and added on the MainTab (see the new lines on the MainTab constructor). Also, Extra Info, Information, Photos and Statistics where ported to this new way helping reduce the number of lines and functions on the MainTab quite a bit. Overall this is a step in the right direction for the future. Signed-off-by: Tomaz Canabrava <tcanabrava@kde.org> Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2017-04-04 17:21:30 +00:00			`virtual void updateData() = 0;`
			`virtual void clear() = 0;`
desktop: automatically pick a good theme title color The preference setting seemed far too strange to do this. And not very user friendly. So instead we figure out if this is a dark theme or not by looking at text and background colors in the palette, and make sure we get notified if that changes. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2020-11-04 21:09:44 +00:00			`virtual void updateUi(QString titleColor);`
Break down MainTab into smaller classes Maintab is one of our most complex classes, and it's something I'm not actually proud of. But it currently works and the idea of splitting it was in my head for quite a while. This is the third or fourth tentative of splitting it, and this time I let the most complex part of it untouched, the Notes and Equipment tab are way too complex to untangle right now on my limited time. A new class 'TabBase' should be used for any new tab that we may create, and added on the MainTab (see the new lines on the MainTab constructor). Also, Extra Info, Information, Photos and Statistics where ported to this new way helping reduce the number of lines and functions on the MainTab quite a bit. Overall this is a step in the right direction for the future. Signed-off-by: Tomaz Canabrava <tcanabrava@kde.org> Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2017-04-04 17:21:30 +00:00			`};`

			`#endif`