diff options
| author | Gatis Paeglis <gatis.paeglis@qt.io> | 2016-12-20 11:42:45 +0100 |
|---|---|---|
| committer | Gatis Paeglis <gatis.paeglis@qt.io> | 2016-12-21 11:35:41 +0000 |
| commit | 1b30c228f653a712e884adcbb22750b5643c0452 (patch) | |
| tree | 10c8a9c88b882e2d0b0299cb33868c4e4b8b3d90 /qt-ostree | |
| parent | ffc7a483fba2b2e902550072780c87c6f066e947 (diff) | |
Remove impractical API from QOtaClient
These convenience methods do not provide any real
convenience after all. This API is not practical
and extenting it would be pain (each new json property
would require a new accessor method for each *Metadata
version).
The reduced subset of API is still sufficient to be used
in property bindings:
Label { text: extractVersion(OtaClient.remoteMetadata, "version") }
Label { text: extractVersion(OtaClient.remoteMetadata, "description") }
Where extractVersion() parses JSON metadata. If the metadata
file is huge (parsing takes long time), API users can subscribe
to onRemoteMetadataChanage:
onRemoteMetadataChanged: {
// parse the whole metadata file only once and set
// appropriate properties.
}
Change-Id: If095e8c17712fa7b06bd577364ec10ae6ca6d52e
Reviewed-by: Gatis Paeglis <gatis.paeglis@qt.io>
Diffstat (limited to 'qt-ostree')
| -rwxr-xr-x | qt-ostree/qt-ostree | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/qt-ostree/qt-ostree b/qt-ostree/qt-ostree index d436277..a5b4798 100755 --- a/qt-ostree/qt-ostree +++ b/qt-ostree/qt-ostree @@ -185,9 +185,7 @@ usage() echo echo "--ota-json FILE" echo - echo " JSON file containing an OTA update metadata, can be arbitrary formatted. The" - echo " following top-level fields have convenience methods in the Qt/QML OTA API:" - echo " version, description." + echo " JSON file containing an OTA update metadata." echo echo "--ostree-repo DIR" echo |