ArduPilot / MissionPlanner

Mission Planner Ground Control Station for ArduPilot (c# .net)
http://ardupilot.org/planner/
GNU General Public License v3.0
1.75k stars 2.38k forks source link

Mission Planner "Makeover" #1748

Open Naterater opened 6 years ago

Naterater commented 6 years ago

Issue details

According to ~80% the community (of 103 users following ardupilot.org on facebook), Mission Planner could use a makeover. To begin, MP is packed with a wonderful amount of features. Maybe those features have outgrown the current organization of mission planner. While there are many lists of "feature requests" here already, I don't think this is why people think MP needs a makeover. To clarify, this is not a request for addition or reduction in features.

I believe the two most useful things for a mission planner makeover would be

I think this is the right first step to making mission planner more user-friendly and adaptable to users of all levels. It may or may not seem like a big change, but most users are very familiar with the "ribbon" layout and managing windows. By placing almost all commands and options at the top in a ribbon that can be hidden, the entire lower screen can fit more data applicable to the user. (This would effectively move the buttons under the HUD to the top ribbon)

I envision the top ribbon containing ~9 tabs

Within each ribbon tab, there will be 4 main types of buttons.

Since almost everything would be located in the top ribbon that is collapsible, there is more room for displaying whatever the user wants during flight monitoring. The command buttons could be selected while still viewing the "quick data grid." All features would be in the ribbon and not hidden behind left clicks or double-clicks.

I understand this is not a paid endeavor, but I really think the community needs this. This is the "face" of ardupilot.

jaimemachuca commented 6 years ago

This research on the UX/UI by Intel is very interesting and valuable.

http://juca.work/work/drones/

And the GitHub Repo:

https://github.com/Dronecode/UX-Design

Naterater commented 5 years ago

It doesn't appear to me that there will be much effort on these big-picture items. Here is a list of smaller, simpler tasks that could make a difference.

2027

2028

2032

2038

2050

2013

2026

2030

2031

1860

2029

Maybe after these are addressed/discussed, larger architectural changes could be made.