davbeck

Swift options

Recently, 2 Swift Evolution proposal results have really disappointed me. Together they move Swift away from the flexibility of using method parameters as option lists.

SE-0060 Enforcing order of defaulted parameters, which was accepted, removes the ability to provide optional parameters in any order you like. I had actually hoped to go the other direction and extend this ability to include required parameters. Now, as you add and remove parameters to a call site, you have to make sure to do so in the proper order. As the number of parameters a method takes grows, and as the relation between them gets weaker, it becomes more and more difficult to determine the correct positioning without referring to documentation.

SE-0084 Allow trailing commas in parameter lists and tuples was rejected. This proposal so

davbeck

imgIX

imgIX is similar to a proxy CDN that sits between where we store the full-size images and the devices and browsers that download them. Images are not stored in imgIX directly but instead on an HTTP server such as S3. You configure "sources" in imgIX that then proxy to the source server.

In our case, we would upload images directly to S3, then the clients would request them using the imgIX URL instead of the direct S3 URL. You can then include URL parameters in addition to the original URL that specify the size you will display the images at, the pixel density (ie retina), as well as other transformations such as auto compression. This leads to drastically smaller file sizes, which download faster, use less bandwidth and use less memory on the user's device. There are other features we can take advantage of like smart cropping that centers detail like faces in square cropped photos.

Tests

I uploaded 4 photos from an iPhone 6s to S3 using the app and then tested their dow

davbeck

#!/usr/bin/env ruby

require "active_support"


def assetCatalogsAtPath(path)
	results = []
	
  contents = Dir.entries(path)
  

davbeck

extension NSNumber {
	@nonobjc convenience init(_ value: Bool) {
        self.init(bool: value)
	}
	
	@nonobjc convenience init(_ value: Float) {
		self.init(float: value)
	}
	
	@nonobjc convenience init(_ value: Double) {

davbeck

import Foundation


protocol GQLNodeArgument {}
extension String: GQLNodeArgument {}
extension NSNumber: GQLNodeArgument {}


class GQLNode: StringLiteralConvertible, ArrayLiteralConvertible, Printable, DebugPrintable {
    let name: String?

davbeck

//
//  TNKURLFormatter.swift
//
//  Created by David Beck on 2/6/15.
//  Copyright (c) 2015 ThinkUltimate. All rights reserved.
//

import Foundation

davbeck

#pragma mark - WKUIDelegate

- (void)webView:(WKWebView *)webView runJavaScriptAlertPanelWithMessage:(NSString *)message initiatedByFrame:(WKFrameInfo *)frame completionHandler:(void (^)())completionHandler
{
    UIAlertController *alert = [UIAlertController alertControllerWithTitle:nil
                                                                   message:message
                                                            preferredStyle:UIAlertControllerStyleAlert];
    
    [alert addAction:[UIAlertAction actionWithTitle:NSLocalizedString(@"OK", nil) style:UIAlertActionStyleCancel handler:^(UIAlertAction *action) {
        completionHandler();

davbeck

#!/usr/bin/env ruby
#encoding: utf-8

require 'active_support/all'

timezones = ActiveSupport::TimeZone::MAPPING.map { |rails_name, name|
  zone = ActiveSupport::TimeZone.new(name)
  {
    rails_name => {
      offset: zone.utc_offset,

davbeck

{
   "International Date Line West":{
      "offset":-39600,
      "abbreviation":"SST",
      "name":"Pacific/Midway"
   },
   "Midway Island":{
      "offset":-39600,
      "abbreviation":"SST",
      "name":"Pacific/Midway"

davbeck

It's become common practice to use an @selector for associated objects. This is useful because not only are SELs guaranteed to have a unique address, but because as of Xcode 5, Xcode will warn you when you use a selector that it does not know about. Meaning that it is somewhat protected against spelling mistakes.

This can also be useful when using string keys. For things like state restoration, where you want a key for a given property, you can use the selector for the getter, and get a string from that. Xcode will autocomplete the name for you, and will warn you if you misspell it.

- (void)encodeRestorableStateWithCoder:(NSCoder *)coder
{
    [super encodeRestorableStateWithCoder:coder];
    
 [coder encodeObject:self.feedID forKey:TNKPropertyKey(feedID)];