FROM : Shawn Erickson
DATE : Thu Aug 03 20:16:59 2006
On 8/3/06, Paul J. Lucas <<email_removed>> wrote:
> I have a customized NSSavePanel that offers the user more
> options for saving a document. I have the custom stuff in a
> nib file. One of the custom items is a pop-up menu. For one
> selection of the menu, there are no additional user-settable
> controls; for the other selections, there are more controls.
>
> The way I have been doing this is to have a Custom View object
> and then programmatically swapping the contents of the custom
> view.
>
> In peeking at other Mac applications, e.g., Safari, it has each
> set of preferences as a seperate nib file.
>
> So I'm wondering: is it better to do what I'm doing (have custom
> and seperate views in the same nib file) or have a different nib
> file for each view?
>
> It would also be nice to have it so that the view switching
> happens allo inside the nib and that I programatically don't
> have to do anything.
>
> Advice? Examples?
Likely one nib is sufficient but the real answer to that aspect of the
quest depends on how you want to implement things... that can feedback
into who best to split things up, possible across a nibs.
Consider using a tabless tab view with each tab in that view matching
a selection option of popup menu. The popup menu could then drive the
selection of the tab to show.
-Shawn
DATE : Thu Aug 03 20:16:59 2006
On 8/3/06, Paul J. Lucas <<email_removed>> wrote:
> I have a customized NSSavePanel that offers the user more
> options for saving a document. I have the custom stuff in a
> nib file. One of the custom items is a pop-up menu. For one
> selection of the menu, there are no additional user-settable
> controls; for the other selections, there are more controls.
>
> The way I have been doing this is to have a Custom View object
> and then programmatically swapping the contents of the custom
> view.
>
> In peeking at other Mac applications, e.g., Safari, it has each
> set of preferences as a seperate nib file.
>
> So I'm wondering: is it better to do what I'm doing (have custom
> and seperate views in the same nib file) or have a different nib
> file for each view?
>
> It would also be nice to have it so that the view switching
> happens allo inside the nib and that I programatically don't
> have to do anything.
>
> Advice? Examples?
Likely one nib is sufficient but the real answer to that aspect of the
quest depends on how you want to implement things... that can feedback
into who best to split things up, possible across a nibs.
Consider using a tabless tab view with each tab in that view matching
a selection option of popup menu. The popup menu could then drive the
selection of the tab to show.
-Shawn
| Related mails | Author | Date |
|---|---|---|
| Paul J. Lucas | Aug 3, 20:11 | |
| Shawn Erickson | Aug 3, 20:16 | |
| Paul J. Lucas | Aug 3, 20:39 | |
| Michael Watson | Aug 4, 07:46 | |
| Paul J. Lucas | Aug 5, 04:01 |






Cocoa mail archive

