Closed u-an-i closed 3 months ago
@albar965 i was in a desire to implement a streak of ideas.
i was in a desire to implement a streak of ideas.
I fully with you but we've gotta be cautious not to break plugins using the API like https://flightsim.to/file/43086/little-navmap-vr-panel and https://flightsim.to/file/43086/little-navmap-vr-panel .
Alex
Nice. Like the floating ICAO field in the OL map. :slightly_smiling_face:
I fully with you but we've gotta be cautious not to break plugins using the API like https://flightsim.to/file/43086/little-navmap-vr-panel and https://flightsim.to/file/43086/little-navmap-vr-panel .
Alex
Sure! I wasn't aware other web plugins exist. Those 2 are the same link. They appear to be using the wep api. That is not changed ! The web plugin api did change with the previous PR regarding initialisation:
function init (message) { var returned_Value = message.pluginParent.callback(message.pluginParent.callback.TYPE_XXX, stop_Method); ...
instead of function init (callback, version) { var returned_Value = callback(callback.TYPE_XXX, stop_Method); ...
.
This was done to make possible future migration to a different communication technology more straightforward if iframe security changes occur.
…ted and rephrased toolbar API documentation, added example plugin for widget, enhanced example plugin for exclusive plugin to demo attribute overriding, minor ui update to ol-map plugin, let map zoom be default quality initially, afterwards subsequent continued zoom then uses fast map quality, minor ui update re checkbox positioning, automated and auto-safeguarded plugin type transfer, don't reinit map or addon iframe when same content already present