Building Cocoa Applications: A Step by Step Guide

Summary

Well, that’s all we’ve got right now — nothing else works! But marvel at how much functionality we get automatically from the document-based architecture. We’ve done very little to the interface, but already MathPaper has the basic architecture it needs to handle numerous documents simultaneously.

We did, however, do a lot of work on our back end, Evaluator, in the first part of this chapter. In fact, Evaluator is now prepared to perform our requested calculations (as we saw when we ran it in a Terminal window), but it needs to be connected with the interface to work within the document-based architecture. In the next chapter, we’ll tie the front-end interface and the back end together. To do that, we’ll have to make some modifications to the MathDocument class and create the PaperController class. We’ll also need to learn about some new Cocoa classes specifically designed to handle interprocess communications.