- (void)discardEditing
{
[self.viewControllers makeObjectsPerformSelector:@selector(discardEditing)];
}

-(BOOL)commitEditing
{
BOOL success = [super commitEditing];

for (NSViewController *viewController in self.viewControllers) {
success &= [viewController commitEditing];
}

return success;
}

- (id)initWithWindow:(NSWindow *)window;
{
if (![super initWithWindow:window])
return nil;
self.viewControllers = [NSMutableArray array];
return self;
}

I’m trying to implement an application that will allow creating an arbitrary number of chamber music groups using nested collection views (a collection of views for each group, and also a collection of views for each member of the group), and so was thinking of using an NSViewController to contain the collection view information. The nested view seems to match the design principles of XSViewController well.

However, I am using Core Data, and cannot figure out how to integrate the two. A simple example application with NSPersistentDocument and XSViewController would be extremely helpful to me. I need to somehow get the managedObjectContext passed into the child XIB files.

Needless to say, I’m relatively new to Mac development, my previous expertise is in PHP and C. The first Mac app I wrote is a programmable metronome, which my quartet used to learn Elliiot Carter’s 4th string quartet.

Any help is appreciated. The program will be used to put groups together each week at a summer music program, and detect conflicts in both group members, repertoire, and scheduling. The current program I am porting is based on an AJAX javascript/PHP/mysql system, but Core Data document-based is a better fit for this application.

There is a typo in the Copyright text,” Conrtollers”.
‘For example, “Contains “View Conrtollers” by Jonathan Dann and Cathy Shive” will do.’ I was kinda tempted to use that exact spelling in my software :-).

I explained the decision a little more in a recent post:Simple NSViewController Sample Projects - towards the end of the page.

What were your reasons for choosing to implement the responder chain such that the view controllers are inserted around the level of the window controller? UIKit takes the approach that each view controller is inserted in between the view it manages and the superview.

I can see the pros and cons of both and wondered why you chose this design over the other. Or indeed, if there was even a third design considered?