Databases
StackOverflow2013
Postsdbo
POTableView navigation - All the lables, textfields and images in one single ViewController or separate ones?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTableView navigation - All the lables, textfields and images in one single ViewController or separate ones?
    primarykey
    data
    text
    <p>I'm in the start phase of my first iPhone app. Its a tab based application where each of the tabs represent a TableView menu with x cells, leading to other menus. As I'm getting started, after watching several tutorials, reading lots of info from Apples database, here at sof etc, and I'm actually really confused as I'm getting along in x-Code.. Some basic things are slowly getting clearer, but.. There are so many options and so many ways to to things right and wrong, and I'm afraid of making big mistakes and screw it all up. But back to the point:</p> <p>What this app is all about is red wine. Its a guide/register over red wines sold in Norway with bottle imgs, info about price, taste, etc. Now that the TableView main menu is slowly starting to take form, I'm starting to think about the wine register cells and how to delegate the info in the detail View(s).</p> <p>Should I create only one DetailView for the WinelistMasterViewController, and add the info about the wines as lables/textfields/images onto the background image in the storyboard, coded to show according to which cell you press in the list?</p> <p>With more than 100 wines this seems like a big mess with all those lables in one view, it seems more tidy to make 100 views and make the connections from the WinelistMasterViewController to each of the tableviews. Why shouldn't I do it this way? I hope some of you can give me some directions. This is how I'm building the storyboard: </p> <p>TabBarController --> Navigation Controller for tabs. In this case: Tab 2: The Wines --> TableView with cells to choose if you want to show the wine table alfabetically, by popularity, price, etc --> TableView with the Wines in the chosen order (cells with text, bottle image and favourite star ---> full screen background img with all the info about the wine you chose, and you will also be able to swipe between the wines, add to favs etc..</p> <p>I'm a beginner so I have one hell of a job in front of me figuring out how to code up all this in the delegate and xviewcontrollers. But I do it with patience, one thing at the time, trying and failing and learning and slowly things take form.. But this seems like kind of a major issue which, I guess, determines much about how complicated the coding have to be later on. </p> <p>I also want to mention that later on I will add a search function to rule and sort the list by needs, so it all should be adapted for this as well.. On advance, thank you for all help with this project! References to tutorials, articles, websites and other that can help me on my way, is also very much appreciated!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USingenspor
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTableView navigation - All the lables, textfields and images in one single ViewController or separate ones?
      1. This table or related slice is empty.
      1. VTUndeletion
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload