Re: IB Palettes, custom classes and the need for Frameworks
Re: IB Palettes, custom classes and the need for Frameworks
- Subject: Re: IB Palettes, custom classes and the need for Frameworks
- From: Tim Lucas <email@hidden>
- Date: Thu, 13 Jan 2005 16:07:03 +1100
Thanks Gregory,
On 13/01/2005, at 2:05 PM, Gregory John Casamento wrote:
But they are using it in the nib file. A nib file is just a set of
encoded
data which is used to instantiate the objects with the appropriate
connections
(i,e. the ones made by the user in IB). In order to do this you
*must* have
the classes you are unarchiving from the nib file linked into the
application
for you to be able to use it.
I thought that may be the case.
Having to remember to add a framework to your project everytime you
use
a certain IB palette just seems wrong.
It's not wrong, for the reason cited above. :)
I meant "wrong" from an ease of use point of view... though I
understand that we are dealing with developers who should probably
learn why it's necessary anyway.
Is there a way to make this easier for the developers, or is this the
only way?
It is the only way.
Unless IB automatically added the relevant framework to your xcode
project ;)
Also, one suggestion, you should be linking your palette
with the same framework you created.
Cheers. I hadn't noticed earlier but I was linking directly.
- tim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden