I'd have to say that NSDocument is a slightly odd choice for a browser app. The Cocoa document architecture is really designed for editor-type applications that load and save files from disk, whereas there is no real concept of a "document" in a browser.
I'd have to say that NSDocument is a slightly odd choice for a browser app. The Cocoa document architecture is really designed for editor-type applications that load and save files from disk, whereas there is no real concept of a "document" in a browser. Why not just implement a main controller that manages a bunch of window controllers?
What does the document architecture give you that you feel your app needs?
Thanks for the quick reply. I have tried looked into that before, but that seems a bit more complicated than the NSDocument way. Do you know any sites that can teach that?
– theAmateurProgrammer Aug 23 '11 at 0:41 1 Well, you just need to implement a subclass of NSWindowController that manages your browser window. Then you would have some main controller class that manages an NSMutableArray containing instances of your NSWindowController subclass. Your main controller can respond to menu items like "New Window" by instantiating new instances of the window controller and displaying their windows.
– Rob Keniger Aug 23 '11 at 8:12.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.