[digdog dig]; — MapKit annotation drag and drop with callout info... MKPointAnnotation Tutorial - DevFright. Face Recognition with OpenCV · objc.io. A Bit of Background OpenCV is an open-source computer vision and machine learning library. It contains thousands of optimized algorithms, which provide a common toolkit for various computer vision applications. According to the project’s about page, OpenCV is being used in many applications, ranging from stitching Google’s Street View images to running interactive art shows. OpenCV started out as a research project inside Intel in 1999. It has been in active development since then, and evolved to support modern technologies like OpenCL and OpenGL and platforms like iOS and Android. In this article, I will provide an overview of OpenCV from an iOS developer’s perspective and introduce a few fundamental classes and concepts. Overview of OpenCV Concepts OpenCV is a C++ API consisting of various modules containing a wide range of functions, from low-level image color space conversions to high-level machine learning tools.
Using C++ APIs for iOS development is not something most of us do daily. Core Data Tutorial for iOS: Getting Started. Core Data Failed Banks Model Diagram Swift Update: Check out our book Core Data by Tutorials for the latest on Core Data in iOS 8 and Swift! The first chapter of the book is available as a free tutorial too: Your First Core Data App Using Swift. Update 4/17/12: Fully updated for iOS 5 (original post by Ray Wenderlich, update by Adam Burkepile). Of all of the ways to persist data on the iPhone, Core Data is the best one to use for non-trivial data storage. It can reduce the memory overhead of your app, increase responsiveness, and save you from writing a lot of boilerplate code. However, the learning curve for Core Data can be quite large. In this first part of the series, we’re going to create a visual data model for our objects, run a quick and dirty test to make sure it works, and then hook it up to a table view so we can see a list of our objects.
Before proceeding with this Core Data tutorial, I recommend checking out the tutorial series on SQLite for iPhone Developers first. Greg Heo. Top 10 Core Data Tools and Libraries. If you're new here, you may want to subscribe to my RSS feed or follow me on Twitter. Thanks for visiting! Check out the top 10 Core Data tools to use in your apps! Core Data is a great choice for persisting and querying data in your iOS and OSX apps. Not only can it reduce memory usage and improve performance, but it can also save you from writing a lot of unnecessary boilerplate code. In addition, the Core Data API is extremely flexible, which allows it to be used in a myriad of apps, all with different data storage requirements. However, this flexibility means that sometimes Core Data can be slightly difficult to work with.
Luckily, there are a lot of great tools that can help you out and make Core Data significantly easier to work with. Note: Even with these great tools and libraries, you’ll still need a good understanding of Core Data to reap their benefits. Also note this article has an Objective-C focus since most Core Data libraries are written in Objective-C at the moment. 10. 9.
Core Data from Scratch: Subclassing NSManagedObject. Earlier in this series, we created Done, a simple application to learn more about the NSFetchedResultsController class. In that project, we used key value coding (KVC) and key value observing (KVO) to create and update records. This works fine, but from the moment your project has any kind of complexity, you'll quickly run into issues. Not only is the KVC syntax verbose, valueForKey: and setValue:forKey:, it may also introduce errors that are the result of typos. The following code snippet is a good example of the latter problem. Each statement in the above code snippet returns a different result. In fact, every statement will result in an exception apart from the third statement, which uses the correct key as specified in the project's data model. The above problem is easily solved by using string constants, but that's not the point I'm trying to make.
To save some time, we're going to revisit Done, the application we created earlier in this series. We've made five changes. How To Get the Current User Location in iPhone App | iOS Programming. This is the third article of the iOS Programming 101 series. In the previous two articles, we showed you how to hide the tab bar and implement email feature in your app. In this article, we’ll show you how to add GPS capability in your iPhone app and retrieve the user’s current location.
We’ll even cover tip to translate the GPS coordinate into street address. It’s gonna to be fun and pretty easy to implement. Location services provide a way to improve your app by enhancing the user experience. If you’re developing a travel app, you can base on the users’ current location to search for nearby restaurants or hotels. You can also find the location feature in most of the Photo apps that saves where the pictures are taken. In this tutorial, we’ll build a simple app to show you how to use the Core Location framework.
Okay, let’s get started. Create the Project and Design the Interface First, create a new Xcode project using the Single View Template. MyLocationDemo Xcode Project Why? That’s it. Tab Bar Controllers. You use tab bar controller to organize your app into one or more distinct modes of operation. The view hierarchy of a tab bar controller is self contained. It is composed of views that the tab bar controller manages directly and views that are managed by content view controllers you provide. Each content view controller manages a distinct view hierarchy, and the tab bar controller coordinates the navigation between the view hierarchies. This chapter describes how you configure and use tab bar controllers in your app. Anatomy of a Tab Bar Interface A tab bar interface is useful in situations where you want to provide different perspectives on the same set of data or in situations where you want to organize your app along functional lines.
The manager for a tab bar interface is a tab bar controller object. Figure 2-1 shows the tab bar interface implemented by the Clock app. When a tab bar view is part of a tab bar interface, it must not be modified. The Objects of a Tab Bar Interface. An iOS 7 Core Data Tutorial. From Techotopia In the previous chapter, entitled Working with iOS 7 Databases using Core Data, an overview of the Core Data stack was provided, together with details of how to write code to implement data persistence using this infrastructure. In this chapter we will continue to look at Core Data in the form of a step by step tutorial that implements data persistence using Core Data in an iOS 7 application.
 The Core Data Example Application The application developed in this chapter will take the form of the same contact database application used in previous chapters, the objective being to allow the user to enter name, address and phone number information into a database and then search for specific contacts based on the contact’s name.  Creating a Core Data based Application As is often the case, we can rely on Xcode to do much of the preparatory work for us when developing an iOS application that will use Core Data.  Creating the Entity Description Figure 42-1.
