Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation updates #177

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
The Stage Crawler Extension scans and handles all views in the containers or contextview after context initialization.
This enables us to handle the views that might already be on the stage before initialization which would otherwise not be processed (or mediated).

It is reliant on either a IViewManager or a ContextView upon initializtion.
It is reliant on either a IViewManager or a ContextView upon initialization.

## How to Install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@

The Stage Observer Extension adds a single instance. Which listens for everything that is Event.ADDED_TO_STAGE on all root containers in the Container Registry, and then processes the view for you.

It will listen for removal and new root containers and adjust it's listeners appropriatley.
It will listen for removal and new root containers and adjust it's listeners appropriately.

The Stage Observer has a static instance stored in the extension but will destory/cleanup when all context's have been destroyed.
The Stage Observer has a static instance stored in the extension but will destroy/cleanup when all context's have been destroyed.

## How to Install

Expand Down
8 changes: 4 additions & 4 deletions src/robotlegs/bender/extensions/viewProcessorMap/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Overview

The view processor map provides automagic processing of mapped views landing on the stage and manual processing where preferred.
The view processor map provides automatic processing of mapped views landing on the stage and manual processing where preferred.

## Extension Installation

Expand All @@ -28,13 +28,13 @@ You can create your own processor, for example to do property injection without
You map either a specific type or a TypeMatcher to the class or instance of processor you want to be used.

```as3
viewProcessorMap.map(SomeType).toProcessor(FastInjector);
viewProcessorMap.map(SomeType).toProcess(FastInjector);

viewProcessorMap.mapMatcher(new TypeMatcher().anyOf(ISpaceShip, IRocket)).toProcessor(SpacecraftSkinner);
viewProcessorMap.mapMatcher(new TypeMatcher().anyOf(ISpaceShip, IRocket)).toProcess(SpacecraftSkinner);

// you can also use an instance as the processor, in this case, to avoid inspection when doing property injection

viewProcessorMap.map(SomeType).toProcessor( new FastPropertyInjector( { userID:UserID, animationSettings:AnimationSettings } ) );
viewProcessorMap.map(SomeType).toProcess( new FastPropertyInjector( { userID:UserID, animationSettings:AnimationSettings } ) );
```

#### Shortcut method for the most common case: injection by inspection
Expand Down