custom palettes (2)
custom palettes (2)
- Subject: custom palettes (2)
- From: Tristan lorach <email@hidden>
- Date: Wed, 20 Mar 2002 17:44:41 +0100
Thanks to David Remahl I managed to use Custom palettes. Maybe it could
be usefull for anybody else :
- create a custom palette as you could find in various examples
- add a new TARGET : a Framework. And put various classes that the
palette exposes. You may check for public headers, too
- You may include this new generated Framework in the application which
is using your palette.
Another way is to only insert *.h & *.m files of the palette's classes,
but this way of doing would not be right if ever you wanted not the
others to know what's inside your code...
I was interested in the way that these controls are outside of the
application which use them. Thus allowing to provide some new improved
versions of controls without the need to build projects that are using
them.
In our case, the part of the palette built as a framework allow us to
handle this.
But I noticed that the Palette-part doesn't allow us to do it : when you
drop a palette object into your Nib project, it will make a full copy of
it : no reference to any external resource is possible.
Then, if you changed your palette in the way it is displayed, you won't
get back any change inside applications using it until you decide to
remove the old one and drop the new one by using the Interface builder
on each application using this palette...
Tristan
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.