Marble/Dgml: Difference between revisions
< Marble
SaroEngels (talk | contribs) |
m Ochurlaud moved page Projects/Marble/Dgml to Marble/Dgml |
(No difference)
| |
Revision as of 21:01, 10 March 2016
DGML
Extended planet support
Extended planet support should have these requirements:
- A method Planet* MarbleModel::planet() which returns an object of Planet class type.
- The Planet class should store all kinds of properties for a planet (e.g. name, radius, all planetary constants) and should provide setters and getters for them.
- A PlanetFactory that allows to create these planet objects -- either just by providing a name id (to create planets from preset settings) -- or by providing the full amount of properties.
- For a start it would be ok to store the parameters for the planets in the source code. In the next step DGML support would be necessary (so that the preset settings can be provided in a central dgml-file and so that one can also pass them alternatively in each DGML file via the "target"-tag. This should work like a link which references the standard planetspecs in file included within marble.