Add inherent DI support

[glennblock]

Being that this is a new stack, it would be great is if was designed with IoC in mind from the get go.

This means ideally then runtime and all its components can be constructed via a container. Custom user components like controls could have dependencies injected as well, all via ctor injection.

I would recommend looking to Fubu MVC and also ASP.NET MVC/Web API for inspiration.

[grokys]

Hi Glenn,

I would be interested to hear your thoughts on this. I agree that it's best to do try to get this right now while things are still fresh.

Could you give examples of some use-cases you have in mind?

[nerdshark]

These are just a few really general examples, but making Perspex DI-friendly would make it really easy to build composable application shells, such as:

• Gemini
• Wide
• Orchestra

Not only would having DI support baked in (whether through a specific framework, or via an interface implemented by the user) make it easier to build composable applications, it would make it easier to build applications that gain reliability by isolating parts of the application in their own process, like Chrome (and, soon, Firefox) do. Baktun Shell is an example of this in .NET.

[grokys]

Thanks for your input @nerdshark. Is there anything in particular that you think is missing today, or could be implemented today? I'd like to hear some more concrete proposals surrounding this.

[glennblock]

I will try to find some cycles to give you an illustration of what I mean.
On Tue, Aug 2, 2016 at 5:20 PM Steven Kirk notifications@github.com wrote:

Closed #17 #17.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#17 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAInRLJFvafc5_2aIb24kIFgfEdGb3nwks5qb97qgaJpZM4DNT5Y
.