GitLab

1) Added "interface" AbstractDataSubmitter which is the base class for
all data sending strategies.
2) Added "interface" AbstractJsonDataSubmitter which is the base class
for all JSON sending strategies.
3) Existing data sending functionality is extracted to the
DefaultDataSubmitter class.
4) Simplified existing solution: used built-in redirects resolving
instead of manually implemented.
5) Qt 5.9 is required.

Explicitly agreed by everyone who has relevant contributions in here,
namely Aleix, Kevin, Vitaly's employer and myself.

Summary:
Some sort of applications require to store or load settings in a custom
period of time. For example, if an application is a plugin, it might be
unloaded before qApp exists. In this case all settings will be lost.

Reviewers: vkrause

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D19882

Summary:
"Active" state means that all data collected by the data source will be
sent to a server.
This change aims to give a user more control of what data they want to
send. Without this functionality the user might decide to reduce
telemetry level because of one small part of it. This means that we can
collect less statistic without a really good reason.

Reviewers: vkrause

Differential Revision: https://phabricator.kde.org/D19757

Summary: It allows to perform fast look up when needed

Reviewers: vkrause

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D19758

Summary:
This method provides human-readable name that supposed to be used in
UI elements. One of the usage cases is to give the user an ability to
work with individual data sources (e.g., check data, activate/
deactivate, check description, and so on).
This method is not pure virtual because there are might be some data
sources that are not good for individual processing by the user. For
example, trackers of individual QML properties.

Reviewers: vkrause

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D19756

Summary:
People often create a temporary build directory inside of the repository
directory in order to not contaminate top level directory. For this case
it is useful to have all these directories excluded from the version
control tracking.

Reviewers: vkrause

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D19754

Summary:
This makes sense because a string returned by this method is literally a
unique identifier that can be used either on a server side to identify a
data source or in an app itself for a lot of different purposes, e.g.,
for mapping data sources or performing some fast lookup by ID.
A method for getting a short user-visible name will be introduced in one
of the further revisions.

Reviewers: vkrause

Differential Revision: https://phabricator.kde.org/D19727

Reviewers: vkrause

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D19725

Reviewers: vkrause

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D19724

Reviewers: vkrause

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D19505

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

GammaRay is dropping that as well now, which was the only remaining user
of this.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Summary:
for consistency with KF5 frameworks

This file could be much further simplified if the Qt4 support can be removed...

Test Plan: builds

Reviewers: vkrause

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D14833

This allows the usage of more standard-conforming redirection to migrate
the submission interface.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

We only need that for the Qt Quick UI anyway, which doesn't exist for Qt4.