Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Clone this wiki locally
Strange: the IoC framework for
Strange attractors create predictable patterns, often in chaotic systems.
Strange is a super-lightweight and highly extensible Inversion-of-Control (IoC) framework, written specifically for C# and Unity. We've validated Strange on web, standalone, and iOS. We're not currently developing for Android, but we're fairly certain it'll run just fine there, too (er, please let us know!!!).
- StrangeIoC documentation
- The Big, Strange How-To
- Do you use RobotLegs? You're in luck! This Strange page is for you!
- Feature requests/Bug reports
It contains the following features, most of which are optional:
- A core binding framework that pretty much lets you bind one or more of anything to one or more of anything else.
- Dependency Injection
- Map as singleton, value or factory (get a new instance each time you need one)
- Name injections
- Perform constructor or setter injection
- Tag your preferred constructor
- Tag a method to fire after construction
- Inject into MonoBehaviours
- Bind polymorphically (bind any or all of your interfaces to a single concrete class)
- Reflection binding dramatically reduces overhead of employing reflectivity
- A shared event bus
- Dispatch events to any point in your application
- Map local event bus for local communication
- Map events to Command or Sequence classes to separate business logic
- MonoBehaviour mediation
- Facilitate separation of a view from the application using it
- Keep Unity-specific code isolated from the rest of the app
- Optional MVCS (Model/View/Controller/Service) structure
- Multiple contexts
- Allow subcomponents (separate Scenes) to function on their own, or in the context of larger apps.
- Allow communication between contexts.
- Donâ€™t see what you need? The core binding framework is simple to extend. Build new Binders like:
- A different type of dispatcher, like AS3-Signals
- An entity framework
- A multi-loader
In addition to organizing your project into a sensible structure, Strange offers the following benefits:
- Designed to play well with Unity3D. Also designed to play well without it.
- Separate UnityEngine code from the rest of your app.
- Improves portability
- Improves unit testability
- A common event bus makes information flow easy and highly decoupled. (Note: Unity's SendMessage method does this, of course, but it's dangerous as all get-out. I may write a whole article on just this topic at some point.)
- The extensible binder really is amazing (a friend used to tell me "it's good to like your own cookin'"). The number of things you can accomplish with the tiny core framework would justify Strange all on its own.
- Multiple contexts allow you to â€œbootstrapâ€ subcomponents so they operate fine either on their own or as an integrated part. This can hugely speed up your development process and allow developers to work in isolation, then integrate in later stages of development.
- Get rid of platform-specific #IF...#ELSE constructs in your code. IoC allows you to write whole concrete implementations correctly, then bind the ones you want to use at compile time or at run time. (As with other forms of binding, #IF...#ELSE clauses can be isolated into a single class and away from the rest of your code.)
It is hard to adequately credit the creators of the open source Actionscript framework RobotLegs for their influence on the creation of StrangeIoC. While Strange is not a port of RobotLegs, the ensigns of that library are copiously reflected throughout this one. For their great service to my professional development, I offer that team my sincerest thanks. And a donut. Seriously, if youâ€™re ever in town, let me buy you a donut.
I also need to thank and congratulate the folks at ThirdMotion who inexplicably gave me time to build Strange and license to open source it.
/**********************************************/ Copyright 2013 ThirdMotion, Inc.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.