|
|
| Line 1: |
Line 1: |
| == Proposal == | | == Proposal == |
| [http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/kde/t127230760808 Marble To Go (Navigation Mode) for KDE] by Siddharth Srivastava | | [http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/kde/t127230760808 Marble To Go (Navigation Mode) for KDE] by Siddharth Srivastava |
|
| |
| == ToDo List / Optional Stuff ==
| |
|
| |
| === Center and Zoom Adjustments ===
| |
| * Recentering when needed could use a future (predicted) position for recentering. The prediction can be based either on the current speed and direction or on the expected route waypoint at a future point (e.g. in 20 seconds). This prolongs the time the map can stand still.
| |
|
| |
| === Display of Instructions ===
| |
| * Distance units should be localized (miles vs. km) and adjusted (< 1000m: X m, >= 1000m: X.Y km)
| |
| * When calculating the remaining distance, the distance between the current gps position and the position of the next waypoint on the route should be included. Otherwise the remaining distance seems to stall for some time when not crossing a route waypoint, although the gps position changes
| |
| * Shrink the routing float item a bit and display the next instruction text and the distance to it per default, not the distance to the end of the route. "Routing Information" can probably go away.
| |
| * The drawAnnotation() function used to display instructions on top of the map cuts off instruction text and sometimes hides the track / current position indicator
| |
|
| |
| === Offline Use ===
| |
| * A rough estimation of the expected download size (based only on the number of tiles to download) should be displayed
| |
Revision as of 14:35, 22 August 2010
