0

I am using ECSlidingViewController, a library that gives a side-drawer effect. My application opens to a (navigation controller holding a) table view controller of 'Nearby' results, and the cells segue to a scroll view controller.

The hidden left menu is a table view controller (of different class) with a few options, 2 of which are other table view controllers that will use the same layout, cell prototypes, and detail scroll view as the table view seen on startup.

I would like to know if it would be better design to make a more generic tableView with some sort of property like an enum'd typeOfDisplay, which lets me conditionally manage different nuances like populating cells from server/CoreData, navbar titles, sort order, toggling auto-updating, editability, etc. - OR - if I should make a NavigationController->TableViewController->ScrollViewController for each different view controller (A 'Nearby', 'Featured', and 'Saved')

I'd like to reuse my table view because the cells/display/detail will be identical, but the methods for populating the table are different, and I don't want to make something that's difficult to modify.

Edits -

If you are familiar with table views inside tab-bar contollers, the implementation details should be nearly the same.

user
  • 3,388
  • 7
  • 33
  • 67

2 Answers2

3

It's better to put view configuration into view controller. But there can be ways to reuse the configuration actions.

I have ran into the same situation like yours. And I decided to use Strategy Pattern to refactor my controllers. I put all the data related stuff into a TableDataManager class which conforms to the UITableViewDataSource and UITableViewDelegate protocols and I applied polymorphism to it to configure the data in cells and the appearance of the UITableView under different circumstances at runtime.

All the identical actions are implemented in TableDataManager, and nuances are overridden by subclasses of TableDataManager. By assigning a proper subclass of TableDataManager to a view controller, there is no need for you to copy and paste the identical cells/display/detail actions here and there.

That's my experiences. Hope it will help.

liuyaodong
  • 2,547
  • 18
  • 31
-1

I would recommend you to use different view controllers for different datasources. It sounds good initially to put them all together in one place, but as time goes by, you may need to add different functionalities to each table view, and your view controller will be a horrible mess.

nonamelive
  • 6,510
  • 8
  • 40
  • 47
  • Different table view controllers suggests different navigation controllers, yeah? If you had 3 tables that used the same cell style but had different purposes (show nearby, new, saved- each with different http requests) would you use 3 navigation->table->details? – user Aug 02 '13 at 02:35
  • It depends. Suppose you have a table that, when an item is selected, shows an entirely different table. For instance, a drill-down interface where the initial selection is category, but you eventually end up with a list of items. That might imply two table views could realistically share a single nav controller. If the paths are disjoint, though, don't share. – Michael Graff Mar 07 '14 at 15:00