Inversion of control can be described as "an abstract principle describing an aspect of some software architecture designs in which the flow of control of a system is inverted in comparison to procedural programming." [1] IoC is a pattern that naturally results from the proper organisation of dependencies in a body of code. It typically results in delegation of power over instantiation and wiring of dependencies to a framework, rather than writing manual code to sequentially achieve the task in a particular situation. This page provides resources to help you understand why and how the Infusion Framework uses Inversion of Control.
Labels:
None
Page:
Why Inversion of Control?
Page:
How to Use Infusion IoC
Page:
Subcomponent Declaration
Page:
Contexts
Page:
Demands Specifications
Page:
Demand Resolution
Page:
IoC Pipeline
Page:
Invokers
Page:
Expansion of Default Component Options
Page:
Event injection and boiling
Page:
Controlling The Timing of Subcomponent Creation
Page:
IoCSS