|
|
(3 intermediate revisions by 2 users not shown) |
Line 1: |
Line 1: |
| == Overview of Placemarks in Marble ==
| | {{ Moved To Community }} |
| | |
| The {{class|PlaceMarkManager|kdeedu|4.x}} is handled by the {{class|MarbleModel|kdeedu|4.x}} and provides registration of Placemarks from KML data files for Marble (it should handle placemarks for all data files in the future).
| |
| | |
| It depends on the {{class|FileManager|kdeedu|4.x}} which performs the actual file reading and then signals that files have been added/removed.
| |
| | |
| The PlaceMarkManager keeps some information related to the data that it presents. It provides a {{class|MarblePlacemarkModel|kdeedu|4.x}} which presents the list of all placemarks of all files
| |
| | |
| | |
| The {{class|MarbleRunnerManager|kdeedu|4.x}} is a framework to query external servers for placemarks. The user types the query in the search line of the ControlBox widget, and then the MarbleRunnerManager triggers asynchronous runners which inherit from {{class|MarbleAbstractRunner|kdeedu|4.x}}.
| |
| | |
| The MarbleRunnerManager holds the resulting Placemarks until another query is input.
| |
Latest revision as of 04:46, 26 October 2016
This page is now on the community wiki.