Earthwings (Talk | contribs) (move module / package reorganization up) |
Earthwings (Talk | contribs) (→Routing) |
||
| Line 133: | Line 133: | ||
;[[/RoutingIdeas|General ideas about routing]] | ;[[/RoutingIdeas|General ideas about routing]] | ||
;[[/OnlineRoutingImplementation|Implementation of Online-Routing]] | ;[[/OnlineRoutingImplementation|Implementation of Online-Routing]] | ||
| + | ;[[/RoutingRoadmap|Routing Roadmap]] | ||
== valgrind == | == valgrind == | ||
Contents |
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 platforms 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
Using GeoData:
A little overview of map projections
Possible maps we could use:
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 