-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Waypoint routes #22
Comments
How would you feel about a complete revamp of navigation requests? I have the following semantics in mind:
As you can see, the fix command creates a barrier in the queue. Commands following the fix command are executed uppon arrival at the fix. I realise this would take a major rewrite of the navigation system. This is why I would like to know wether you are interested in a patch, that implements the described behaviour. |
Is that syntax used in real life? If it is, I'd gladly accept a patch. |
I can't really comment on that since I have never sat in front of an atc terminal but I feel this user interface is most intuitive. Will get to work later today. |
…that fires up a local server (#22)
…n load if one exists (#14) - feature/ATC-12 - adds http-server and `start` script to package.json that fires up a local server (#22) - Adds comments to ArrivalBase for future refactor work - Simplifies airline_get method and abstracts addAirline() into its own method. - Abstracts parse logic into helper methods. Updates instances of for/in loops to use forEach instead. - Changes .createChildren() method names to ._init() - Adds doc blocks to new AirportModel methods. - Abstracts if logic out of AirportModel.parse() - Updates getFix to getFixPosition in AirportModel - Updates references
Multiple fixes in order.
The text was updated successfully, but these errors were encountered: