https://github.com/ReactiveCocoa/ReactiveCocoaLayout
Reactive layout framework built on top of ReactiveCocoa
https://github.com/ReactiveCocoa/ReactiveCocoaLayout
Last synced: 9 months ago
JSON representation
Reactive layout framework built on top of ReactiveCocoa
- Host: GitHub
- URL: https://github.com/ReactiveCocoa/ReactiveCocoaLayout
- Owner: ReactiveCocoa
- License: mit
- Archived: true
- Created: 2012-12-12T08:24:19.000Z (over 13 years ago)
- Default Branch: master
- Last Pushed: 2015-01-16T21:14:22.000Z (about 11 years ago)
- Last Synced: 2025-07-01T01:47:56.869Z (10 months ago)
- Language: Objective-C
- Size: 1.93 MB
- Stars: 664
- Watchers: 46
- Forks: 57
- Open Issues: 12
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.md
Awesome Lists containing this project
- awesome-iOS-Library-Curator - ReactiveCocoaLayout
README
# ReactiveCocoaLayout
ReactiveCocoaLayout is a framework for describing Cocoa and Cocoa Touch layouts
in a reactive way, based on
[ReactiveCocoa](https://github.com/ReactiveCocoa/ReactiveCocoa).
This framework is very much a work in progress at the moment, and should be
considered **alpha quality**. Breaking changes may happen often during this
time.
## Why Not Use Auto Layout?
RCL intends to offer the following advantages over Auto Layout:
* **Explicit and linear layout.** Reactive layout proceeds in a linear fashion,
making it easier to understand and debug the steps it takes along the way.
* **Top-down layout.** A view's layout doesn't interact with its superview's
layout unless the former's size or frame is explicitly incorporated in the
latter's layout chain, creating a unidirectional relationship that leads to
better encapsulation (no global priorities!) and less complexity.
Bidirectional relationships are still possible, but must be made explicit.
* **Conditional layouts at runtime.** RCL is built on the full power
of [ReactiveCocoa](https://github.com/ReactiveCocoa/ReactiveCocoa), and signals can
be composed to dynamically disable and re-enable entire layout chains (like
when you want to hide and show views) without actually modifying them.
* **Implicit animations.** To animate the setting of a view's frame, simply add
an animation method into the signal chain. No need to explicitly animate
constants anywhere.
* **Incremental use.** RCL can be used internally in views without any
implementation details leaking out. Callers using Auto Layout or struts and
springs can incorporate reactive views without knowing or caring how they
perform layout internally. No UI-wide slowdowns or behavior changes just from
using RCL!
* **Extensibility.** RCL is made up of many independent bits of functionality
unified into a framework. It's easy to extend it with your own functionality
if you want it to behave differently.
* **Not a black box.** Unlike AppKit and UIKit, RCL is an open source project,
so you can crack open any particular bit and see why it behaves the way it
does.
## Getting Started
To start building the framework, clone this repository and then run `script/bootstrap`.
This will automatically pull down any dependencies. Then, simply open
`ReactiveCocoaLayout.xcworkspace` (note: not the `.xcodeproj`) and build.
To use ReactiveCocoaLayout in your project, you will need to include the `ReactiveCocoaLayout.xcodeproj` (note: not the `.xcworkspace`) file in your project, and link
[ReactiveCocoa](https://github.com/ReactiveCocoa/ReactiveCocoa) and
[Archimedes](https://github.com/github/Archimedes) into your application target.
## License
ReactiveCocoaLayout is released under the MIT license. See
[LICENSE.md](https://github.com/ReactiveCocoa/ReactiveCocoaLayout/blob/master/LICENSE.md).