simonbs

SwiftUIHostingConfiguration

In iOS 16, Apple added UIHostingConfiguration, making it straightforward to use a SwiftUI view in instances of UICollectionViewCell and UITableViewCell. This gist shows how UIHostingConfiguration can be backported to iOS 14 by implementing a type that conforms to UIContentConfiguration.

Starting from iOS 16, we can use SwiftUI views in an instance of UICollectionView or UITableViewCell like this:

cell.contentConfiguration = UIHostingConfiguration {
    ExampleCellContentView(color: Color(item.color), text: item.text)
}

marcpalmer

//
//  FrameCapture.swift
//  FrameCapture
//
//  Created by Marc Palmer on 31/03/2020.
//
//  This is free and unencumbered software released into the public domain.
//
//  Anyone is free to copy, modify, publish, use, compile, sell, or
//  distribute this software, either in source code form or as a compiled

minsOne

import _Concurrency
import Combine
import Dispatch
import Foundation

// MARK: General

struct SomeError: Error {}

extension AnyPublisher {

jasdev

import SwiftUI

/**

 ### Exercises for the viewer

 - Phase interrupt handling.
     - Use Swift concurrency.
 - Color scheme awareness.
 - Rework animations to be more spring-like à la what shipped in `0.90.0`.

tclementdev

libdispatch efficiency tips

The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).

My take-aways are:

• You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.

• Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse

niw

UINavigationBar on iOS 11

NOTE This note is written based on Xcode version 9.0 beta 6 (9M214v) and its simulator binary.

iOS 11 changes UINavigationBar a lot, not just only for its large title, but also the internal view hierarchy and lay outing views are changed. This is a small note about UINavigationBar behavior on iOS 11, mainly focusing on migrating the application to iOS 11.

Lay outing views

UINavigationBar has been using manual lay outing until iOS 10, so all its content views like titleView has been directly child view of the UINavigationBar. However, since iOS 11, it is using auto layout with bunch of layout guides to lay out its content views in its own internal container view, _UINavigationBarContentView.

joshavant

class AppDelegate: UIResponder, UIApplicationDelegate {
    private var currentUserNotificationTypes: UIUserNotificationType = .None

    private func processUpdatedUserNotificationSettings(application: UIApplication, currentUserNotificationSettings notificationSettings: UIUserNotificationSettings?) {
        let newUserNotificationTypes: UIUserNotificationType = notificationSettings?.types ?? .None
        
        // only performs actions if the current value has a delta with the new value
        if currentUserNotificationTypes.contains(.Alert) != newUserNotificationTypes.contains(.Alert) {
            self.currentUserNotificationTypes = newUserNotificationTypes
            

soffes

import UIKit

/// Space view intented to be used with auto layout.
/// Similar to UIStackView, setting a background color is not supported.
final class SpaceView: UIView {

	// MARK: - Properties

	private let contentSize: CGSize

JadenGeller

// Example

let blueView = UIView()
blueView.backgroundColor = UIColor.blueColor()
blueView.translatesAutoresizingMaskIntoConstraints = false

let greenView = UIView()
greenView.backgroundColor = UIColor.greenColor()
greenView.translatesAutoresizingMaskIntoConstraints = false

zats

#ifdef DEBUG

#import "WMLSwizzler.h"

static SEL wml_loadViewSEL;

static void wml_swizzleLoadViewForClass(Class class) {
    typedef void(*load_view_t)(id, SEL);
    __block load_view_t loadView = (load_view_t)[class S_replaceInstanceMethod:wml_loadViewSEL withBlock:^(UIViewController *self){
        loadView(self, wml_loadViewSEL);