(→Intro) |
|||
| (9 intermediate revisions by one user not shown) | |||
| Line 41: | Line 41: | ||
=== With Python === | === With Python === | ||
==== Intro ==== | ==== Intro ==== | ||
| + | ;[http://techbase.kde.org/Projects/Marble/MarblePythonInstructions Installing Marble's Python bindings] | ||
;[[/MarblePythonHello|Hello World]] | ;[[/MarblePythonHello|Hello World]] | ||
;[[/MarblePythonMarbleWidget|Changing basic map properties]] | ;[[/MarblePythonMarbleWidget|Changing basic map properties]] | ||
;[[/MarblePythonSignalsSlots|Creating a window with controls]] | ;[[/MarblePythonSignalsSlots|Creating a window with controls]] | ||
| − | ==== | + | ==== Loading Files ==== |
;[[/Runners/MarblePythonLoadingKML|Loading KML files into Marble]] | ;[[/Runners/MarblePythonLoadingKML|Loading KML files into Marble]] | ||
;[[/Runners/MarblePythonLoadingOSM|Loading OSM files into Marble]] | ;[[/Runners/MarblePythonLoadingOSM|Loading OSM files into Marble]] | ||
| + | |||
| + | ==== GeoData ==== | ||
;[[/Runners/MarblePythonDisplayGeoDataPlacemark|Display GeoData Placemark]] | ;[[/Runners/MarblePythonDisplayGeoDataPlacemark|Display GeoData Placemark]] | ||
| + | ;[[/Runners/MarblePythonVehicleTracking|Vehicle Tracking]] | ||
| + | |||
| + | ==== Routing/Runners ==== | ||
| + | This part of the Python API has not yet been ported and the tutorials could not be completed. [https://bugs.kde.org/show_bug.cgi?id=329364 see this bug for more info]. | ||
| + | |||
| + | ==== GeoPainter ==== | ||
| + | ;[[/Routing/MarblePythonGeoPainter|Painting onto the map]] | ||
| + | ;[[/MarblePythonLayerInterface|Drawing in Custom Layers]] | ||
| − | |||
;[[/MarbleDBus|via a shell script]] | ;[[/MarbleDBus|via a shell script]] | ||
This part of the Python API has not yet been ported and the tutorials could not be completed. see this bug for more info.
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 