Marble/Placemark: Difference between revisions

From KDE Community Wiki
No edit summary
No edit summary
Line 1: Line 1:
== Overview of Placemarks in Marble ==
== Overview of Placemarks in Marble ==


The {{class|PlaceMarkManager|kdeedu|4.2}} is handled by the {{class|MarbleModel|kdeedu|4.2}} and provides registration of KML data files for Marble (it should handle all data files in the future).
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 uses a {{class|PlaceMarkLoader|kdeedu|4.2}} to perform the file reading thanks to a {{class|GeoDataParser|kdeedu|4.2}}.
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 files and data that it read. It provides  
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


* a list of file names
 
* a {{class|FileViewModel|kdeedu|4.2}} which presents the list of 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}}.
* a {{class|MarblePlacemarkModel|kdeedu|4.2}} which presents the list of all placemarks of all files
 
* a {{class|MarbleGeometryModel|kdeedu|4.2}} which represents the list of all files' in-memory representation as {{class|GeoDataDocument|kdeedu|4.2}}.
The MarbleRunnerManager holds the resulting Placemarks until another query is input.

Revision as of 19:19, 12 September 2009

Overview of Placemarks in Marble

The PlaceMarkManager is handled by the MarbleModel 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 FileManager 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 MarblePlacemarkModel which presents the list of all placemarks of all files


The MarbleRunnerManager 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 MarbleAbstractRunner.

The MarbleRunnerManager holds the resulting Placemarks until another query is input.