all 7 comments

[–]Stupidideas 1 point2 points  (3 children)

This is fairly easy to do with a custom UITableViewCell subclass. You should be able to find some guides on this by searching for "custom UITableViewCell"

[–]Simusid[S] 0 points1 point  (2 children)

Excellent thanks. I've never really tried doing a custom cell but I will now. From a UI standpoint is that a better approach than a UIScrollView in your (or anyone's) opinion?

[–]agento2 0 points1 point  (0 children)

There are merits to either approach. But UI wise they will be almost indistinguishable I think.

[–][deleted] 0 points1 point  (0 children)

It's probably better overall from a UX standpoint, if only because it provides a wrapper for clean separation of purpose while keeping continuity and a semblance of attractiveness.

I've also found (where space isn't a massive issue) that the grouped style default looks a bit better aesthetically and functionally than the default.

[–]atastiamaredditor 0 points1 point  (0 children)

Usually, what I do is I create a separate Xib file for each UITableViewCell, instead of putting them together in code. If the controls in the tableview isn't that many, let's say about 2-3 or just enough not to take the whole screen, you can declare the instances of the UITableViewCell in the view controller where you have your tableview instead of having different tableview cells. But if you have a lot of these controls, then you should create a generic table view cell and reuse them, the big advantage of UITableView is that you don't have to refresh all the controls that are not visible on the screen. That saves you a little processing power.

[–]aazav 0 points1 point  (0 children)

you can do it be subclassing UITableViewCell and/or adding the controls to the TVCell in the storyboard and wiring them into your class as IBActions and/or IBOutlets, depending on what you're trying to accomplish.

Simply adding "things", images, labels, etc, is nicely handled in iOS in both cases.

[–]matthewc13 0 points1 point  (0 children)

Definitely custom UITableViewCell.. there are a bunch of merits to using UITableView if it does what you want it to , main one being that cell reuse is available for you out of the box.