If your Haskell project has lots of dependencies, you can find yourself reaching the timeout while compiling them - the free service has a timeout of 50 minutes. How do we address this?
First, a quick reminder of build statuses in Travis CI:
All builds finish with one of four possible statuses: succeeded, failed, errored, or (manually) cancelled. The difference between a failed and errored
| import UIKit | |
| class MyView: UIView { | |
| fileprivate var myPreviewInteraction: Any? = nil | |
| init() { | |
| super.init(frame: CGRect.zero) | |
| if #available(iOS 10.0, *) { | |
| myPreviewInteraction = UIPreviewInteraction(view: self) |
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,
| import UIKit | |
| extension UIImage { | |
| // colorize image with given tint color | |
| // this is similar to Photoshop's "Color" layer blend mode | |
| // this is perfect for non-greyscale source images, and images that have both highlights and shadows that should be preserved | |
| // white will stay white and black will stay black as the lightness of the image is preserved | |
| func tint(tintColor: UIColor) -> UIImage { | |
| //some time, frc section may be need section offset | |
| @objc public protocol MFetchedResultsControllerOffsetSectionDelegate{ | |
| func offsetSection() -> Int | |
| } | |
| class MFetchedResultsController: NSFetchedResultsController, NSFetchedResultsControllerDelegate { | |
| weak var viewController: UIViewController? //UITableViewController UICollectionViewController | |
| weak var scrollView: UIScrollView? //TableView CollectionView | |
| weak var offsetSectionDelegate: MFetchedResultsControllerOffsetSectionDelegate? |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
| extension UIImage | |
| { | |
| func tint(color: UIColor, blendMode: CGBlendMode) -> UIImage | |
| { | |
| let drawRect = CGRectMake(0.0, 0.0, size.width, size.height) | |
| UIGraphicsBeginImageContextWithOptions(size, false, scale) | |
| let context = UIGraphicsGetCurrentContext() | |
| CGContextClipToMask(context, drawRect, CGImage) | |
| color.setFill() | |
| UIRectFill(drawRect) |
| #!/bin/bash | |
| set -x | |
| cd ${0%/*}/.. | |
| # codesigning and choosing of provisioning profile is configured via project settings and is dependent of build config | |
| : ${BUILD_NUMBER:?"Need to set BUILD_NUMBER"} | |
| WORKSPACE=<yourworkspace>.xcworkspace |
For iPhone app developers. Emphasis on getting the fastest app store approval. Everything stated as suggestion made into an imperative. When "violating" these imperatives, you can check for yourself what the caveats are. Generally speaking, deviating will more likely cause your app to be hung up in approval.
You can read this entire document in about 20 minutes. This is faster than reading and understanding the entire Human Interface Guidelines.