Posted on
March 9th, 2012
Which framework should I choose for this application? - This was the most common question which I used to think before starting any application. But since the time I am working on iOS, I hardly remember when did I ask this. As per Apple's technical guidelines, you 'always' have to stick to the default framework. Fortunately or unfortunately, the default framework is the only framework made available by Apple. But what is meant by 'only framework'? Read more »
Posted on
January 22nd, 2012
XML Parsing on iPhone/iPad - Is that something your current sprint revolves around? Well if it does, this blog might help you. While parsing XMLs on device, we need to look into factors like performance and memory consumption. While googling, i found couple of XML parsing APIs including Apple's native NSXMLParser. NSXMLParser looked like this is all i need. But my requirement was also to 'write' xmls making sure that i do not compromise on performance and memory. On googling more i found couple of APIs which can provide me XML writing capabilities. I chose to explore libXML2 and KissXML.
Read more »
Posted on
December 28th, 2011
iOS5 have introduced Storyboards, using which you can connect your static views and easily prepare a navigation workflow. Prior to iOS5, we used to have .xib files for every view controller. With Storyboards, all the views (and their controllers) are in one single file with an extension .storyboard. View navigation using storyboard happens with Segues. Segues define a way using which you can define things like transition type, data flow, etc. To navigate from one view to another, you simply need to CTRL CLICK and DRAG from the source view controller to the destination view controller. For example, if on a click of a button you want the next screen to show up, CTRL CLICK and DRAG from that button to the desired view controller. When you release, you can see three options – PUSH, MODAL and CUSTOM. Push and Modal are self explanatory. But when do you want to use Custom Segues? Before the answer, lets have a look at a use case:
Read more »
Posted on
September 11th, 2011
One of the pain points in GIT was resolving merge conflicts. I have highlighted ‘was’ because at the end of this blog you will find your life easy the next time you encounter merge conflicts. Working with GIT in agile development increases the probability of merge conflicts, and the reason behind is straight forward – Parallel Development. As I mentioned in my earlier blog, there are lot of advantages of using GIT branching model. But one of the pain points I mentioned was resolving merge conflicts. One has to manually open the files and identify conflicts. In this blog, I will share how you can configure and open a 3-way merging tool to identify your merge conflicts. Read more »
Posted on
May 15th, 2011
We have been working with GIT branching model for a long time now. GIT allows you to maintain different branches in your codebase. It is a developer's choice when to make/merge branches. We, as a team decided on certain guidelines as to when make/merge branches. Apart from the user story specific branches, we had Development and Master. The concept of Development branch was introduced to keep our Master stable and be in a state to give release-ready builds. All the user story branches are merged into Development. Read more »
