Projects/Marble/Placemark - Revision history

Tgridel: /* Overview of Placemarks in Marble */

2011-12-26T19:41:55Z

‎Overview of Placemarks in Marble

Tgridel: /* Overview of Placemarks in Marble */

2011-12-26T19:19:54Z

‎Overview of Placemarks in Marble

Tgridel at 19:19, 12 September 2009

2009-09-12T19:19:01Z

Tgridel at 21:06, 22 July 2009

2009-07-22T21:06:18Z

Tgridel at 21:04, 22 July 2009

2009-07-22T21:04:54Z

Tgridel: Created page with '== 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 f...'

2009-07-21T22:23:35Z

Created page with '== 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 f...'

New page

== 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).

It uses a {{class|PlaceMarkLoader|kdeedu|4.2}} to perform the file reading thanks to a {{class|GeoDataParser|kdeedu|4.2}}.

@@ Line 1: / Line 1: @@
-== Overview of Placemarks in Marble ==
+= Overview of Placemarks in Marble =
 The {{class|GeoDataPlacemark|kdeedu|4.x}} is the class representing a placemark in Marble, with GeoData classes following kml specification. There are basically 2 kinds of Placemarks: Point Placemarks, and Placemarks containing a Geometry class inheriting {{class|GeoDataGeometry|kdeedu|4.x}}.
-=== Registration and use in MarbleModel ===
+== Registration and use in MarbleModel ==
 The {{class|MarbleModel|kdeedu|4.x}} provides registration of Placemarks within a {{class|GeoDataTreeModel|kdeedu|4.x}}. The tree model stores multiple {{class|GeoDataDocument|kdeedu|4.x}} corresponding to the data they hold.
 It is used currently by 3 frameworks:
-- The {{class|FileManager|kdeedu|4.x}} performs file reading and then signals that files have been added/removed. It registers its document in the tree model.
+=== File Management ===
-- 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 then provides the resulting Placemarks in the tree model.
+The {{class|FileManager|kdeedu|4.x}} performs file reading and then signals that files have been added/removed. It registers its document in the tree model.
-- The {{class|PositionProvider|kdeedu|4.x}} class has a document to display the current position, as well as the track stored of past positions. That document belongs in the tree model.
+* Centralise file parsing while relying on the {{class|MarbleRunnerManager|kdeedu|4.x}} to support various file formats thanks to Parsing plugins.
 The Point placemarks are displayed thanks to the {{class|PlacemarkLayout|kdeedu|4.x}} which does layouting of the labels, and filtering of the important placemarks to render, based on a popularity ranking.
 The Geometry placemarks are displayed thanks to the {{class|GeometryLayer|kdeedu|4.x}} which contains a {{class|GeoGraphicsScene|kdeedu|4.x}}.

@@ Line 1: / Line 1: @@
 == Overview of Placemarks in Marble ==
-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).
+The {{class|GeoDataPlacemark|kdeedu|4.x}} is the class representing a placemark in Marble, with GeoData classes following kml specification. There are basically 2 kinds of Placemarks: Point Placemarks, and Placemarks containing a Geometry class inheriting {{class|GeoDataGeometry|kdeedu|4.x}}.
-It depends on the {{class|FileManager|kdeedu|4.x}} which performs the actual file reading and then signals that files have been added/removed.
+=== Registration and use in MarbleModel ===
-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
+It is used currently by 3 frameworks:
-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 {{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 then provides the resulting Placemarks in the tree model.
-The MarbleRunnerManager holds the resulting Placemarks until another query is input.
+- The {{class|PositionProvider|kdeedu|4.x}} class has a document to display the current position, as well as the track stored of past positions. That document belongs in the tree model.

@@ Line 1: / Line 1: @@
 == 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.

@@ Line 7: / Line 7: @@
 The PlaceMarkManager keeps some information related to the files and data that it read. It provides
- * a list of file names
+* a list of file names
- * a {{class|FileViewModel|kdeedu|4.2}} which presents the list of files
+* a {{class|FileViewModel|kdeedu|4.2}} which presents the list of files
- * a {{class|MarblePlacemarkModel|kdeedu|4.2}} which presents the list of all placemarks of all files
+* 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}}.
+* a {{class|MarbleGeometryModel|kdeedu|4.2}} which represents the list of all files' in-memory representation as {{class|GeoDataDocument|kdeedu|4.2}}.

← Older revision		Revision as of 21:04, 22 July 2009
Line 4:		Line 4:

	It uses a {{class\|PlaceMarkLoader\|kdeedu\|4.2}} to perform the file reading thanks to a {{class\|GeoDataParser\|kdeedu\|4.2}}.		It uses a {{class\|PlaceMarkLoader\|kdeedu\|4.2}} to perform the file reading thanks to a {{class\|GeoDataParser\|kdeedu\|4.2}}.
		+
		+	The PlaceMarkManager keeps some information related to the files and data that it read. It provides
		+
		+	* a list of file names
		+	* a {{class\|FileViewModel\|kdeedu\|4.2}} which presents the list of files
		+	* 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}}.