tei/MapLibreParticleLab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: typos (#4202)

Browse Source 
Co-authored-by: Bart Louwers <bart@emeel.net>
This commit is contained in:
Mike Taves
2026-07-14 03:08:27 +12:00
committed by GitHub
parent 9d53ac53a6
commit fba652eb72
76 changed files with 100 additions and 97 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
design-proposals/2025-05-08-plugin-layers.md
View File

@@ -6,7 +6,7 @@ This project is to add the ability to "register" additional layer types at runti
## Proposed Change
For the initial implemention, the following functionality is proposed:
For the initial implementation, the following functionality is proposed:
* At the platform level, be able to register a plug-in layer that is then parseable by the style parser
* The plug-in layer will be limited to simple rendering (via handing off the rendering context to the plug-in layer) and will not include the ability to define drawables/etc
@@ -18,7 +18,7 @@ Future features:
* Placeholder for ideas that could be implemented in the future
## Example IOS Utilization
An example implemention is shown in the PR: https://github.com/maplibre/maplibre-native/pull/3430
An example implementation is shown in the PR: https://github.com/maplibre/maplibre-native/pull/3430
The platform/darwin/app/PluginLayerExampleMetalRendering.h/mm class shows how the layer manages it's own rendering and how properties from the style are passed to it. In platform/ios/app/MBXViewController.mm there's a single line where the plug-in layer class is registered with the map view
```
[self.mapView addPluginLayerType:[PluginLayerExampleMetalRendering class]];