Marble: Difference between revisions

From KDE Community Wiki
No edit summary
(Move first community stuff over from techbase)
Line 1: Line 1:
= Marble Community =
== Hot topics ==


[[Schedules/MarbleMaps1.0| Marble Maps 1.0 (Android)]]
[[Schedules/MarbleMaps1.0| Marble Maps 1.0 (Android)]]
Line 5: Line 5:
[[/TestingVectorOSM| Testing Vector OSM]]
[[/TestingVectorOSM| Testing Vector OSM]]


== Resources ==
== Tools for Marble ==
Here are just some links for now.


[http://techbase.kde.org/Projects/Marble Marble Technical pages]
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]
;[https://phabricator.kde.org/project/profile/38/ Phabricator]
;[https://reviewboard.kde.org/groups/marble/ Review Board (superceded by Phabricator)]
;[https://api.kde.org/marble/html/index.html API Docs of libmarblewidget (master branch)]
;[https://ebn.kde.org/apidocs/apidox-kde-4.x/kdeedu-marble.html APIDOX reports]
;[https://ebn.kde.org/krazy/reports/kde-4.x/kdeedu/marble/index.html Krazy reports]
 
 
== valgrind  ==
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


== Meetings ==
[[Multimedia/MarbleWeekend2012| Marble sprint 2012]]
[[Multimedia/MarbleWeekend2012| Marble sprint 2012]]


[[/Protocol| Minutes of Saturday]]
[[/Protocol| Minutes of Saturday]]
== Other ==
[http://techbase.kde.org/Projects/Marble Marble Technical pages]

Revision as of 20:57, 20 October 2016

Hot topics

Marble Maps 1.0 (Android)

Testing Vector OSM

Tools for Marble

Here are some tools and checks that are performed on marble code:

Marble Open Bugs
Phabricator
Review Board (superceded by Phabricator)
API Docs of libmarblewidget (master branch)
APIDOX reports
Krazy reports


valgrind

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

Meetings

Marble sprint 2012

Minutes of Saturday

Other

Marble Technical pages