IPhone xcode code vs interface builder?

If constructing everything in code is working for you, then great. Personally if it can be done in IB it's done in IB I'd be surprised if there's a best practice for this; everyone will have their opinion and preference I like to do UI related work in IB - if i'm dealing with presentational concerns I like to be in an environment that offers immediate visual feedback. It also cuts down the amount of boiler-plate code that you would have if constructing everything programmatically That said you can't do everything in IB.

There are times you'll fall back on programatically constructing or laying out a view A little knowledge of both approaches goes a long way.

If constructing everything in code is working for you, then great. Personally if it can be done in IB it's done in IB. I'd be surprised if there's a best practice for this; everyone will have their opinion and preference.

I like to do UI related work in IB - if i'm dealing with presentational concerns I like to be in an environment that offers immediate visual feedback. It also cuts down the amount of boiler-plate code that you would have if constructing everything programmatically. That said you can't do everything in IB.

There are times you'll fall back on programatically constructing or laying out a view. A little knowledge of both approaches goes a long way...

Possible duplicate of: stackoverflow.com/questions/3438804/ipho... at the end of the day its whatever you feel more comfortable doing. IB is horrible in my opinion, programming takes more effort - more thought. :).

P (i'm being facetious, to each their own). – dannywartnaby Sep 21 '10 at 12:40 sorry my answer doesn't read very well... I was giving two sides of a coin read as "IB is horrible BUT programming takes more effort - therefore its whatever you feel more comfortable doing". :) Thats what I'm saying - you end up spending all your time just trying to get the layout spot on and budging something 1px to the right, building, clicking to that view looking going back budging it 1px again etc etc gets very tiring very quickly.

– Thomas Clayson Sep 21 '10 at 13:08 MY reason for not using IB is that it is annoying when implementing methods and trying to do other things. Mixing IB and programming (espcially anything that uses subviews of the view from IB) gets annoying and tedious. Separating the view from the methods was a good idea on paper - but integrating it just annoys... well, me at least.

:) – Thomas Clayson Sep 21 '10 at 13:10.

I usually use IB, get immediate visual feedback and make the layout looks exactly easier. Only in one case that I have to give up with IB is performance with UITableView scrolling. In this case, the best solution I can find is to write code to draw everything in the cell using code.

This makes the performance much better. Generally, I recommend to use IB until you have some specific requirements like performance or you need to have really much control over the view.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.