| Matt Guest | |
| ============ | |
| Profile | |
| ---------- | |
| I strive to be an asset on any team. I'm a supportive and enthusiastic team-player who prioritizes clear communication, as well as streamlining processes to effectively tackle and conquer project issues. I always take ownership of critical project features. | |
| Education | |
| --------- |
Sources include, but not limited to:
| // You have a very very large video file you need to upload to a server while your app is backgrounded. | |
| // Solve by using URLSession background functionality. I will here use Alamofire to enable multipart upload. | |
| class Networking { | |
| static let sharedInstance = Networking() | |
| public var sessionManager: Alamofire.SessionManager // most of your web service clients will call through sessionManager | |
| public var backgroundSessionManager: Alamofire.SessionManager // your web services you intend to keep running when the system backgrounds your app will use this | |
| private init() { | |
| self.sessionManager = Alamofire.SessionManager(configuration: URLSessionConfiguration.default) | |
| self.backgroundSessionManager = Alamofire.SessionManager(configuration: URLSessionConfiguration.background(withIdentifier: "com.lava.app.backgroundtransfer")) |
| import os, filecmp | |
| codes = {200:'success',404:'file not found',400:'error',408:'timeout'} | |
| def compile(file,lang): | |
| if lang == 'java': | |
| class_file = file[:-4]+"class" | |
| elif lang == 'c': | |
| class_file = file[:-2] | |
| elif lang=='cpp': |
| internal let DEFAULT_MIME_TYPE = "application/octet-stream" | |
| internal let mimeTypes = [ | |
| "html": "text/html", | |
| "htm": "text/html", | |
| "shtml": "text/html", | |
| "css": "text/css", | |
| "xml": "text/xml", | |
| "gif": "image/gif", | |
| "jpeg": "image/jpeg", |
| import UIKit | |
| class ViewController: UIViewController, UITableViewDelegate, UITableViewDataSource { | |
| @IBOutlet var tableView: UITableView! | |
| var itemsInSections: Array<Array<String>> = [["1A", "1B", "1C"], ["2A", "2B"], ["3A", "3B", "3C", "3D", "3E"]] | |
| var sections: Array<String> = ["Section 1", "Section 2", "Section 3"] | |
| func colorWithGradient(frame: CGRect, colors: [UIColor]) -> UIColor { | |
| // create the background layer that will hold the gradient | |
| let backgroundGradientLayer = CAGradientLayer() | |
| backgroundGradientLayer.frame = frame | |
| // we create an array of CG colors from out UIColor array | |
| let cgColors = colors.map({$0.CGColor}) | |
| backgroundGradientLayer.colors = cgColors |
| // Playground - noun: a place where people can play | |
| import Foundation | |
| func toRoman(number: Int) -> String { | |
| let romanValues = ["M", "CM", "D", "CD", "C", "XC", "L", "XL", "X", "IX", "V", "IV", "I"] | |
| let arabicValues = [1000, 900, 500, 400, 100, 90, 50, 40, 10, 9, 5, 4, 1] | |
| var romanValue = "" |
#Collections in Swift
Arrays and dictionaries are the most common data stores in many applications. Swift has brought us a new generation of these collections, so let's take a look at how they compare to the collections found in Objective-C.
##Greatest Differences
###Typing One of the most obvious differences between collections in Objective-C and Swift is that Swift collections are explicitly typed. Typed collections are useful for many reasons, primarily because the system requires you to be precise with the content type you are working with. Any type mismatches will throw errors, which will help you avoid common mistakes.
###Mutability
