In iOS8 the code to show a simple alert to the user is completely changed. UIAlertView is now deprecated:
The new class is UIAlertController and it is not complex to use (more in a minute). But we also want to support our iOS7 users, so wouldn’t it be nice to have a single class handling the different code? This is what we are going to create in this post.
In the previous posts we coded a fully functional JSON parser completed with error handling and independent from the source of the data (the reader).
In the parser we used also a custom operator >>> to invoke a function on an optional (if this is not nil) and return the result.
Now we are going to refine it and, in the way, see other custom operators.
Sometimes it happens to me to observe my code and to say: “no, these things should be made differently”. Then I go into “refactoring”. I think this is an important step of every programmer. Don’t be afraid to refactor (don’t listen to the voice inside you: “… don’t touch that code! Nothing will work correctly after changing this single byte …”): code is something always in evolution (and in test …).
Seeing the code of Part 2 I don’t like two different callbacks to be passed to the start method:
In this post we continue the development of a JSON Parser starting from the previous one: Swift JSON Parser – Part 1.
Let us begin handling the “something went wrong” part.
Error handling strategy
Two types of “bad things” can happen:
This is the first part of a multi-step process in which we will build a JSON parser in Swift.
In this first post we will see, among others, the following swift features in action:
Design Patterns are something we should use not just because they exists, but because they help us to solve a real problem we are trying to fix. The problem I wanted to solve some times ago was the strong coupling of two view controllers when they want to communicate via a segue.
Perfect code does not exist and the swift compiler too has, as of today, some bugs. Continue reading A compiler crash
One of the news of iOS8 is that we can now simply create framework to separate, organize and reuse our code (it wasn’t impossible before but it was more complex).
In some simple steps we will see how to create a version of our PopDatePicker (see A simple iOS PopDatePicker) built as a separate framework.
In this article we will build a simple iOS DatePicker popping up from a text field. This will be the final result:
I just returned from the #Pragma Conference 2014, a very intense meeting hosting some of the best developers of the iOS world.
Special thanks to Ash Furrow (@ashfurrow) for underlining in his session (“Idiomatic Swift”) the importance of sharing what we learn:
