Samuel Défago defagos

WWDC                                2006  2007  2008  2009
2010 2011 2012 2013 2014

How to use a `.xcconfig` file and a `.plist` file with SPM

Worth a read for some more context.

Create a Package.xcconfig file

Create the file in the root of the project (where your Package.swift file lives as well), and use the following contents:

/// Package.xcconfig

To support my open-source work, consider adding me on Patreon.

macOS 10.14 Mojave Mostly-Automated Setup

An easy to refer to document for regularly setting up macOS 10.14 Mojave.

Controversy

The topic of recipe-based frequent fresh reinstalls of macOS is a controversial issue. Some people are against reinstalling macOS, citing that they have never had an issue with Apple provided upgrade installs.

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

running:

bash create-vod-hls.sh beach.mkv

will produce:

    beach/
      |- playlist.m3u8
 |- 360p.m3u8

`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.

	/// Used to identify traits of the current UI Environment - especially useful for cross-platform code
	public struct MNCUITraits: Withable {

	/// Does not identify the device type, but the idiom of the layout to apply
	/// This means that e.g. on iPad the layoutIdiom can be `.phone`, if run in Split Screen or SlideOver
	public enum LayoutIdiom {
	case phone(hasRoundCorners: Bool)
	case pad(hasRoundCorners: Bool)
	case mac
	}

	#!/bin/bash
	# usage: get [ RESOLUTION [ YEAR [ IDS... ] ] ]

	resolution=${1:-SD}
	year=${2:-2015}
	shift
	shift
	ids=$*

	RESOLUTION=$(echo $resolution \| tr '[:lower:]' '[:upper:]')

	public enum Direction {
	case forward
	case backward
	}

	internal var player: AVPlayer?

	private var isSeekInProgress = false
	private var chaseTime = kCMTimeZero
	private var preferredFrameRate: Float = 23.98