Convert ChartFox interfacing to v2 API. #204
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change modifies the ChartFox interfacing to use the latest (v2) API for chart retrieval.
The authentication protocols have been updated, so that each Avitab user is required to have a ChartFox login and use their account in order to obtain an authentication token that allows chart retrieval.
The new API works similarly to the older API. Some codings have been modified, and georefs are now available (not yet used).
Some general and minor refactoring updates are also included in this change, including some renaming of Navigraph-related variables.
To enable the new ChartFox interfacing in the build of Avitab it is necessary to define the environment variable CHARTFOX_CLIENTID with the value of a recognised ChartFox client ID before configuring with cmake. The client ID serves to identify Avitab as the requesting application. The user will still be required to authenticate with ChartFox before any charts may be retrieved.
This change resolves issues #149 and #196.