Re: Interface Builder plug-in 'chicken and egg' problem
Re: Interface Builder plug-in 'chicken and egg' problem
- Subject: Re: Interface Builder plug-in 'chicken and egg' problem
- From: "Jack Nutting" <email@hidden>
- Date: Tue, 11 Nov 2008 14:22:24 +0100
On Tue, Nov 11, 2008 at 1:43 PM, Cathy Shive
<email@hidden> wrote:
It was suggested to me that I use a custom NSView in the inspector and set its class to KTGradientPicker. This works great and now my Plugin builds on the first go.
But I still have the same problem in another Xcode project that has .xib files that use my plug-in.
Basically, I want to share a project that uses my plug-in in its .xib files. I expect that the other person can build and run from Xcode with no problem and that when they try to open the .xib files, then they'll get an error from Interface Builder telling them that they need to install the plug-in.
This is how it works with .nib files, right? I still have old .nibs that use old IB2 palettes that don't even exist anymore. The Xcode project they're used in doesn't care at all. I just can't open them in Interface Builder.
Why does Xcode try to compile .xib files ( CompileXIB)instead of just copying the file into the resources directory like it does with .nib files? Is there something I can do to prevent that part of the build?
I'm simply trying to avoid making people install the framework and plugin just to run the project. It makes sense that they would have to do that if they want to look at the .xibs in IB, but not just to build the Xcode project without errors.
I'm not at all sure about this, but I think that the reason it always wants to compile .xib to .nib is that .xib is still not a "native" format, or at least not the preferred format; I don't know if the bundle system can even open them at runtime, the way it can open .nib files.
Which seems to suggest a sort of workaround: How about including the compiled .nib files with your project, instead of the .xib files?
_______________________________________________
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