Comments on: NSViewController, the New C in MVC - Pt. 3 of 3

By: cathy

cathy — Thu, 25 Sep 2008 09:25:00 +0000

Hi Dennis,

No, you still need the actual view itself - either NSSplitView or RBSplitView. You can use a controller to lay out two views next to each other, but if you want the interactive features of a split view - mainly the movable divider - you’ll want to use what you have now.

Good luck!

By: Dennis Christopher

Dennis Christopher — Wed, 24 Sep 2008 14:19:47 +0000

Hi Cathy,

Thanks for this series–it’s great for us Cocoa GUI developers.

I have a legacy project begun with a single window (non-doc based) application that uses RBSplitView which is said to be an improvement over the built-in NSSplitView. I find it a bit complicated to use. Can you comment on how it may compare to the XS framework, and specifically whether the latter is meant to handle split views as well?

By: name

name — Mon, 01 Sep 2008 03:39:23 +0000

Hi!,

By: name

name — Mon, 01 Sep 2008 01:33:17 +0000

Hello!,

By: name

name — Mon, 01 Sep 2008 01:32:57 +0000

Good day!,

By: professional

professional — Sun, 20 Jul 2008 10:39:45 +0000

Hello. I think you are eactly thinking like Sukrat. I really loved the post.

By: Duncan Robertson

Duncan Robertson — Mon, 23 Jun 2008 19:34:07 +0000

I attended wwdc for the first time last week. Although I got lots from the conference, the thing I find that advances my knowledge quickest, is when people trigger things that have been whirling in your head to make you go aaahh .. I see … These 3 articles from Jonathan and yourself have triggered such a moment. Thankyou to you both.

By: jerry

jerry — Mon, 16 Jun 2008 16:32:58 +0000

love to drop an email, but I cant find your addr. google did turn up some interesting leads — were you looking for a powerglove serial adapter back in 2004?

By: Cathy

Cathy — Sun, 15 Jun 2008 16:25:35 +0000

Hi Jerry,

Been away from my computer for the past week (WWDC). Glad to see that you seem to have solved your problem. I’ll be sure to address the issue of a non-document based application with the next update to the view controllers.

Thanks for sharing your solution and if you have more questions, don’t hesitate to send me an email.

By: jerry

jerry — Sun, 15 Jun 2008 05:58:34 +0000

I figured out how to make it work with my non-document app, but not with the XS stuff. I’m not quite clear on why that is needed as my solution seems to work ok. Does the XS/Resonder stuff address the layout issue?

I posted my solution back on the cocoa-dev list (june 14 2008 postings)
It required a bit of code in my AppController specifically

@interface AppController : NSObject {
IBOutlet NSWindowController *windowController;
NSViewController *viewController;
}

@implementation AppController
- (id)init
{
if ( self = [super init] )
{
// substitute yourView’s nib + controller names in next line
viewController = [[TheViewController alloc] initWithNibName:@”TheView” bundle:nil];
}
return self;
}

- (void)awakeFromNib
{
[viewController.view setFrame:[windowController.window.contentView frame]];
[windowController.window.contentView addSubview:viewController.view];
}
@end

plus adding an NSWindowController, putting both into the MainMenu.nib and connecting them there.

Then in TheView.xib I set the FileOwner to be TheViewController and connect its view in IB… and set up all the other widgets/connections.

That seems to work and can be copied/shared with other apps.