You can ask yourself the question, "Why would I read the book about this library?" Of course, you can read the RestKit documentation. It's a perfect example of how to write down a good API reference for a framework. On the other hand, you can dive into researching the RestKit test cases, which is also nice and interesting, as the unit tests are covering almost all the functionalities of a framework. However, it won't make you happy.
While reading the API documentation is nice and it is full of simple examples for every class, it won't help you understand how to easily apply the framework in your daily jobs. Therefore, the key goal of this book is to provide guidance and real-life usage examples. We will start from a basic example of how to load a simple list of objects to creating a full-featured app, with advanced mapping techniques, Core Data integration, and so on.
Chapter 1, Getting Started, starts with the key concepts of RestKit, describes how to install it, and shows a short example of basic data loading.
Chapter 2, Modeling and Loading Remote Objects, describes how to configure RestKit and data mapping, how to use one-line methods to load objects and push them back to the server, and how to integrate the code with nice UI.
Chapter 3, Persistence with Core Data, describes how to make RestKit persist and synchronize data with Core Data databases.
Chapter 4, Advanced Stuff, covers some more advanced features of RestKit and AFNetworking libraries that developers might use in everyday app development and will help overcome potential bottlenecks.
Appendix A, Helpful Resources, lists links to nice guides that might be useful to a developer.
Appendix B, Helpful Libraries, lists links and describes some popular libraries that might be useful for developing iOS apps.
A free Apple iOS Developer account with Xcode 4.5 running in OS X, and an Internet connection for downloading the RestKit and related libraries.
iOS developers of all levels who are interested in boosting their productivity by using third-party libraries with a willingness to learn how to build RESTful apps using the RestKit framework. Basic knowledge of Objective-C is required and a simple understanding of how Core Data works.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "It heavily uses tables (such as UITableViewController
) to present the loaded data (list of objects) to the user."
A block of code is set as follows:
// in MDatabase @implementation - (NSString *)titleText { return self.name; } - (NSString *)subtitleText { return self.plan; }
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
[self setupObjectManager];
// Setup CoreData stack after Object Manager
[self setupCoreData];
[self setupMappings];
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "A Save button is added to the navigation controller, it triggers the saveAction
method with the following code."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>
, and mention the book title via the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files for all Packt books you have purchased from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]>
with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]>
if you are having a problem with any aspect of the book, and we will do our best to address it.