title: Should I really use a UITableView in this situation?
body: <p>Imagine you have a view like this:</p>
  
  <p>At the top, there is an <code>UISegmentedControl</code> with two segments. It functions like a tab. Pressing one segment will activate this particular content below that <code>UISegmentedControl</code>.</p>
  
  <p>Below the <code>UISegmentedControl</code> are some switches. These modify the way how the content should be rendered. </p>
  
  <p>And finally, below those switches, there's a table. Imagine a table not in sense of <code>UITableView</code>, but just what it really is: A table. It shows little messages like twitter messages or chat messages for example, one below the other. Like you know it from skype and other chats. Basically they're just rows with some formatting. A label, some image views, some lines, a background. Pretty basic.</p>
  
  <p>The data comes from an array. No core data. The whole thing including the segmented control and setup switches must be scrollable.</p>
  
  <p>So what I did is: I put all this stuff in an <code>UIScrollView</code>. Now I have to make the decision if I would use a <code>UITableView</code> inside there for that table part, or if I would just print a lot of rows on to the scroll view (with <code>-drawRect:</code>).</p>
  
  <p>But some problems stick in my head: Can I put a <code>UITableView</code> inside a <code>UIScrollView</code>? I assume this makes a lot of problems. I don't want that the table part is separately scrollable.</p>
  
  <p>Again imagine that view: First there are some basic choice things (segmented control, switches). Then there comes the table. When you scroll, the whole thing scrolls. That's mainly because this first part with the settings can be pretty big, so you would want to scroll it away.</p>
  
  <p>The next thing is: Can I customize <code>UITableView</code> in such a way, that it consists of two parts? One for that settings part, and one for the actual data to display?</p>