Developed by Daniel Marth during Google Summer of Code 2011. User interface ideas (under development): On startup a "home screen" is shown that lines up a couple of possible activities. Each activity is represented by its name and an icon, aligned in a grid. Selecting any activity brings the user to the main screen. The main screen adjusts itself to the chosen activity and provides a way to go back to the home screen and related activities. Most activities display a map (MarbleWidget) as the main widget, but that's not always the case (e.g. during configuration).
Planned activities are as follows:
Marble Touch for MeeGo 1.3, to be released with KDE 4.8. Supported activities are
The following features will be missing in the very first release 1.3.0:
Releases will be aligned with the KDE release schedule. Minor releases will be feature releases, however. The missing features from above will be added gradually in these releases.
|Tile creation crash||Crash||1.3.0||Possibly related to a model change/reset killing the listview delegate item that triggered the change|
|Use MyDocs||Packaging||1.3.0||8 GB space in /home/user/MyDocs vs 2 GB in /home/user. Use fremantle patch.|
|Monav dependency||Packaging||1.3.0||Small and reliable, no point not to have it installed|
|Use Harmattan colors||Polishing||1.3.0||Replace: Blue and gray in Navigation activity, lightsteelblue in hightlights|
|quick Online toggle icon||Polishing||1.3.x||Where useful, e.g. Routing activity. See Navigation activity|
|Consistent margins and spacing||Polishing||1.3.x||Bad example e.g. map theme selection in Preferences|
|Add missing activity icons||Polishing||1.3.x||Routing, Tracking and Navigation still use generic icons|
|QML Tile Creation Progress Item||Polishing||1.3.x||QWidget version instantiated by MarbleMap, looks strange and is portrait only|
|Improve whitespace usage in Search/Routing||Polishing||1.3.x||Use more space for the map whenever possible (e.g. no search result, no turn directions)|
|Remove via points||Feature||1.3.x||Currently deactivated as triggering it from the ViaPointEditor delegate affects the delegate itself (deletes it) which results in a segfault for some reason|