|
|
| (19 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| ==Marble Junior Jobs==
| | {{ Moved To Community }} |
| | |
| If you are new to Marble then you want to check this page. We list a few things you can do which are easy tasks and introduce you to Marble development.
| |
| You can possible find some Junior Jobs at [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=marble&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=junior-jobs&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= KDE's Bugzilla].
| |
| | |
| ===Quality Assurance / Documentation===
| |
| We want our <i>Marble source code to look good</i>. The <i>documentation should be concise and helpful</i> and the comments shouldn't have spelling errors. Also it shouldn't have any obvious "formal" bugs. Help us to improve our code quality. This is an easy job that helps you to get familiar with the source code. It's the first thing that absolute beginners usually want to look at. We list a few important issues that need to be checked for <i>regularly</i>:
| |
| | |
| * Try to find <b>spelling errors</b> in the source code comments and in Marble UI strings. (EASY)
| |
| * <b>KDE Krazy check</b>: Have a look at the results of the <i>static code checker</i>: http://www.englishbreakfastnetwork.org/krazy/reports/kde-4.x/kdeedu/marble/index.html. Try to understand possible problems and create a fix for them. (EASY/MEDIUM)
| |
| * Get rid of <b>compile warnings</b>: Compile Marble from scratch and check all the warnings that possibly appear. Try to get rid of the warnings by adding fixes. If parameters are not used, examine why and either remove them or hide the warning or leave it as it is. (EASY-MEDIUM)
| |
| * Compile marble with the cmake option <b>-DPEDANTIC=ON</b>. Fix all errors that come up until Marble compiles through (MEDIUM).
| |
| * <b>Add comments</b>. You don't understand some source code in Marble? Then probably other people won't either. Try to understand it and ask Marble developers. The add some comments so that the next person will be able to understand the source code much easier (MEDIUM).
| |
| * Create <b>API-Documentation</b> (EASY).
| |
| * <b>Review the API</b>. Make sure that the API is Qt-ish (MEDIUM). Read http://qt.gitorious.org/qt/pages/ApiDesignPrinciples and read the Marble source code. Try to find cases which seem to be non-standard. (MEDIUM)
| |
| * Read our <b>Marble Coding Standards</b>: http://websvn.kde.org/trunk/KDE/kdeedu/marble/CODING?revision=700337&view=markup. Ensure that the Marble source code follows it (EASY).
| |
| * Help to <b>translate Marble into your own language</b>. Try to find "weird" translations or translations that don't express things in words that a normal user would understand and correct/report them (MEDIUM).
| |
| | |
| * Check KDE's <b>Bugzilla</b> for any open Marble bugs: https://bugs.kde.org/buglist.cgi?quicksearch=Marble. Try to reproduce the bugs and check whether the bugs are still valid. Remove them if they're not valid anymore and seem to be fixed already (EASY). Try to fix them if they are still valid (MEDIUM/HARD).
| |
| | |
| If you come across a problem don't hesitate to ask us (there are no stupid questions, just people who are afraid of asking for stupid reasons ;-)
| |
| If you want to send in your patch for review, please send it to our mailing list [email protected]. | |
| | |
| | |
| ===KML===
| |
| This section deals with junior jobs that deal with Marble's data structure:
| |
| | |
| ====Implement a "simple" tag for KML support (e.g. LookAt)====
| |
| The <LookAt> tag in KML should be quite easy to implement -- at least compared to the other tags. Alternatively you can try to find a different tag that looks like it would be easy to implement, however you need to check in the handler or data directory whether it is implemented already.
| |
| * Have a look at the KML reference:
| |
| | |
| http://code.google.com/apis/kml/documentation/kmlreference.html#lookat
| |
| | |
| * Have a look at Marble's geodata source (in marble/src/lib/geodata).
| |
| * Try to understand what the parser, the handler and the data stuff does.
| |
| * Create a new handler (EASY)
| |
| * Connect Marble's MarbleMap::setLookAt() command to execute the lookat command
| |
| | |
| ===Create an "Open Recent ..." menu entry===
| |
| In marble/src/KdeMainWindow.cpp use
| |
| | |
| http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKRecentFilesAction.html
| |
| | |
| to create an open recent menu entry for the KDE version of Marble.
| |
| Adding the same functionality to the Qt version of Marble is a bonus task.
| |
| | |
| | |
| ===Displaying Debug Info on request===
| |
| * One could change the MarbleWidget::setTileId method to a
| |
| | |
| MarbleWidget::setDebugInfo( DebugFlags )
| |
| | |
| method where DebugFlags is using QFlags
| |
| | |
| http://doc.trolltech.com/4.5/qflags.html
| |
| | |
| One could then set enable the qDebug messages by e.g. setting
| |
| | |
| m_widget->setDebugInfo( DebugText | ShowTileID );
| |
| | |
| | |
| Level of difficulty: EASY
| |
| | |
| ===Adding Bookmarks===
| |
| <b>Gaurav</b> is already working on this one.
| |
| | |
| * It would be nice if Marble had its own bookmark feature: Like in Konqueror you'd be able to click Bookmark->Add Bookmark and the current position and zoom value would get stored as a bookmark. Once the user would click the bookmark item the original coordinate and zoom value would get restored. You can use MarbleWidget::centerLongitude(), MarbleWidget::centerLatitude(), MarbleWidget::zoom() and the setters for the same properties to retrieve and set the coordinates.
| |
| | |
| Level of difficulty: HARD
| |
| | |
| === Reload Maps in the Qt Application ===
| |
| The KDE Marble application has a menu entry to reload maps. The same functionality is available in the context menu on the Marble Widget, but the Qt Marble application is currently missing the "Reload Map" menu entry. Please add it and connect it to the appropriate slot (see MarbleWidgetInputHandler).
| |
| | |
| Level of difficulty: EASY
| |
| | |
| === Add more Plugin Icons ===
| |
| Marble's plugin API lets plugins define an icon which is shown in the menu for activating plugins. Only a few plugins use icons so far however. Please locate appropriate plugin icons (chances are high the oxygen project already has some) and add them. A good start would be the Photos Online Service Plugin.
| |
| | |
| Level of difficulty: EASY
| |
| | |
| === Add support for 23 to marble's Photos Online Service Plugin ===
| |
| Marble's Photos Online Service Plugin currently displays photos downloaded from Flickr. As [http://www.23hq.com 23] also provides flickr API, it should be possible to display images from 23 as well.
| |
| | |
| [https://bugs.kde.org/show_bug.cgi?id=232357 Bugzilla]
| |
| | |
| Level of difficulty: HARD
| |
| | |
| === add fast adding messurment points by ctrl+click ===
| |
| See [https://bugs.kde.org/show_bug.cgi?id=232098 Bug 232098] for more information.
| |
| | |
| Level of difficulty: MEDIUM
| |
