Adds plugin protocol handlers #3958
Open
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.
Protocol Handler
This adds support similar to plugin-layers and style filters by exposing a data loading paradigm via a plug-in class and lambda implementation. This does not create or implement a way to chain FileSources together.
To add a custom handler, descend from MLNPluginProtocolHandler and implement the two methods to let the system know if this handler can handle the request and then return data when the system asks for it. There's a sample implementation which just loads the local test style file when the url starts with "pluginProtocol"
Like other plug in items, these handlers are added to the map view at runtime with a single call.
Supported on Android as well. Just descend from the PluginProtocolHandler class and implement the two methods, one for if this handler can support the request and returning the actual data for the request.
and register the plugin using the mapview