Komponents is a Swift framework for building component-oriented interfaces.
Because it's unfair to need javascript to enjoy Components ! 😎
| Komponents | |
|---|---|
| 🔶 | Pure Swift (no JS, no XML) |
| 🎨 | Declarative Api |
| 💉 | Hot Reload with injectionForXcode |
| ⚙️ | Diff algorithm running in background |
| 🏗 | Can be used Incrementally in your App |
| 🕸 | No external Dependencies |
Building a Loading screen with Hot reload 🎩
class LoadingVC: UIViewController, StatelessComponent {
override func loadView() { loadComponent() }
func render() -> Tree {
return
View([
HorizontalStack(layout: .center, [
Label("Loading..."), ActivityIndicatorView(.gray)
])
])
}
}This is all we need to render a loading view !
New to components? Fear not! Facebook's React guide is a gold mine of information to get you started :)
The easiest way to get started and feel the power of Komponents is to take a look at the example project KomponentsExample.xcodeproj and play around !
For an even better experience, we strongly recommend enabling Hot reload
You can learn how, like React, Komponents tries to be smart about what it rerenders when the state changes in Patching section.
You can find more detailed information and guides in the Wiki
Komponents can be installed Manually, via Carthage, Cocoapods or Swift Package Manager.
Detailed installation steps in the wiki here
YannickDot,
S4cha, YOU ?!
We'd love to hear what you think so don't hesitate to reach out through an issue or via twitter
@sachadso
Komponents is released under the MIT license. See LICENSE for details.
Facebook's React, ComponentKit, Preact, Vue.js AlexDrone's render, Angular...
We're not the first to tackle the great endeavor of swift components and here are some other very cool projects :
Please be aware that this is still very experimental 🔬.
The actual api can and will change.
This is not battle-tested and we advise you against using this in Appstore Apps (for now)
Applying styles directly on the UIKit elements was super handy in v0.1 but came with major strings attached. Indeed, the styles blocks in the nodes could only be called on the main thread, because UIKit is meant to be accessed from the UI Thread (for the most part).
Also, in order to compare styles, we needed to create a duplicate UIKit element (heavy) and look for differences on it.
That's where Props come in!
The idea is to have a Props layer, aka a structure that defines an element's style, that is Equatable.
Being equatable, it becomes trivial to compare two buttons styles.
For instance, you can just write :
let styleIsTheSame = (button.props == newButton.props)
Being Value-typed, it is also safe to process the diff in background !
Could we get all this goodness for free? Of course not, welcome to engineering.
The major drawback is that we have to bridge every UIKit element property to its corresponding Props struct.
However the properties supported can only get better with time classic escape hatch through refs will always be accessible to access UIkit elements if a property is not yet supported.
This is worth it!
The coming version is switching from Autolayout (and Stevia) to a declarative layout.
The new layout system is based on a super simple Layout struct, that, combined with classic StackViews enables 99.9% of layout cases.
It is a value type, meaning it will be thread safe and thus enable comparison in a background thread :)
With elements, styling, and layout purely declarative, Value-Type and Equatable, we can now safely put all the heavy duty stuff off to a background thread !!!
In v0.2, the diffing algorithm (also known as reconciliation) will run on the virtual DOM, on a background thread and only schedule UI changes on the UI thread. 🎉
Like the project? Offer coffee or support us with a monthly donation and help us continue our activities :)
Become a sponsor and get your logo on our README on Github with a link to your site :)
