Line 56: | Line 56: | ||
===Displaying Debug Info on request=== | ===Displaying Debug Info on request=== | ||
− | + | <b>Harshit</b> is working on this JJ already | |
* Have a look at: | * Have a look at: | ||
Line 95: | Line 95: | ||
===Adding Bookmarks=== | ===Adding Bookmarks=== | ||
− | Gaurav is already working on this one. | + | <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. | * 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 | Level of difficulty: HARD |
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.
We want our Marble source code to look good. The documentation should be concise and helpful 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 regularly:
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 marble-devel@kde.org.
This section deals with junior jobs that deal with Marble's data structure:
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.
http://code.google.com/apis/kml/documentation/kmlreference.html#lookat
The earth at night map still shows some shading, when sun shading is enabled.
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.
There is a Marble version that only depends on Qt. The KDE version of Marble is always a bit ahead of the Marble Qt version as KDE is a pretty powerful framework. Still not everybody can and wants to use KDE libraries. And especially for our Windows and Mac packages the Marble Qt version is a lot smaller. So help us to bring the Marble Qt version on par with the Marble KDE version in terms of features. You need to look into marble/src/qtmain.cpp and marble/src/QtMainWindow.{cpp,h}
Harshit is working on this JJ already
http://doc.trolltech.com/4.5/qtglobal.html#qInstallMsgHandler
It would be nice if Marble would switch off all debug info by default. Only when passing the command line parameter --debug-info it should display the debug text.
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/MEDIUM
In marble/src/lib/MarbleControlBox.cpp, line 107-109 there are the lines:
d->uiWidget.celestialBodyLabel->setVisible( false ); d->uiWidget.celestialBodyComboBox->setVisible( false );
comment them out on your local checkout (but don't commit this change until you have finished the implementation of this feature). After recompiling you should see a "Celestial Body" combo box above the Map Theme selection list view.
Level of difficulty: HARD
Gaurav is already working on this one.
Level of difficulty: HARD