http://techbase.kde.org/index.php?title=Projects/Marble/Dgml&feed=atom&action=history 2013-05-25T00:04:54Z Revision history for this page on the wiki MediaWiki 1.20.2 http://techbase.kde.org/index.php?title=Projects/Marble/Dgml&diff=39289&oldid=prev 2009-03-08T17:58:33Z

<p>‎<span dir="auto"><span class="autocomment">Extended planet support</span></span></p> <table class='diff diff-contentalign-left'> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr style='vertical-align: top;'> <td colspan='2' style="background-color: white; color:black;">← Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 17:58, 8 March 2009</td> </tr><tr><td colspan="2" class="diff-lineno">Line 5:</td> <td colspan="2" class="diff-lineno">Line 5:</td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"><div>Extended planet support should have these requirements:</div></td><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"><div>Extended planet support should have these requirements:</div></td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del class="diffchange diffchange-inline">1.) </del>A method Planet* MarbleModel::planet() which returns an object of Planet class type.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins class="diffchange diffchange-inline"># </ins>A method Planet* MarbleModel::planet() which returns an object of Planet class type.</div></td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del class="diffchange diffchange-inline">2.) </del>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.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins class="diffchange diffchange-inline"># </ins>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.</div></td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del class="diffchange diffchange-inline">3.) </del>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.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins class="diffchange diffchange-inline"># </ins>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.</div></td></tr> <tr><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'>&#160;</td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del class="diffchange diffchange-inline">4.) </del>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 &quot;target&quot;-tag.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins class="diffchange diffchange-inline"># </ins>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 &quot;target&quot;-tag<ins class="diffchange diffchange-inline">. This should work like a link which references the standard planetspecs in file included within marble</ins>.</div></td></tr> <!-- diff cache key wwwdeveloper:diff:version:1.11a:oldid:39288:newid:39289 --> </table>

SaroEngels http://techbase.kde.org/index.php?title=Projects/Marble/Dgml&diff=39288&oldid=prev 2009-03-08T17:39:13Z

<p>New page: ==DGML== ====Extended planet support==== Extended planet support should have these requirements: 1.) A method Planet* MarbleModel::planet() which returns an object of Planet class type....</p> <p><b>New page</b></p><div>==DGML==<br /> <br /> ====Extended planet support====<br /> <br /> Extended planet support should have these requirements:<br /> <br /> 1.) A method Planet* MarbleModel::planet() which returns an object of Planet class type.<br /> <br /> 2.) 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.<br /> <br /> 3.) 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.<br /> <br /> 4.) 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 &quot;target&quot;-tag.</div>

Tampakrap