| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
The place files were in src/location as a holdover from when
qgeoplace was used. Moved it into the places directory instead.
Change-Id: Ide98fba615c8ff5a73493c81eaefc19b21f2203a
Reviewed-by: Alex <alex.blasche@nokia.com>
|
|
|
|
|
|
|
| |
Change-Id: Id1789bca6cdefd3d6ca6381d06b0419e5d97aeee
Reviewed-by: Samael Wang <freesamael@gmail.com>
Reviewed-by: Alex <alex.blasche@nokia.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It may be possible that other rating values
could be added to the rating object e.g.
a count for how many gave a rating 1
a count for now many gave a rating of 2
or perhaps ratings for different aspects
of a place eg.
service
cleanliness
etc.
Therefore ratings should be used instead or rating.
Change-Id: I8a46646942dcd938bcee31921cabfa9df9862adc
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
| |
Change-Id: Ia5b353e7f97f2bc93c988cbfbd8d57784d3e3bbd
Reviewed-by: Alex <alex.blasche@nokia.com>
|
|
|
|
|
|
|
| |
Also fix constness of contactDetails()
Change-Id: I6662a87b0810a2a25c096cef6f507f67d8697ee1
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
| |
Implementation detail shouldn't be exposed, not using the map
also results in less code for the developer.
Change-Id: I767cd60c4b614e86d84069d1737a4c5993a63875
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The REST server now supports labels for each contact value, so
now it makes sense to incorporte the ContactValue class.
ContactValue = user visible label + value(phone number, email etc)
We use a map type implementation where the key for the map
is the contact type and the value is a list of contact values.
The first element of each list becomes the primary value.
Eg the primaryPhone() field references the first element in the
list of phone numbers.
The setters for the primary___() functions has been removed.
Url has also been renamed to Website to keep in line with LBSP.
Change-Id: I9382a8286c5348bd1eb93d93f25088dfdf321852
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
| |
Q_LOCATION_EXPORT_TEMP -> Q_LOCATION_EXPORT
Change-Id: I65b1d9c59ab2d2ad437f1934013eb53b0b96e606
Reviewed-by: Alex <alex.blasche@nokia.com>
|
|
|
|
|
|
|
|
| |
Removing all location related defines from qglobal.h causes this macro
to fail. It seems that it is no longer used in new modules.
Change-Id: Ifbfa6f7f40a419e0890a4611bab7e2d681f63a04
Reviewed-by: Alex <alex.blasche@nokia.com>
|
|
|
|
|
|
|
|
|
| |
Each module handles each its own exports. We need to change the
QtLocation version, remove the qglobal.h define and then add it back
under the old name in QtLocation
Change-Id: I7530a251b78402215a466cd55a33ec24664786b7
Reviewed-by: Alex <alex.blasche@nokia.com>
|
|
|
|
|
|
|
|
| |
Change-Id: I559c96427db542dd71122f937dff90c900a02241
Reviewed-on: http://codereview.qt-project.org/6041
Sanity-Review: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
Reviewed-by: abcd <qt_abcd1@ovi.com>
|
|
|
|
|
|
|
| |
Change-Id: Ic902592c3367a76fc0e23c237712224abbf31703
Reviewed-on: http://codereview.qt-project.org/6206
Sanity-Review: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
| |
Change-Id: Id1f5d248fd17554b17211d48facf3f6b85565853
Reviewed-on: http://codereview.qt-project.org/5341
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The attribution is a rich text string that some place providers may
require to be displayed when a place is shown to an end user.
Also remove unnecessary semi-colons for the declarative place
header
Change-Id: Id5b70a1962e80afce536fc2f01674db8456116ce
Reviewed-on: http://codereview.qt-project.org/5350
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
| |
Change-Id: I4986fbd7579c31a4d1e13d388181a39286b75b23
Reviewed-on: http://codereview.qt-project.org/5277
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Add QT_{BEGIN,END}_HEADER
Add QT_{BEGIN,END}_NAMESPACE
Add QT_MODULE(Location)
Change-Id: Ib12682b847d9439c0e55e78fdf8a71ee8406c282
Reviewed-on: http://codereview.qt-project.org/5435
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
| |
Change-Id: I0ced086aea91189f6e74c2e2ca13776d79b537d5
Reviewed-on: http://codereview.qt-project.org/5274
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: abcd <qt_abcd1@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
| |
Change-Id: Iac577b229ffa1b82a35921f748a74e5655cf3d25
Reviewed-on: http://codereview.qt-project.org/5196
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: abcd <qt_abcd1@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
additionalData is now superseded by place attributes.
In the qjsondetailsparser processAdContentPackages used to put
some content into additional data. indicating whether a place type
was an "ad_prime_plus" place. For the Qt 5 use case, for 3rd party
developers this doesn't seem necessary and neither does it seem
part of the new REST API.
Also it seems that the search type has erroneously been placed into
the additionalData. This is not necessary as the SearchResult
already has the type defined.
Change-Id: I35545b48666700a08aa93bfa0fa90ef2f301163e
Reviewed-on: http://codereview.qt-project.org/5213
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
|
|
|
|
|
|
|
|
| |
These should've been removed when we shifted to using content
objects to hold paginated classes.
Change-Id: Iede78a69a840292c2917cdcc716ad335e775c8f8
Reviewed-on: http://codereview.qt-project.org/5214
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|
|
This is to be more consistent with the other place classes
like QPlaceManager.
The alternative would be for everything to have the QGeo prefix
e.g QGePlaceManager, QGeoPlaceCategory,
the Geo prefix does not help much in avoiding name collisions
since 'Place' shouldn't collide with anything anyway.
For classes like routing the Geo prefix is necessary to give
context for what's being routed.
Change-Id: Ibcf6e6909a41ea0ce2c402e24b427496d06bf243
Reviewed-on: http://codereview.qt-project.org/5210
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Aaron McCarthy <aaron.mccarthy@nokia.com>
|