• 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: Animation when adding view. Where should view come from, NIB or programmatic?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Animation when adding view. Where should view come from, NIB or programmatic?


  • Subject: Re: Animation when adding view. Where should view come from, NIB or programmatic?
  • From: "Rob Napier" <email@hidden>
  • Date: Fri, 21 Mar 2008 12:15:44 -0400

On Thu, Mar 20, 2008 at 3:53 PM, David <email@hidden> wrote:

> I think this is a basic question.In interface builder you can specify
> animations which occur when adding a view. Question is, where does the
> view
> typical come from? It seems desirable to be able to design a potentially
> complex view in IB, obtain a reference to it and use it for animations. Or
> is it assumed that you're programmatically creating the view?


The view can come from many places. It can come from the main NIB by using a
IBOutlet to keep track of it. You can create it in code, or you can stick
the view in its own NIB and load it with an NSViewController (or a
hand-rolled view controller if you're pre-Leopard). There's no deep
assumption here about where the view comes from. I personally find it handy
to have several small NIBs rather than one complicated NIB, but it is a
matter of style, preference and your particular problem. I also personally
like to keep my NIBs very simple and move most complexity into the code
because I find it easier to manage that way, especially with multiple people
working on the same project. Again, though, that's just my preference. Cocoa
is designed to handle any of these approaches.


I've been trying to find similar examples to popup windows and found some
> discussions stating that you can't find a window in the nib and that you
> should have a separate NIB per window.


It is often useful to create a separate NIB per window (I usually do), but
you can certainly find a secondary window in a NIB if you tie it to an
IBOutlet variable. You can even walk a NIB and find the window, as described
here:

http://developer.apple.com/documentation/Cocoa/Conceptual/LoadingResources/CocoaNibs/chapter_3_section_6.html

This last technique is useful if you're trying to dynamically load NIBs at
runtime that are not known at compile time (such as if you have a plug-in
architecture). It's not the normal way to find a window.

-Rob

--
Rob Napier -- Software and Security Consulting -- http://robnapier.net
"Those who would give up essential liberty to purchase a little temporary
safety, deserve neither liberty nor safety." -- B. Franklin, Printer
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >Animation when adding view. Where should view come from, NIB or programmatic? (From: David <email@hidden>)

  • Prev by Date: Re: Best Way To Lookup From a Huge Table
  • Next by Date: Re: Leopard NSTableView Cell and single click editing
  • Previous by thread: Animation when adding view. Where should view come from, NIB or programmatic?
  • Next by thread: extract text from image
  • Index(es):
    • Date
    • Thread