/explore
|
You are here 
|
rx-marin.com | ||
| | | | |
swiftrocks.com
The choice between using Storyboards and writing views programmatically is very subjetive. Having dealt with both in the past, I personally vouch for writing projects entirely through view code as it allows multiple people to work in the same class without nasty conflicts, and easier code reviews. |
|
| | | | | ||
| | | | |
www.neilmacy.co.uk
A better way to deal with UITableViewCells. |
|
| | | | | ||
| | | | |
sintraworks.github.io
Recently I started studying Ray Wenderlich's tutorial book RxSwift. Early on, the book suggests using Rx as an alternative to delegates and their associated protocols. I though, great, but, for the task at hand, that's a rather heavy handed solution. (Yes, I know it is just an example designed to teach me the basics.) So I tried to imagine how I could achieve something similar to the functionality they built for their initial examples, without the overhead of importing a big library like RxSwift. |
|
| | | | | ||
| | | | |
www.dabblingbadger.com
SwiftUI, Apple's declarative framework for rapid user interface development, is an awesome alternative to UIKit, but still missing some key features. Here, I will discuss a few of the common issues surrounding keyboard dismissal and provide two solutions and workarounds that I have found after an embarrassing amount of googling and combing of StackOverflow. |
|
| | | |||
