The problem with macOS and Drawing
Trying to write cross-platform code for drawing routines is ridiculously frustrating. It’s never just a matter of creating cross-platform type aliases. UIColor and NSColor are cousins, not brothers. UIBezierPath and NSBezierPath are slightly more distantly related, especially when it comes to adding curves and retrieving an underlying cgPath. Although a lot of tech debuts on Cocoa, it often gets r
The names of things
Last night, someone was asking what you call the things created by types. My take on the subject is this: Classes, structures, and enumerations are constructs. You create new instances by calling a constructor, even when building things that aren’t reference types. I avoid calling reference types “objects”. I stick with instances, following the Swift Programming Language’s lead, e.g. “Use the init
Swift, Xcode: Beta 6 accessing Swift-native definitions
Having any problems in Swift getting access to native definitions through Command-click? You’re not alone. (As one person put it, “b6 is [colloquial expression of extreme disappointment] even by Xcode beta standards”) Here’s a workaround. Select any Foundation item like NSString and Command-click it like you used to. In the definitions file, use the Jump bar to move from Foundation > NSString > NS
iOS 8: Building custom simulators
Right now in Xcode 6, there are plenty of simulators to choose from but did you know that you could create your own simulators and customize them for specific testing needs? The simctl command line utility, which you find at /Applications/Xcode6-Beta.app/Contents/Developer/usr/bin/simctl, enables you to create new custom simulators built to your specifications. You start by creating a device, sett
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Dear Erica: Playground Support Folder
