frontend: mission-planning: interface improvement suggestions

[ES-Alexander]

Current behaviour

Mission planning is currently

1. slightly awkward to access
   • requires 3 clicks to get to it, and another 3 to get back to flight/operation mode
2. inconsistent with the rest of the application
3. unwieldy to manage surveys and large numbers of mission waypoints
4. incapable of detecting mission changes on a vehicle
5. hard to use for missions fetched from vehicles

Expected or desired behaviour

• Include a button on every map widget as a shortcut to jump to mission planning mode
• Refactor the mission planning mode to be more like edit mode, in style and behaviour
  
  • Have a map in the main view area, with a sidebar listing components, and a bottom bar for adding and configuring components
    • frontend: editor: make configuration windows and mechanisms consistent #1540 has various consistency suggestions
  • Missions are like Profiles
    • The user can store multiple pre-defined missions and switch between them, before deciding which one to upload to the autopilot
    • A map widget can load a pre-defined mission like a video widget can choose a video source
  • In future, a mission can be distributed between multiple vehicles as a set of sub-missions, which are like Views
    • This would include a visibility toggle, to help focus on specific sub-missions within the whole
  • Surveys are like mini-widget bar widgets, and other widget sequences are like the header and footer bars
    • Surveys should be hoverable for focus, movable in the main view area, draggable to reorder in the list, and configurable to set the size/shape and waypoint generation properties
    • Ideally survey polygon edges should be controllable with dimensions, like defining a shape using CAD
      • It should at least be possible to manually specify the locations of each polygon point
  • Waypoints are like mini-widgets
    • They should be hoverable for focus, reorderable, movable, and configurable
• Add a setting in the Mission Configuration section to limit the maximum number of waypoints, to avoid users accidentally overloading their RAM by generating overly fine-grained / large surveys
• Monitor MISSION_CURRENT MAVLink messages to determine when the mission has changed without Cockpit being the cause
  • Requires adding mission_id field support in ArduPilot (and relevant other firmwares)
• Include higher-level Cockpit mission definition components/metadata in the missions sent to the autopilot
  • May require including a metadata file using MAVFTP, and/or making use of the MAV_CMD_SPATIAL_USER_* / MAV_CMD_WAYPOINT_USER_* / MAV_CMD_USER_* commands
  • Some internal discussion

Prerequisites

• I have checked to make sure that a similar request has not already been filed or fixed.