| Line 36: | Line 36: | ||
Here are some tools and checks that are performed on marble code: | Here are some tools and checks that are performed on marble code: | ||
| + | ;[https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=marble&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Importance Marble Open Bugs] | ||
;[http://reviewboard.kde.org/groups/marble/ Review Board] | ;[http://reviewboard.kde.org/groups/marble/ Review Board] | ||
;[http://api.kde.org/4.x-api/kdeedu-apidocs/marble/html/index.html API Docs (KDE Trunk)] | ;[http://api.kde.org/4.x-api/kdeedu-apidocs/marble/html/index.html API Docs (KDE Trunk)] | ||
Languages: عربي | Asturianu | Català | Česky | Kaszëbsczi | Dansk | Deutsch | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | Italiano | 日本語 | 한국어 | Norwegian | Polski | Português Brasileiro | Română | Русский | Svenska | Slovenčina | Slovenščina | српски | Türkçe | Tiếng Việt | Українська | 简体中文 | 繁體中文
Welcome!
Here you'll get all the information you need to start Marble development:
Here is some advice about how packaging is supposed to happen on the various plattforms that are supported.
Here are some tools and checks that are performed on marble code:
Here are a few links to various issues we are working on:
the base classes to manipulate geographic data
importing and displaying your data
if you want to fix memory leaks, you can run valgrind with:
valgrind --leak-check=full --track-origins=yes --num-callers=30 marble 2>&1 | tee MARBLE_MEMCHECK
Summaries and logs of scheduled Marble meetings can be found on the following pages:
KDE TechBase 