Difference between revisions of "User:Mansona/Marble geodata"

Jump to: navigation, search
(New page: ==Introduction== the geodata library is were the magic happens from within marble, once you understand this library you have opened pandora's box and the world will be yours for the takin...)
 
 
Line 1: Line 1:
 
==Introduction==  
 
==Introduction==  
the geodata library is were the magic happens from within marble, once you understand this library you have opened pandora's box and the world will be yours for the taking... Now for the explination
+
This page is intended to allow for a fuller understanding of how Marble deals with Layers/Geodata. After reading this guide you should be able to:
 +
# understand how marble paints geodata on top of texture data
 +
# develop your own handler for geodata
 +
 
 +
==Sections==
 +
The Geodata Implementation has been split into two main sections, a parser and a handler.
 +
 
 +
 
 +
===Handler===
 +
 
 +
===Data===
 +
refers to a geodata document, this is what the parser produces if working with a set of geodata
 +
 
 +
====Difference between a scene and a Data Document====
 +
Not really sure of the difference, but there is one!
 +
 
 +
====Element Dictionary ====
 +
an element dictionary is intended to be a static list of all of the tags in XML namespace of your geodata XML. this allows for one static list of tags and prevents large amounts of string comparisons throughout the code
 +
 
 +
==Process==
 +
#create a new GeoDataParser or GeoSceneParser with enum argument referring to the type of document. Enum is available in respective header files
 +
#use the parser to read the file using Parser->read(String filename)
 +
#extract the datadocument from the parser using parser->releaseDocument()

Latest revision as of 21:47, 2 September 2008

Contents

[edit] Introduction

This page is intended to allow for a fuller understanding of how Marble deals with Layers/Geodata. After reading this guide you should be able to:

  1. understand how marble paints geodata on top of texture data
  2. develop your own handler for geodata

[edit] Sections

The Geodata Implementation has been split into two main sections, a parser and a handler.


[edit] Handler

[edit] Data

refers to a geodata document, this is what the parser produces if working with a set of geodata

[edit] Difference between a scene and a Data Document

Not really sure of the difference, but there is one!

[edit] Element Dictionary

an element dictionary is intended to be a static list of all of the tags in XML namespace of your geodata XML. this allows for one static list of tags and prevents large amounts of string comparisons throughout the code

[edit] Process

  1. create a new GeoDataParser or GeoSceneParser with enum argument referring to the type of document. Enum is available in respective header files
  2. use the parser to read the file using Parser->read(String filename)
  3. extract the datadocument from the parser using parser->releaseDocument()

This page was last modified on 2 September 2008, at 21:47. This page has been accessed 429 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal