Understanding the parsing process
Video: Understanding the parsing processXML is one of the most common formats for raw data on the Internet today. It's used for XHTML, SOAP, RSS, and many other data delivery applications. The iOS SDK provides a powerful event driven XML Parser, like many iOS Services, it's event driven, and it works with the delegate protocol. The parsing process can take some time, so we use a separate execution thread for it. This allows the application to continue to respond to touch events, while the parsing takes place in the background.
Viewers: in countries Watching now:
The iOS software development kit (SDK) includes the popular SQLite library, a lightweight yet powerful relational database engine that is easily embedded into an application. In this course, Bill Weinman teaches you how to build an RSS reader for iOS devices, integrating XML data and a streamlined interface. He explains how to use the SQLite database, display information in a table view, code view controllers, and create a preferences pane for your app. The resulting application is optimized for all iPhone and iPad displays.
- Prototyping the app
- Coding and working with a testbed
- Creating an Objective-C interface for SQLite
- Designing a database schema
- Creating the view controllers
- Reading and writing to the database
- Parsing the RSS feed with NSXMLParser
- Updating the item view with feed items
- Implementing the pull to refresh gesture for iOS 6
- Creating a universal application with multiple views
Understanding the parsing process
XML is one of the most common formats for raw data on the Internet today. It's used for XHTML, SOAP, RSS, and many other data delivery applications. The iOS SDK provides a powerful event driven XML Parser, like many iOS Services, it's event driven, and it works with the delegate protocol. The parsing process can take some time, so we use a separate execution thread for it. This allows the application to continue to respond to touch events, while the parsing takes place in the background.
This provides a better user experience as it keeps the application from seeming unresponsive. Before we can parse the XML, we need to get it from the network using the NSURLConnection Class. As we get the data from the network, we'll be displaying the activity indicator in the status bar. This gives the user some feedback so they know that something is happening and data is coming. Using the Activity Indicator is not an excuse to block User Input. The user must still be able to use the app. They will expect the user interface to still respond to input.
XML data is parsed and added to a local database. We store the data for two reasons: one, a portable device has limited available memory, so we cannot carry around a lot of data at once. Storing data in the database freezes up valuable RAM, while keeping data readily available. And two, this gives our application data persistence. So the user can maintain a context between sessions and they don't have to read and parse the data from the net every time they need it. So we drive the app from the database.
This allows the user to use the app without having to wait for data from the net every time they need it. This is the lifecycle of the data in our application. Read XML from the net, parse it, store the results in the database, and drive the application from the data in the database. This is a very common model for a data driven application as it allows the app to provide a great user experience.
Find answers to the most frequently asked questions about iOS SDK and SQLite: Building Data-Driven Apps (2013) .
Here are the FAQs that matched your search "" :
- Q: Why is the RSSDB library in the exercise files different than the one in the videos?
A: The RSSDB library had to be updated to work around a bug in the iOS 7 SDK.
There is a bug in the iOS 7 SDK that prevents the BWDB fast enumeration implementation from working on a device. The symptom is code that runs fine on the emulator, but not on a device. iOS devices use an ARM processor, while the emulator runs on your Mac's Intel processor. This points to the LLVM ARM code generator as the source of the bug. Because the bug appears to be in the LLVM compiler, it may be some time before it is fixed.
As a workaround we have changed the getFeedIDs and getItemIDs methods in the RSSDB library so they don't use Objective C fast enumeration.
Please note that this same bug also affects some of the BWDB testbed code in Chapter 2. The result is that it will run on the emulator but not on a device.
- Q: After upgrading to Xcode 5.1 I get an error that says:
"Used type va_list (aka_builtin_va_list) where arithmetic or pointer type is required"
- A: Please download the exercise files again to get the latest version of the BWDB library.
- Q: I'm using Xcode 6. Why am I getting error messages with the exercise files?
- A: A lot has changed in iOS since this course was released. The author is in the process of rewriting the code and updating the course for iOS 8. In the meantime he has prepared a version of the app that works in iOS 8 and Xcode 6. Download it here:http://ios.bw.org/
Sorry, there are no matches for your search "" —to search again, type in another word or phrase and click search.