Maybe I missed something when I learned about TableViewControllers. I'm struggling with a simple concept - nested TableViewControllers - and I'm looking for the right design pattern / idiom for this.
When I say nested, I mean a hierarchy of tables - as an example, consider this:
I did a quick search through this forum and didn't find anything that seemed to match, so I'm asking. Is there a better design pattern for this or is this the right way to do it?
When I say nested, I mean a hierarchy of tables - as an example, consider this:
a first table view is presented with 3 options: A, B, and C. If A is selected, another table view is presented with options a,b, and c; if B is selected, a different table view is presented with options x, y, and z; and if C is selected, yet another table view is prestned with options 1, 2, and 3. This continues through the hierarchy of possible options.
I've coded this up with a whole set of TableViewControllers that get pushed onto the navigation stack (FirstTableViewController, AnotherTableViewController, DifferentTableViewController, and YetAnotherTableViewController) as the various options are selected, but it seems both tedious and sub-optimal. Tedium and sub-optimal are fine when it's limited, but I'm afraid it won't stay that way (and further I expect other apps will follow this same pattern).
I did a quick search through this forum and didn't find anything that seemed to match, so I'm asking. Is there a better design pattern for this or is this the right way to do it?
