Season's Greetings, NSHipsters!
As the year winds down, and we take a moment to reflect on our experiences over the past months, one thing is clear: 2014 has been an incredible year professionally for Apple developers. So much has happened in such a short timespan, and yet it's hard to remember our relationship to Objective-C before Swift, or what APIs could have captivated our imagination as much as iOS 8 or WatchKit.
It's an NSHipster tradition to ask you, dear readers, to send in your favorite tips and tricks from the past year for publication over the New Year's holiday. This year, with the deluge of new developments—both from Cupertino and the community at large—there should be no shortage of interesting tidbits to share.
Submit your favorite piece of Swift or Objective-C trivia, framework arcana, hidden Xcode feature, or anything else you think is cool, and you could have it featured in the year-end blowout article. Just comment on this gist below!
If you're wondering about what to post, look to past year's write-ups for inspiration (2014, 2013).
I can't wait to see what you all send in!
Swift Playgrounds all share the same
Shared Playground Data
folder that's symlinked to/Users/HOME/Documents/Shared Playground Data
.If you like using lots of Playgrounds, you'll want to organize the data that each Playground is using into subfolders of that shared folder, but then you've got to let the Playground know where to look. Here's a helper function that I use that makes that easy:
That
processName
property inNSProcessInfo
contains the name of the Playground file, so as long as you have already created a sub-folder in theShared Playground Data
folder with the same name you can access those files pretty easily, like reading local JSON:or pulling out a local image: