great job, and I really like the fact that you are reusing existing stuff and extending the tutorials subsystem - that approach is so much better than the usual method of coming up with stuff from scratch and then complaining that FG is lacking certain features. If we could extend the tutorial system to provide all these things as building blocks, people could come up with arbitrary adventures and missions - which is a really long-standing and popular feature request, and we have enough existing projects that could benefit from something like this.
From a coding point of view, I would suggest to generalize the aircraft-specific stuff - so that aircraft specific parameters are looked up from an XML checklist:
http://wiki.flightgear.org/Aircraft_ChecklistsThose are just XML files, and if anything is missing, it can be added within seconds. The main point being, that this would allow us to support aircraft-agnostic tutorials (missions/adventures), where people could select a different aircraft - for example, the bo105 or the R22:
http://wiki.flightgear.org/Talk:Tutoria ... gnostic.29From a "missing design" point of view, I can help you use the Nasal/Canvas MapStructure framework to come up with a GUI dialog where you can place "hoops" (targets) on a map, and then edit those to refine altitude/orientation/position etc. Most of the required features are already supported - We really only need to add a new controller that responds to mouse events.
That should allow people to easily create their own missions (tutorials) - as a workaround, we could also use the route manager and flightplan() APIs to place hoops for each waypoint
I'll send a heads-up to Thorsten and DFaber so that they're aware of your work here - because this is clearly overlapping with their most recent effort, and manually coming up with an "event management structure" without using Stuart's existing work simply doesn't scale as well.