Re: Creating NSViews with code.
Re: Creating NSViews with code.
- Subject: Re: Creating NSViews with code.
- From: j o a r <email@hidden>
- Date: Thu, 17 Feb 2005 07:58:58 +0100
On 2005-02-17, at 05.47, Daniel Jalkut wrote:
I think it's a bad idea to (ab)use tab views like this. Whatever the
number of configurations (N), you will have (N * N-1) wasted instances
of tab view UI content views. I agree with the proposition that one
should not worry about performance until it's measurable, but in this
case it's really just as easy to have a blank slate into which you set
a view loaded from a specific nib.
Two things:
1) I think that's a completely irrelevant "optimization" (At least as
long as we - like in this case - talk about a limited and reasonable
number of configurations.).
That said, if that's how you want to spend your engineering resources,
you could always:
2) Keep the content views of the individual tabs in the tab view in
separate nib files that are loaded when the user first switch to the
tab.
A tab view is IMO an excellent UI element for something like this. It
basically provides all the subview-management for you, so you don't
have to write any code to do that.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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