chriseidhof

// Run any SwiftUI view as a Mac app.

import Cocoa
import SwiftUI

NSApplication.shared.run {
    VStack {
        Text("Hello, World")
        	.padding()
            .background(Capsule().fill(Color.blue))

TyrfingMjolnir

Based on

https://developer.apple.com/design/human-interface-guidelines/ios/icons-and-images/image-size-and-resolution/

Prerequisite

$ brew install imagemagick

This is one way to run this script:

avdyushin

OS X Screencast to animated GIF

This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.

Instructions

To capture the video (filesize: 19MB), using the free "QuickTime Player" application:

avdyushin

#!/usr/bin/python
# coding: utf8

import io
import re
import time
import shutil
import os.path
import hashlib
import argparse

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

gokselkoksal

public class Channel<Value> {
    
    private class Subscription {
        
        weak var object: AnyObject?
        private let notifyBlock: (Value) -> Void
        private let queue: DispatchQueue
        
        var isValid: Bool {
            return object != nil

inamiy

React & Elm inspired frameworks in Swift

This is a curated list of iOS (Swift & ObjC) frameworks which are inspired by React and Elm.

Swift frameworks

React-inspired

• ReactSwift by @ColinEberhardt
• https://github.com/ColinEberhardt/ReactSwift

jeamesbone

extension UIStoryboard {
    func instantiateViewController<S: Scene>(for scene: S) -> S.ViewController {
        guard let viewController = instantiateViewController(withIdentifier: scene.identifier) as? S.ViewController
        else {
                fatalError("expected view controller with identifier '\(scene.identifier)' to be of type '\(String(describing: S.ViewController.self))'")
        }
        scene.configureViewController(viewController)
        return viewController
    }
}

CanTheAlmighty

//
//  DisplayLink.swift
//  MetalMac
//
//  Created by Jose Canepa on 8/18/16.
//  Copyright © 2016 Jose Canepa. All rights reserved.
//

import AppKit

andymatuschak

A composable pattern for pure state machines with effects

State machines are everywhere in interactive systems, but they're rarely defined clearly and explicitly. Given some big blob of code including implicit state machines, which transitions are possible and under what conditions? What effects take place on what transitions?

There are existing design patterns for state machines, but all the patterns I've seen complect side effects with the structure of the state machine itself. Instances of these patterns are difficult to test without mocking, and they end up with more dependencies. Worse, the classic patterns compose poorly: hierarchical state machines are typically not straightforward extensions. The functional programming world has solutions, but they don't transpose neatly enough to be broadly usable in mainstream languages.

Here I present a composable pattern for pure state machiness with effects,