There was a lot of talk a few months ago about Apple’s marketing of the iPad Pro, and how they are positioning it as a PC replacement. In order for app developers to produce professional-level content creation apps, Apple needs to create more complex and generalized user-facing developer components that are designed for the human finger.
I’d like to go back to the basics, and revisit the interface that I need for this to work. We want to be able to display a list of venues, either alphabetically or in proximity to some location. The list is filtered by venue type, and sometimes, a subtype and/or a search string. To accomplish this, we need a few steps.
The new Kosher GPS app is finally out. I’ve been working on it for over two years, and it’s finally out. (This post is a little late too, I guess in the spirit of things.) It’s really exciting. The new version includes a modern user interface and some really cool integrations.
From the App Store release notes, the new features are:
I linked to my previous post on a swift slack channel and got some interesting feedback. I forgot to mention in the last post the option of subclassing NSSortDescriptor to order by location. One of the ideas was one I tried but forgot to mention: subclassing NSSortDescriptor to compare based on distance. I had initially abandoned that approach because of something in this blog post which explains some gotchas involved in that process. I mistakenly thought that ARC made it impossible to override
copyWithZone:, which is one of the “requirements” mentioned in that post.
I’m building an app that is supposed to track user location and sort a bunch of venues based on where the user is on the latitude/longitude coordinate system relative to those venues. This post is me thinking through how to make Core Location and Core Data work together to sort the venues. I’m using Objective-C for some parts of the app, but my Core Data stack is all Swift 2.2, Xcode 7.3.1 and I’m testing on iOS 9.3.1.
There are plenty of situations where you might want to generate a PDF from a
UIScrollView. If you search the internet, you’ll find lots of posts instructing you to change the frame of the scroll view to enclose all of its contents. This won’t work if you’re using AutoLayout. In any case, there’s a better way.
If you’ve ever seen this Xcode complain about that the “plain style” for UIBarButtonItem is “unsupported in a navigation item” you know that it can be a nuisance to narrow down which button item has the unsupported style, especially in larger projects.
Here’s some good news for you. It’s pretty easy to figure out what button is causing the warning. Here’s how you do it: