the best way to implement a document based app that also manages documents?
the best way to implement a document based app that also manages documents?
- Subject: the best way to implement a document based app that also manages documents?
- From: John Clayton <email@hidden>
- Date: Mon, 30 Dec 2002 19:24:50 -0500
This is a similar case to what we have in ProjectBuilder, a project
document that manages other documents.
So, if I create a document based app using the ProjectBuilder set up, I
get an app capable of opening documents, etc. I understand I also get
a document controller, a window controller and the methods that come
along with NSDocument. If I get this correctly, The DocumentController
will handle most of the messages sent to FirstResponder from menu
items. This works great for the parent document. But now I am
wondering how to manage the child documents. All the usual messages
sent to FirstResponder get intercepted first by the objects set up in
PB, so they never seem to reach the children. Ok, I think, then should
I subclass NSDocument for the children at all? Should I then create my
own document controller and add it's methods to FirstResponder and wire
them from the menu items in IB? Or, is there some way to route the
messages to the child documents such that the document controller knows
on which document to invoke the methods? Is this simply a matter of
having the child documents be FirstResponder?
I wonder if I'm making any sense here ... sigh. Does anyone know of an
example of such an application where the source code is available?
Your help is appreciated. Thanks.
Regards,
John Clayton
----------------------------------
email@hidden
----------------------------------
Ask a question, remain a fool for five minutes
Don't ask a question, remain a fool forever
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.