• 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: Writing application without Interface Builder
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Writing application without Interface Builder


  • Subject: Re: Writing application without Interface Builder
  • From: Erik Buck <email@hidden>
  • Date: Tue, 18 Jul 2006 19:22:56 -0700 (PDT)

Interface Builder does not do anything that you can not do with code.  Interface Builder allocates and initializes objects, sends messages to those objects in response to your interactions through IB's GUI, and then archives the objects and connection info into a nib file.  When your application runs, all it does in unarchive the objects and connection info from the nib file and use them.

  See http://www.stepwise.com/Articles/Technical/FreezeDriedObjects.html for a nice brief explanation.

  P.S. On the whole, Apple's Cocoa documentation is excellent, and frankly, when you are using aspects of the framework that have existed for 13+ years, you can be assured that lots of people have figured it out from the documentation before you.

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

This email sent to email@hidden

  • Follow-Ups:
    • Re: Writing application without Interface Builder
      • From: Sherm Pendley <email@hidden>
  • Prev by Date: Re: OpenGL with Cocoa?
  • Next by Date: Virtual concept in Objective-C
  • Previous by thread: Re: Writing application without Interface Builder
  • Next by thread: Re: Writing application without Interface Builder
  • Index(es):
    • Date
    • Thread