Do I need to override the writing methods of NSDocument in subclasses for an application that will only be a viewer for files?

Given that the documentation says “must”, I’d say yes, write a do-nothing write method. Even if it works without one now, and there’s no obvious reason to break that, if it says “must” it’s entirely fair for AppKit to actually require it at some point in future.

Thanks for the answer Jens. – Abizern Mar 28 '10 at 16:53 1 The reason that you "must" override a write method is that the default implementations will throw an exception at the highest level. Overriding one breaks the chain and stops that.

– ughoavgfhw Dec 17 '10 at 4:31.

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.