Update Framework Overview for RAC 5.0 #109
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andersio
requested changes
Nov 23, 2016
Documentation/FrameworkOverview.md
Outdated
| ## Signals | ||
|
|
||
| A **signal**, represented by the [`Signal`][Signal] type, is any series of [events](#events) | ||
| A **signal**, represented by the [`SignalProtocol`][Signal] protocol, is any series of [events](#events) |
Member
There was a problem hiding this comment.
This should not be changed. We use SignalProtocol only to constraint the extensions, since we can't use same-type requirements in concrete type extensions yet. A signal is always the concrete type Signal.
Documentation/FrameworkOverview.md
Outdated
| ## Signal Producers | ||
|
|
||
| A **signal producer**, represented by the [`SignalProducer`][SignalProducer] type, creates | ||
| A **signal producer**, represented by the [`SignalProducerProtocol`][SignalProducer] protocol, creates |
Documentation/FrameworkOverview.md
Outdated
| An **observer** is anything that is waiting or capable of waiting for [events](#events) | ||
| from a [signal](#signals). Within RAC, an observer is represented as | ||
| an [`Observer`][Observer] that accepts [`Event`][Event] values. | ||
| from a [signal](#signals). Within RAC, an observer is represented by the [`ObserverProtocol`][Observer]. |
Documentation/FrameworkOverview.md
Outdated
| ## Actions | ||
|
|
||
| An **action**, represented by the [`Action`][Action] type, will do some work when | ||
| An **action**, represented by the [`ActionProtocol`][Action] protocol, will do some work when |
iv-mexx
force-pushed
the
feature/frameworkOverview
branch
from
d0b1de4 to
78364e5
Compare
Contributor
Author
|
@andersio So, for |
Member
|
Hmm, probably not |
iv-mexx
force-pushed
the
feature/frameworkOverview
branch
from
78364e5 to
b192a17
Compare
Contributor
Author
|
Alright, I've change that for |
andersio
requested changes
Nov 23, 2016
|
|
||
| ## Properties | ||
|
|
||
| A **property**, represented by the [`PropertyProtocol`][Property], |
Member
There was a problem hiding this comment.
Line 132 has a broken link. May you help fix it please?
Contributor
Author
There was a problem hiding this comment.
Oh my, missed that in #101, but fixed it now 👍
iv-mexx
force-pushed
the
feature/frameworkOverview
branch
from
bb5ab22 to
520366c
Compare
mdiep
approved these changes
Nov 23, 2016
andersio
approved these changes
Nov 23, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the title says.
Most is about the renaming of the events (
Next->value, lowercases) and the use of the Protocols rather than the types. Furthermore,SignalProducer.bufferis now gone.Similar to the part about
DynamicPropertywhich was deleted in #101 because its now in ReactiveCocoa, I've also deleted the part aboutCocoaAction.