• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Newbie question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Newbie question


  • Subject: Re: Newbie question
  • From: Howard Moon <email@hidden>
  • Date: Wed, 11 Feb 2009 11:17:14 -0800




IB is supposed to be an aid. I find it a hindrance. Its terminology and operation amount to yet another language. You have to make that language agree with your code. It is easier to define the things I want in the code.

For example, I wanted a dozen buttons arranged in a circle and responding to single and double taps. Without much trouble I was able to write code that placed them where I wanted, made them work as I wanted and allowed me to adjust the location and radius of the circle. Perhaps IB could do this, but it was proving to be too much work to learn it. My needs were simple, IB imposes a big threshold to cross. This is only one example.

David

A very specific and somewhat contrived example, may I add. :) For most UI development tasks IB makes your life a lot easier once you are confortable with the basic concepts of how it works and how to use it. Please don't put it aside as a waste of time.



All examples are specific (and contrived).

There is also a question of portability. Outside the Mac/iPhone world, IB and Objective C are virtually useless. I use ObjC where I must, but keep it to a minimum. I know C++ quite well, and for me it is more powerful, more trustworthy and more universal. Using IB would entangle me in another layer of incompatibility.


I write in purely C++ (for now anyway), and my objects are not tied directly to the IB objects the way you might do if using Cocoa and Objective-C. Instead, I use NIBs to create my window templates, and write code to create the actual windows on the fly (using CreateNibReferenceWithCFBundle) and set and get the control values in code (in almost identical fashion as I've done for years in Windows). So you don't *have* to know anything about how code objects are connected to IB objects, if you don't want. It can still be an easy-to-use tool for WYSIWYG window construction (especially for modal dialogs).


-Howard

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Newbie question
      • From: Howard Moon <email@hidden>
References: 
 >Newbie question (From: TrePos <email@hidden>)
 >Re: Newbie question (From: David Rowland <email@hidden>)
 >Re: Newbie question (From: João Pavão <email@hidden>)
 >Re: Newbie question (From: David Rowland <email@hidden>)

  • Prev by Date: Re: Newbie question
  • Next by Date: Re: Newbie question
  • Previous by thread: Re: Newbie question
  • Next by thread: Re: Newbie question
  • Index(es):
    • Date
    • Thread