subsurface/desktop-widgets/tab-widgets/TabDivePhotos.h
Tomaz Canabrava 1fc4fba69f 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-06 18:23:25 -07:00

33 lines
562 B
C++

#ifndef TAB_DIVE_PHOTOS_H
#define TAB_DIVE_PHOTOS_H
#include "TabBase.h"
namespace Ui {
class TabDivePhotos;
};
class DivePictureModel;
class TabDivePhotos : public TabBase {
Q_OBJECT
public:
TabDivePhotos(QWidget *parent);
~TabDivePhotos();
void updateData() override;
void clear() override;
protected:
void contextMenuEvent(QContextMenuEvent *ev) override;
private:
void addPhotosFromFile();
void addPhotosFromURL();
void removeAllPhotos();
void removeSelectedPhotos();
Ui::TabDivePhotos *ui;
DivePictureModel *divePictureModel;
};
#endif