Marble/NewMarbleMoldules: Difference between revisions

From KDE TechBase
(Page moved to community wiki)
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
We want to simplify packaging and maintenance of Marble. And we want to make it easier for KDE application authors to link against the marble library by getting rid of a kde-edu dependency.
{{ Moved To Community }}
 
So starting with KDE 4.5 the Marble source code is supposed to be reorganized:
 
==Marble Qt Library==
 
* It's <b>Qt Only</b>. No KDE dependencies.
* Contains the actual Marble library. Suggested package name: "libmarble".
* Contains the base data. This includes the most basic maps: <i>Atlas</i>, <i>Satellite</i>, <i>OSM</i> and <i>Plain Map</i>. Suggested package name: "libmarble-data".
* Contains all base <i>plugins</i>.
* Provides the Marble Qt application (Executable: "marbleqt") as an example application (Compilation of this part can be switched off at wish).
* Located in SVN at <code>kdesupport/libmarble</code>
* Provides Qt development documentation, bindings and tools for Marble. Suggested package name: libmarble-dev.
 
==Marble KDE application==
* Provides the Marble Application (Executable"marble"). Suggested package name: kdeedu-marble.
* Provides the KPart. Actual location of this part in SVN needs to be evaluated for best reuse.
* Provides optional data ( <i>Moon</i>, <i>Historical Map</i>, <i>Precipitation</i>, <i>Temperature</i>, etc.)
* Located in SVN at <code>kdeedu/marble</code>
 
==Other==
* What should happen to the worldclock plasmoid? Move it to the other KDE plasmoids (which would depend on libmarble inside kdesupport).

Latest revision as of 04:51, 26 October 2016

This page is now on the community wiki.