• 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: Nib exploded (according to SCM)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Nib exploded (according to SCM)


  • Subject: Re: Nib exploded (according to SCM)
  • From: Jeff Johnson <email@hidden>
  • Date: Mon, 5 Oct 2009 15:04:11 -0500

On Oct 5, 2009, at 2:31 PM, Jonathan Hess wrote:

On Oct 5, 2009, at 11:24 AM, Jeff Johnson wrote:

Hi David.

I've experienced the same thing. Your nibs were originally created with Interface Builder 2, right?

There are three different formats: NIB 2.x, NIB 3.x, and XIB 3.x. Support for NIB 2.x in IB 3.2 is extremely limited at best. IB 3.2 can open them, but it can't save them, it automatically transforms them into NIB 3.x, and sometimes messes up the nib a bit in the process. What you're seeing in svn is the switch from NIB 2.x to NIB 3.x.

Yes, IB 3.2 automatically updates NIBs from the 2.x format to the 3.x format. And the files in the file package of a 3.x NIB file are different. They only include "keyedobjects.nib", and "designable.nib", and not "info.nib" and "classes.nib". If it "sometimes messes up the nib a bit" could you please file a bug report at bugreport.apple.com? However, I think what you're saying is just that the contents of the NIB package change on disk. If so, that's expected.


One thing to watch out for is that the the "development target" of a NIB 2.x file that's auto-upgraded will be set to IB 3.2, which will make it only openable on newer version of Interface Builder. You can reset this to a lower version in the document info panel, which is reachable from Windows menu.

I think you're pretty much out of luck. My recommendation is to take the plunge now and switch all of your nibs to xibs. Ideally, you would do this in IB 3.1 on Leopard instead of IB 3.2 on Snow Leopard, to avoid new 3.2 regressions.

Switching to XIB files is a great suggesting, they integrate with SCM systems like Subversion much better. Which new regressions are you referring to?


Jon Hess

Hi Jon.

I was indeed referring to the "Development Target" problem.

I may have also come across a case where "Wants Core Animation Layer" got magically set, but I haven't had time to investigate that further yet.

-Jeff

_______________________________________________
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: Nib exploded (according to SCM)
      • From: Jonathan Hess <email@hidden>
References: 
 >Nib exploded (according to SCM) (From: David Dunham <email@hidden>)
 >Re: Nib exploded (according to SCM) (From: Alastair Houghton <email@hidden>)
 >Re: Nib exploded (according to SCM) (From: David Dunham <email@hidden>)
 >Re: Nib exploded (according to SCM) (From: Jeff Johnson <email@hidden>)
 >Re: Nib exploded (according to SCM) (From: Jonathan Hess <email@hidden>)

  • Prev by Date: Xcode 3.1 doesn't jump to error location
  • Next by Date: Re: Nib exploded (according to SCM)
  • Previous by thread: Re: Nib exploded (according to SCM)
  • Next by thread: Re: Nib exploded (according to SCM)
  • Index(es):
    • Date
    • Thread