It is possible for an extension to an app (based on ExtensionFoundation) to declare its own extension point and host its own ExtensionFoundation extensions?
Based on the documentation, I am guessing the answer is no, but worth double-checking.
What would be the reason to prevent this? Every ExtensionFoundation extension runs in its own process, and may have need to be extended safely just as its host app does.
Thank you!
Lemme confirm that I’m parsing your question correctly:
- There is a host app.
- Which supports its own extension point.
- You’re building an extension for that extension point.
- And you want to host your own extension point within your extension.
- So that other developers can build their own extensions for your extension.
Did I get that right?
If so, then, yeah, there’s no way to do that.
What would be the reason to prevent this?
I don’t think it’s a question of preventing it, but rather of not enabling it. When you design a plug-in system, or indeed any API, you generally want to constrain things as much as possible, partly for security reasons but mainly because every bit of flexibility you add has to be maintained in the long term.
But if you have a specific use case that needs this, I recommend that you file an enhancement request outlining your requirements. And if you do that, please post your bug number, just for the record.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
