• 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 Dependency Madness
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Nib Dependency Madness


  • Subject: Re: Nib Dependency Madness
  • From: Chris Hanson <email@hidden>
  • Date: Wed, 27 May 2009 19:01:12 -0700

If you have the source code to the class itself, or the library or framework the class is in, you could create your own Interface Builder palette (for 2.5) and/or plug-in (for 3.0+) that should allow you to at least open a nib containing an instance of the class.

  -- Chris

On May 27, 2009, at 1:58 PM, Kevin Cathey wrote:

If you don't have the palette anywhere, then you will not be able to open the nib, as IB will not be able to decode the object that was in that nib.

Kevin

On 27 May 2009, at 11:38, Waldo Lee Sharvey wrote:

On 5/27/09, Waldo Lee Sharvey <email@hidden> wrote:
Tried that earlier today. The nib doesn't open in IB 2.5.6 either, and
gives the same basic decode error.





On 5/27/09, Andrew Merenbach <email@hidden> wrote:
On May 27, 2009, at 10:04 AM, Waldo Lee Sharvey wrote:


I have an pre-ib 3.0 nib that makes use of a control in a
custom-written palette that a previous programmer seems to have lost.
Whenever I try to open the nib in Interface Builder 3.0, I get a
dialog with the message "Unable to resolve plug-in dependency for
mynibfile.nib". The warning dialog does give me the option of
"Continue" which I'd think would let me continue to open the nib sans
the control, but this only leads to another dialog stating "The
document mynibfile.nib" could not be opened. An instance of
mypalettecontrol could not be decoded". And IB stops dead in its
tracks.


My goal is to salvage/reuse what's left of the nib file keeping
everything intact, with the exception of the problematic palette
control, which I don't really care about anyways. Is this possible, or
is the entire nib file basically fried by virtue of this dependency
and not being able to decode a palette that no longer exists?



You won't be able to open the old file in Interface Builder 3. Try
installing Xcode 2.5, then opening it in Interface Builder 2, then creating
a new nib and copying over the interface from the old one, then save the new
nib and start using it in IB 3 (how's that for a run-on sentence?).


Cheers,
       Andrew


_______________________________________________
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

_______________________________________________ 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

_______________________________________________ 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
References: 
 >Nib Dependency Madness (From: Waldo Lee Sharvey <email@hidden>)
 >Re: Nib Dependency Madness (From: Andrew Merenbach <email@hidden>)
 >Re: Nib Dependency Madness (From: Waldo Lee Sharvey <email@hidden>)
 >Re: Nib Dependency Madness (From: Kevin Cathey <email@hidden>)

  • Prev by Date: Recording Audio
  • Next by Date: Re: Recording Audio
  • Previous by thread: Re: Nib Dependency Madness
  • Next by thread: gmp 4.3.0 and Xcode 3.1.2: _main not found due to architecture mismatches
  • Index(es):
    • Date
    • Thread