>> > > As a general rule of thumb, then, would you say a developer *should* use IB > to design the interface, or is manually building a UI with careful > consideration for size (due, for example, to localization in another > language) an acceptable practice? I realise there are times when manually > building is just best, as in my iOS project, but I don't want to get into bad > habits. >
Super attitude you have towards trying to learn the platform. I would say, to your last question, for OS X apps a developer *should* design the interface in IB, it's how it was designed to work, there's a sort of expectation that you build with NIBs. You can certainly customize things in code later but starting with the thought "I'll do this in IB" and only going into code if you really find an unusual case where IB just doesn't cut it is a good habit approach. For iOS I know that right at the start, code-built UIs were quite common because .. actually I'm not sure why .. a lot of books and articles did it that way so people did it that way when IB would have done some of the heavy-lifting for them. I did it too, my first app, when I look at it now, I see how hard I made life. Now I do what I would do in OS X, I use IB for as much of the interface as I can, especially as now that platform has storyboards which I find helps me. I'm still not averse to dumping a placeholder view I can't build in IB (especially since Apple took away IB plugins) and filling that up that in code when the view loads, but I find myself doing that less and less these days. I possibly have very simple apps. If you can use IB, use it. If you can't use it, try one last time to use it, then do it another way. That's what I think at least. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
