From working with NSViewController
in Leopard, I can tell you that its functionality is very basic, and that you should be able to replicate it with fairly minimal effort.
Essentially, it has a view
property/outlet, and an initWithNibName:bundle:
method. Beyond that, it doesn't do anything especially fancy. It has some convenience things, like adopting NSEditor
, and a representedObject
property. You should be able to bang out an equivalent class in an hour or two.
Now, what you will give up if you do this is compatibility with later versions of Cocoa. Eventually, you'll probably drop 10.4 support and you'll be left with your class and the real NSViewController
. When that happens, I'd recommend re-basing your custom view controller on Cocoa's NSViewController
. If you've named the properties with the same names/data types as NSViewController
, you should only have to drop the properties and methods you've declared yourself.