Question

I have a UInavigation controller, UITabelView with customized UITableViewCells, which I will create 4 different xib files for that custom cells, which I will get user input from them.

I am a bit confused here, it is said every view should have its own controller in Iphone, so I will push a new subclass of UItableviewcontroller on stack for each page(UITableView), and in theory it should be responsible for the delegations of the uicomponents on that table. But each UItableVIew consists of customized cells(xibs),

So
-Do I also need a different controller for each customized cell?

-If so, where can I put the delegation methods of those ui components on the custom cells?

-is this hiearchy correct?

UINavigationController–> UITableViewControllersSubclasses –>customUITableViewCellcontrollers

Answer 1

No. You do not need a different controller for each customized cell.

it is said every view should have its
own controller in Iphone

This is not true. Actually, a view controller typically manages a view hierarchy rather than a view. Although the view controller is associated with a view, this view is just the root of the whole view hierarchy of a screen’s worth of content (in iPhone applications).

From View Controller Programming Guide for iOS:

Each view controller is responsible
for managing a discrete part of your
application’s user interface. View
controllers are directly associated
with a single view object but that
object is often just the root view of
a much larger view hierarchy that is
also managed by the view controller.
The view controller acts as the
central coordinating agent for the
view hierarchy, handling exchanges
between its views and any relevant
controller or data objects. A single
view controller typically manages the
views associated with a single
screen’s worth of content, although in
iPad applications this may not always
be the case.