Re: Interface Builder can't identify plugins when opening old NIBs
Re: Interface Builder can't identify plugins when opening old NIBs
- Subject: Re: Interface Builder can't identify plugins when opening old NIBs
- From: Mark Douma <email@hidden>
- Date: Mon, 19 Nov 2007 09:23:05 -0500
On Nov 10, 2007, at 3:37 AM, Jens Miltner wrote:
Hi,
I've rewritten our old IB palettes as Interface Builder plugins for
the new Leopard Interface Builder.
However, whenever I open a NIB file that was generated by the old
Interface Builder, containing some of our custom objects that
require the plugin, IB will tell me it can't find the appropriate
plugin, asking me to locate it.
My new plugin is definitely loaded in IB and when I press
"Continue" (without locating the plugin), the NIB loads just fine
and I can edit our custom objects properties, so I don't really
understand why IB insists on not being able to locate the plugins?
I also tried to save the NIB once with the new IB, but when opening
it again, IB will still prompt me for the plugin.
How can I make sure IB will associate my new plugin with the custom
objects stored by the old IB?
Thanks,
-jens
Just went through this myself.
When you saved a .nib file in with a palette in IB 2.x, inside your
nib would be the mandatory Sample.nib/keyedobjects.nib, but also a
Sample.nib/data.dependency file with contents similar to:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd
">
<plist version="1.0">
<dict>
<key>IBPaletteDependency</key>
<array>
<string>MDLevelIndicator</string>
</array>
</dict>
</plist>
---------------------------------
It looks like it's the presence of this file that causes Interface
Builder 3.0 to balk upon opening the nib file. Once I remove this file
from the older nibs, IB 3.0 will open the files just fine.
At the same time, and even better, it looks like Interface Builder 2.x
is still able to open the same nib file if the data.dependency file is
removed.
My guess is that resaving the file from IB 3.0 still won't remove that
pesky data.dependency, and so IB 3.0 continues to object.
Anyway, hope this helps....
Mark Douma
---------------------------------------------------------------------------
Mark Douma
Grand Rapids, MI, USA
email@hidden
http://homepage.mac.com/mdouma46/
---------------------------------------------------------------------------
_______________________________________________
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