Marble/RoutingRoadmap: Difference between revisions

From KDE TechBase
(Page moved to community wiki)
 
(53 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== KDE 4.5 (Marble 0.10) ==
{{ Moved To Community }}
* Online-Routing using OpenRouteService
* GPX export
 
== KDE 4.6 (Marble 0.11) ==
This is an elaborated version of the [http://techbase.kde.org/Schedules/KDE4/4.6_Feature_Plan#kdeedu 4.6 Feature Plan]. It only lists features to be done / in progress. Finished ones are removed.
 
=== GPX/KML Import ===
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Marble|Check parsing of route related gpx and kml elements|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Connect to FileManager and import routes, if any|[email protected]|Dennis Nienhüser}}
|}
 
=== Route Printing ===
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Marble|Extend current print dialog with Marble option page for configuration|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Optional inclusion of legend and routing instructions|[email protected]|Dennis Nienhüser}}
|}
 
=== Route state save ===
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Marble|Check KML export of route elements|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Auto-save route to kml file at appropriate times|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Auto-load kml route at startup, if any|[email protected]|Dennis Nienhüser}}
|}
 
=== Worldwide and Offline Routing ===
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Marble|Include gosmore-instructions in Marble|[email protected]|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Also parse routino output|[email protected]|Dennis Nienhüser}}
|}
 
=== Routing API ===
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Marble|Rename RouteSkeleton to RouteRequest|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Routing API review|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Decouple RoutingWidget, RoutingLayer and RoutingManager|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Export RoutingManager and RouteRequest headers|[email protected]|Dennis Nienhüser}}
|}
 
=== Turn-by-turn Navigation ===
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Marble|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)||}}
{{FeatureTodo|Marble|Swap z-order of current position indicator and route waypoints||}}
{{FeatureTodo|Marble|Make current position indicator better visible (e.g. include half-transparent indicating position dop)||}}
{{FeatureTodo|Marble|Selection of autzoom/recenter mode should be possible whenever a position provider is selected, not only when a position is known. Otherwise the user has to wait for the GPS signal to come in, which can take long||}}
|}
 
=== Maemo UI ===
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Marble|Optimize "Download Region" dialog for little space||}}
{{FeatureTodo|Marble|Fix visual glitches in routing pluing (icon transparency, black frame of progress bar, font size||}}
|}
 
=== General Polishing ===
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Marble|Reset stored position in via point input widgets when user starts editing it|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Use geodatacoordinates string as via input widget text only when reverse geocoding fails|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Custom, i18ned display of (nominatim) reverse geocoding results also respecting the altitude (zoom)|[email protected]|Dennis Nienhüser}}
{{FeatureTodo|Marble|Minimize the total number of MarbleRunnerManager instances|[email protected]|Dennis Nienhüser}}
|}
 
== Undecided ==
* Tour height profiles (using SRTM data)
* Multiple routes (one active route)

Latest revision as of 05:01, 26 October 2016

This page is now on the community wiki.