So that you can type

dispatch(event)

instead of

eventDispatcher.dispatchEvent(event);

So that you can type dispatch(event) instead of eventDispatcher.dispatchEvent(event);

No, not really. The context just holds on to the RobotLegs apparatus – it’s not a “holder” or a “kitchen sink” object. Why it’s called a context is another discussion.

“Avoid reaching into one object, to get another, etc. Do not look for the object of interest by walking the object graph (which needlessly makes us intimate with all of the intermediary objects. The chain does not need to be deep. If you count more than one period in the chain, you’re looking right at an example of this flaw.”

If you were to look into the framework code, or the code of an application that uses the framework properly, you wouldn’t find any examples of this. Single dots all the way yo!

“Inject directly the object(s) that you need, rather than walking around and finding them.”

This is exactly what RobotLegs does, and what it enables for applications that use it.

RobotLegs is all about making the right thing easy to do. The inspiration for building it came directly from reading Miško Hevery’s posts.

So, perhaps the word “context” was a really bad choice!

Cheers,

No, not really. The context just holds on to the RobotLegs apparatus – it’s not a “holder” or a “kitchen sink” object. Why it’s called a context is another discussion.

“Avoid reaching into one object, to get another, etc. Do not look for the object of interest by walking the object graph (which needlessly makes us intimate with all of the intermediary objects. The chain does not need to be deep. If you count more than one period in the chain, you’re looking right at an example of this flaw.”

If you were to look into the framework code, or the code of an application that uses the framework properly, you wouldn’t find any examples of this. Single dots all the way yo!

“Inject directly the object(s) that you need, rather than walking around and finding them.”

This is exactly what RobotLegs does, and what it enables for applications that use it.

RobotLegs is all about making the right thing easy to do. The inspiration for building it came directly from reading Miško Hevery’s posts.

So, perhaps the word “context” was a really bad choice!

Cheers,