| <?php | |
| include("wp-config.php"); | |
| $mysqli = new mysqli(DB_HOST, DB_USER, DB_PASSWORD, DB_NAME); | |
| if ($mysqli->connect_error) { | |
| die('Connect Error (' . $mysqli->connect_errno . ') ' | |
| . $mysqli->connect_error); | |
| } | |
| if ($result = $mysqli->query("SELECT term_taxonomy_id FROM " . $table_prefix . "term_taxonomy")) { |
| import SwiftUI | |
| extension Calendar { | |
| func generateDates( | |
| inside interval: DateInterval, | |
| matching components: DateComponents | |
| ) -> [Date] { | |
| var dates: [Date] = [] | |
| dates.append(interval.start) |
To enable the rotation of a single view controller used to display the preview of Images/Videos. It is intuitive to allow user to rotate there device and screen changes accordingly, so it feels pleasant. But to achieve this, we need to enable the (almost) all Supported Device orientations.
Ex: `Portrait`, `LandscapeLeft`, `LandscapeRight`.
| #! /bin/bash | |
| # | |
| # Script to deploy from Github to WordPress.org Plugin Repository | |
| # A modification of a number of different sources: | |
| # @link https://github.com/deanc/wordpress-plugin-git-svn | |
| # @link https://github.com/GaryJones/wordpress-plugin-svn-deploy | |
| # @link https://github.com/thenbrent/multisite-user-management/blob/master/deploy.sh | |
| # | |
| # Accompanying Tutorial Here: | |
| # @link https://ericbusch.net/?p=106 |
Modern Cocoa development involves a lot of asynchronous programming using closures and completion handlers, but these APIs are hard to use. This gets particularly problematic when many asynchronous operations are used, error handling is required, or control flow between asynchronous calls gets complicated. This proposal describes a language extension to make this a lot more natural and less error prone.
This paper introduces a first class Coroutine model to Swift. Functions can opt into to being async, allowing the programmer to compose complex logic involving asynchronous operations, leaving the compiler in charge of producing the necessary closures and state machines to implement that logic.
| // | |
| // TooltipView.swift | |
| // Customizable Tooltips | |
| // | |
| // Copyright © 2017 Simon Wuyts | |
| // | |
| // 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 |
| // | |
| // Obfuscator.swift | |
| // | |
| // Created by Dejan Atanasov on 2017-05-31. | |
| // | |
| import Foundation | |
| class Obfuscator: AnyObject { | |
| //: Playground - noun: a place where people can play | |
| import UIKit | |
| import PlaygroundSupport | |
| class WLCollectionCell: UICollectionViewCell { | |
| required init?(coder aDecoder: NSCoder) { | |
| fatalError("init(coder:) has not been implemented") | |
| } | |
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,
