Extension System

[sr229]

Discussed in #216

^{Originally posted by sr229 May 9, 2021}
This has been requested by the community; however, this is kinda low priority as we focus most on the core components. The way this works is the following:

• Extensions can expose their settings in MainMenu.
• They will be strictly be conformant to the o!f model to properly load. This is considered "bare minimum" for what people requires to make an extension.
• They will be packaged as either a .dll or a .nupkg which the program can "extract" or "compile" into a DLL, something we can do once we have a better idea with how to dynamically load assemblies.

Anyone can propose a better design here since this is a RFC, we appreciate alternative approaches for this.

[LeNitrous]

Move to high priority as it is now considered integral to the core.

[sr229]

Escalating into a new feature.

[sr229]

I believe @adryzz wanted to implement ACLs on this since from our specification, we do require the extensions to list their required capabilities.

For now what we require are the following capabilities implemented:

• scene
• tracking
• io
• net

[sr229]

Here's the formalized/finalized version of our extension architecture, for more details check out GH-256.