Place Autocomplete Requests The Place Autocomplete service is part of the Google Places API Web Service and shares an API key and quotas with the Google Places API Web Service. The Place Autocomplete service can match on full words as well as substrings. The returned predictions are designed to be presented to the user to aid them in selecting the desired place. Required parameters Optional parameters <? Intro to MapKit API and Add an Annotation on Map | iOS Programming.
A month ago, we covered how to use Core Location framework to retrieve the user’s location. We also showed you how to convert the GPS coordinate into an address. However, the best way to show a location is to pin it on map. Thanks to the MapKit API. It lets programmers easily work with the built-in Maps and pin a location. The Map Kit framework provides an interface for embedding maps directly into your own windows and views.
MapKit is a neat API, comes with the iOS SDK, that allows you to display maps, navigate through maps, add annotations for specific locations, add overlays on existing maps, etc. Let’s get started. Create the Project and Design the Interface We use Xcode 4.5 to create the project. First, create a new Xcode project using the Single View Template. MyLocationMap Xcode Project Once you successfully created your project, go to the Storyboard and design the user interface. Embed View Controller in Navigation Controller Optionally, you can set the title of the navigation bar. Ios - Calculate distance between two place using latitude-longitude in gmap for iPhone.
⌘Boom - Storyboards, multiple developers and git. Storyboards are great. You can get the flow of your app set up in a few minutes without writing a line of code, you can initialise your navigation controllers and tabs ridiculously easily and zoom out a bit and you get a lovely picture of your entire app on a single screen, with lines and boxes and everything. But storyboards can be cruel if you’re not careful. Git pull’s become nervy affairs, a slip merging by hand can render your storyboard unreadable by Xcode and not knowing when to stop using them can turn your lovely lines and boxes into a maintenance nightmare.
“Come to the coast, we’ll get together, have a few segues” We’ve done a bunch of apps of all shapes and sizes using storyboards over the last year or so and we’re working on perfecting our use of them. The Precap (Wiktionary says it’s a word) Xcode We’ve had hassle sharing storyboards across even minor versions of Xcode, storyboards created in one will do crazy stuff in another, or just plain won’t work. Multiple storyboards. Using Multiple Storyboards in iOS Development. I recently started working on an iOS project with two other senior developers here at Atomic Object. When it came time to set up our project in xCode 5, a practical issue was raised: how can we best work on the app in parallel, using the Interface Builder with storyboards?
Storyboards are described by XML files, which is great because it allows a user to look at the properties of the view controllers, views, etc. in code and make changes. We’ve also had success with our designers adding and changing assets directly in interface builder via storyboards. What isn’t so great is dealing with merging changes when multiple developers are editing the same storyboard.
In this blog post, I will describe how we addressed the storyboard merging problem and give some simple tips for how to avoid the problem in the future. What Not To Do Hand-Coded UIs In the post “Why Can’t We Merge Storyboards,” Brian Hynds covers some of the issues that developers face when trying to merge changes to a storyboard. User interface - Using Multiple Storyboards in iOS. Programming Knowledge Base: Linking Storyboards.
Summary Previously I wrote about best practices with UIStoryboards. Since then I have continued to explore the possibilities of storyboards. With today being the eve of WWDC 2012, I wanted to share one of the tricks I have learned. A key practice of storyboards is to break them down into natural, reusable modules. The downfall to this decomposition is when we need to transition from one storyboard to another. Storyboards were supposed to save us from the tedious transition code, but decomposition brings some of it back. Fortunately, there is a way to remove this pain. Before I go into any details, I want to start with a disclaimer. Implementing You should first download my code from GitHub. The first thing to do is build your storyboards as you normally would.
Now that you have your various storyboards, you can begin connecting them. Next you need to create a segue to each of these surrogate scenes. Once you have your surrogate scene in place, we can make the magic happen. Explanation. Programming Knowledge Base: UIStoryboard Best Practices. UIStoryboard is a hot topic right now in iOS. However, there have been many misconceptions on the topic. The first reaction to storyboards (what I have seen anyway) is that they are a panacea for all situations. Following that reaction I saw many people claim that storyboards are awful and broken.
The truth is, both these ideas are wrong. During WWDC 2011 Apple may have over-promoted storyboards, thus giving the wrong impression and leading to unmet expectations. Let me correct this now: UIStoryboard is not an all-purpose solution, it is another tool for your toolbox. My intent here is to provide the best practices for UIStoryboard. Break your storyboard into modules The first mistake developers have been making with storyboarding is producing large, monolithic storyboards. The first question to ask is "how do I identify the natural modules of my app?
" Keep in mind that having a single view in a storyboard is not a bad thing. You don't need to convert everything at once @end Summary. Introduction to Core Data for iOS and iPhone Programming. Editor’s note: After we published the tutorial about saving data in plist file, some readers asked about Core Data and how we can use it to save persistent information. This week, we work with Ziad Tamim, an independent iOS developer, to give you an introduction of Core Data and work with you to build a sample app using Core Data.
This tutorial talks about persistence on iPhone (or other iOS devices). What I mean by persistence is to make data that’s in your apps stay around between application launches. Persistence lets users store persistent data and also retrieve it, so that users don’t have to reenter all their data each time they use their applications. There are multiple ways to store data in iOS devices but most of them aren’t good enough to store a complicated data. They are usually used to save settings or to preload some data such as “Property List” and “Archiving Objects”. The focus of the tutorial is to provide a practical introduction of Core Data framework. Core Data Stack. Ios - How to hide the keyboard when i press return key in a UITextField?
Unity - Scripting API: Saving Texture2D as a PNG image to HDD in Standalone build. Ios - How To Access Camera & Camera Roll Objective-C. Getting Started · Consuming a RESTful Web Service from iOS. Select the main.storyboard from the project navigator on the left side of the Xcode window. A Storyboard contains the layout for the view. Remember that you can always use the code in the initial folder if you have trouble with any of these steps.
Xcode provides a WYSIWYG editor for creating views. This editor is often referred to as Interface Builder because, historically, it was a separate application. In the bottom right corner of Xcode select and drag two Label objects to the storyboard layout. Next, select and drag a Button object to the storyboard layout. Double-click one label and change it to "[id]", and the other to "[content]". Using the editor, you can move these labels around the storyboard to look similar to the following: The content and id returned from the RESTful service may be longer than the label widths allow. Now that you have all the UI objects on the storyboard, you can associate those objects with the properties in the RestViewController.
iOS. Provisioning. How to Deploy your App on an iPhone. Origami & Quartz. iOS 7. iOS 7. NSURLSession Tutorial. How to build a custom control in iOS. Create Your Own iOS Framework. Iphone - How to build a framework or library for other developers, the secure way? How to Create a Framework for iOS. Build Boost 1.55.0 for iOS 7 and OS X including 64 Bit. Mgrebenets/boost-xcode5-iosx. Danoli3/ofxiOSBoost. Video Capture. OpenCV iOS - Video Processing. Taking Charge of UIView Transforms in iOS Programming. Fluid UI - fast and friendly mobile prototyping. Securing and Encrypting Data on iOS.