Re: IBPlugin embedding question
Re: IBPlugin embedding question
- Subject: Re: IBPlugin embedding question
- From: Alexander Spohr <email@hidden>
- Date: Thu, 25 Jun 2009 09:46:26 +0200
Am 25.06.2009 um 00:46 schrieb Doug Scott:
I have developed a small series of custom IBPlugin framework
projects, two of which include other custom IBPlugin objects. Here
is a quick overview of the hierarchy.
- IBPlugin-A: A view with a custom API.
- IBPlugin-B: A view which adds a set of controls to manipulate the
embedded IBPlugin-A view via its API.
This sounds like A and B should be one IB-Plugin?
- IBPlugin-C: A view which embeds two IBPlugin-B views side by side.
And just throw C in as well.
Why do you have to have three plugins where it looks like you just
need one?
Although I'm quite happy with the end results of being able to
utilize nested IBPlugins of ever encreasing complexity [...]
I am always unhappy if my code gets too complex. I often just take
some time to clean up my code. :)
Nib files seem to be only a static 'snapshot' of a point in time
during the development processes,
This is exactly what they are: Frozen objects.
and not really part of a modern dynamic build system.
Why? Because they work different than code? They are different because
they are just data.
Did I miss your point somewhere?
atze
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden