OK I agree it would be clearer given the changes made, if it were Controller::setViewOption('viewClass', <>). But some of the discussion above was around whether all the vars that I've move into setViewOption() should be directly settable on Controller as they were before, using __set() magic. I don't think they should be, as its confusing, but will wait for consensus on this before I make any change to this one.