CODEWITHSUNDEEP
objective-cios
nullfox
nullfox

Reputation: 607

Splitting up large iOS View Controller?

I have a view table view controllers that contain a fairly large set of functionality and many lines of code - Is there an accepted way to split the single controller into multiple controllers or objects to help make it more readable and easier to navigate/maintain?

Upvotes: 2

Views: 588

Answers (2)

Jaybit
Jaybit

Reputation: 1864

Yes there are ways to make your code more modular. First off using a UITableView there is a Delegate and a DataSource. You can create separate NSObject classes for each of these.

The DataSource class would contain things like tableView:cellForRowAtIndexPath: and tableView:numberOfRowsInSection:. With the full list here: UITableViewDataSource.

The Delegate class would contain things like: tableView:didSelectRowAtIndexPath: and tableView:willDisplayCell:forRowAtIndexPath:. WIth the full list of here: UITableViewDelegate

It really matter on where most of your code is. If its all in creating a custom cell create a class for that and just send it the info it needs to build its self.

Upvotes: 4

mdominick
mdominick

Reputation: 1319

You could just use two subclasses of UIView (or tableView depending on what your are doing) to make the View code a bit more modular. Without more details on what you are attempting it is hard to be more specific.

Upvotes: 1

Related Questions