Genady Okrain genadyo

Brooklyn Swift Developers Meetup Presenters

A list of presenters at the Brooklyn Swift Developers Meetup with links to videos, slides and source code: http://www.meetup.com/Brooklyn-Swift-Developers

September 2017

Taiki Suzuki - Flux & MVVM (Video)

Harlan Kellaway - Should Code Always be DRY? (Video)

Glances in Apple Watch

Introduction

So last time we learned how to synchronise data between our iPhone and Watch app, this week we're going to look at using that to set up glances. Glances enable us to display timely and relevant data to our users, for our example we're going to show the user whatever colour they were last looking at on the iPhone app.

The official documentation for glances suggests using timers to periodically update the data the glance is displaying. How often your app checks for updates is up to you however, I wouldn't do it too often or the user might uninstall your app for consuming too much battery power.

Running Glances

Firstly, we need to tell our emulator to run the "glances" mode and not the proper Apple Watch App. To do this click on the target for the emulator (bit to the left of which device your going to run on) and press edit scheme.

Last week, a number of publications ran a story about 1,000's of apps allegedly being vulnerable due to an SSL bug in AFNetworking. These articles contain a number of inaccurate and misleading statements on this matter.

We are publishing this response to clarify and correct these statements.

Background Information

For those not familiar with AFNetworking, here are some relevant details about the library for this story:

AFNetworking is an open source, third-party library that provides convenience functionality on top of Apple's built-in frameworks.
One component of AFNetworking is AFSecurityPolicy, which handles authentication challenges according to a policy configured by the application. This includes the evaluation of X.509 certificates which servers send back when connecting over HTTPS.

This code has moved

Please refer to the TimeLapseBuilder-Swift repository on GitHub from now on.

I will leave the original code here as a reference, but new comments may be removed. Please open an issue on GitHub if you have questions or would like to contribute.

Thanks!

Thoughts on Swift 2 Errors

When Swift was first announced, I was gratified to see that one of the (few) philosophies that it shared with Objective-C was that exceptions should not be used for control flow, only for highlighting fatal programming errors at development time.

So it came as a surprise to me when Swift 2 brought (What appeared to be) traditional exception handling to the language.

Similarly surprised were the functional Swift programmers, who had put their faith in the Haskell-style approach to error handling, where every function returns an enum (or monad, if you like) containing either a valid result or an error. This seemed like a natural fit for Swift, so why did Apple instead opt for a solution originally designed for clumsy imperative languages?

I'm going to cover three things in this post:

	#!/bin/sh

	###
	# SOME COMMANDS WILL NOT WORK ON macOS (Sierra or newer)
	# For Sierra or newer, see https://github.com/mathiasbynens/dotfiles/blob/master/.macos
	###

	# Alot of these configs have been taken from the various places
	# on the web, most from here
	# https://github.com/mathiasbynens/dotfiles/blob/5b3c8418ed42d93af2e647dc9d122f25cc034871/.osx

	import time
	import random


	class MatrixFibonacci:
	A = [[1, 1],
	[1, 0]]

	def __init__(self):
	self.__memo = {}

	//
	// UINavigationBar+CustomHeight.h
	//
	// Copyright (c) 2014 Maciej Swic
	//
	// Permission is hereby granted, free of charge, to any person obtaining a copy
	// of this software and associated documentation files (the "Software"), to deal
	// in the Software without restriction, including without limitation the rights
	// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	// copies of the Software, and to permit persons to whom the Software is

	/// Observes a run loop to detect any stalling or blocking that occurs.
	///
	/// This class is thread-safe.
	@interface GHRunLoopWatchdog : NSObject

	/// Initializes the receiver to watch the specified run loop, using a default
	/// stalling threshold.
	- (id)initWithRunLoop:(CFRunLoopRef)runLoop;

	/// Initializes the receiver to detect when the specified run loop blocks for

	<?xml version="1.0" encoding="UTF-8"?>
	<Bucket
	type = "2"
	version = "2.0">
	<Breakpoints>

	<!-- All Exceptions -->
	<BreakpointProxy
	BreakpointExtensionID = "Xcode.Breakpoint.ExceptionBreakpoint">
	<BreakpointContent