Question

I am quite new to Cocoa and to iPhone programming.

I am using the Xcode Utility Application template to implement a simple app that has:

• a view with a text field to collect a username
• a view with a connect button to start a connection to a remote site using the
  username to get some data via HTTP. The data will be presented as a text string on the screen.

I think this represents my VIEW in the MVC pattern.

I created a simple class to store the username and to do all connection work that represents my MODEL and instantiated it inside the AppDelegate.

Here a really simplified sketch:

It is not really clear to me how can I get data nested deep into subviews (username) or how can I trigger actions in nested parent views (connect button).

My question is:

What is the best/cleanest way to implement this architecture?

How do I implement the CONTROLLER?

Thanks in advance for any help,
Paull

Answer 1

Updating my answer based on comment:

It’s in most cases ok to have state in your controller. Like an array or an instance of whatever modelobject you are writing an application for.

I would keep the model object clean of any networking code and put that in the Controller instead though. In this case the ViewController where that connection action is triggered.

Original answer:

It is not really clear to me how can I
get data nested deep into
subviews(username) or how can I
trigger actions in nested parent
views(connect button).

With the utility application template you already have a couple of ViewControllers.

To get references to your UI inside your controllers you need to declare IBOutlets and connect them inside Interface Builder. To respond to actions you need to declare and implement IBActions in your ViewControllers and hook them up in Interface Builder as well. Which you do in Connections pane (2nd from left) in the inspector.