Memory management is a pretty important issue when talking about any kind of system. You can’t pretend that your resources are unlimited, and give them out no matter what. When working with ReactiveSwift it’s really easy to fall into the pit of wasted resources if you don’t follow simple rules.
The first Cocoapod created
Today, we will take a closer look at Rex - ReactiveCocoa extensions. I find Rex pretty helpful when working with ReactiveCocoa, especially creating UI bindings.
CocoaAction is a wrapper around Action type that is available in ReactiveCocoa. (Here you can read more about Action). We use CocoaAction to bind our Actions to GUI controls. Let’s see a quick example of how it works.
Today I’ll tell you about an Action type that is available in ReactiveCocoa 4.
Understanding signal events in ReactiveCocoa is a must. We can’t effectively use signals and signal producers if we don’t know what will happen after certain event is received. We distinguish two kinds of events that you can send through signals - terminating and non-terminating. There are three kinds of terminating events: Failed, Interrupted, Completed, and one non-terminating - Next.
Using open source code in projects is a common thing. I do it. Most of us do. But what is “open source” by default? Well, I’ve heard about this for the first time at MCE Conf 2016 - “Open by default” panel. It’s an idea to make software open by default and close it only if needed. There are many reasons to close it of course, but sometimes we do it unnecessarily.
Hi! In my first post I want to share with you some cool tip which I watched in ‘Swift in Practice - Apple WWDC 2015’ Alex Migicovsky presentation about using UIImages in Swift project.
Configuring Android device to connect to the web proxy running on development build machine is tedious. You have to make the same steps over and over again on every device you want to debug HTTP traffic.<br/ > It goes like this:
I wrote simple helper which allow loading specific certificate to SSLContext. You can use it to support HTTPS connections which rely on a untrusted certificate. By untrusted certificate, I mean this one which server is certified but system denies it (doesn’t trust it) for some reason. I found it very useful to load particular certificate dynamically.