I'm wondering what the brain trust here thinks about the best way to model an application that has multiple list view presentations for a single set of data.
In my case, the data (as well as the UITableViewCell) is identical, but I have 3 different sort/grouping options. The first sort option results in a single section with all rows beneath it, the second option results in 2 sections, and the third option will result in about 50 sections.
Should this be 3 different views/controllers or a single view/controller with enough logic to get the correct data displayed?
It seems to me that 3 different views/controllers makes the most sense. That way I can prepare and group the data as required and tie it specifically to the controller.
I would agree with your assessment. It may seem like a lot of extra code, but the functionality is split out nicely making it easier to change or add or remove.
If you have all the logic for those scenarios built into one controller it could easily become a nightmare for maintaining and debugging, imo.
Same data, multiple presentations
Linear Mode
