Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Early:</p> <blockquote> <p>In order to learn from scratch (and because I know my app would need dynamic views), I decided not to use Interface Builder.</p> </blockquote> <p>Later:</p> <blockquote> <p>As soon as I try to create something on my own which is not a "Hello World" screen, I realize that something is missing, logic wise.</p> </blockquote> <p>I think what is missing logic wise is that you have accepted your assumption that Interface Builder was a crutch and that to learn "from scratch" you had to avoid using it. You are trying to learn the MVC design pattern but you are not willing to use the tools that have been designed to support it.</p> <p>In <a href="http://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/CocoaFundamentals/CocoaDesignPatterns/CocoaDesignPatterns.html#//apple_ref/doc/uid/TP40002974-CH6-SW1" rel="nofollow">Apple's own documentation</a> they discuss the fact that sometimes there is value in having combined roles—Model Controllers and View Controllers—and that is worth reading, as it may explain some of the code examples you're reviewing. But my primary advice would be: before assuming you know better than the people who built the tools, trying using them the way they recommend. It might be an eye-opener.</p> <p>Additions later: OK, so to try and actually answer your questions...</p> <blockquote> <p>1)Where should I put the the second view (along with the first one in "xxxView" or should I create another class h and m file?)?</p> </blockquote> <p>If I am understanding correctly and the two views you are thinking of here are the red and the blue displays to the user, you wouldn't have a second view—what you would do, whether in IB or in code—is to have an element in your view on which you changed a colour property... This would be done programmatically whether you were setting up the parent view in IB or in code. </p> <blockquote> <p>2) What would the controller(s) do, for that kind of application? In which files would they be created and in which files would they be invoked and how would they "control" the related view?</p> </blockquote> <p>There would be a view controller that would implement the gesture support, and would provide a method for changing the colour of the item in the view between blue and red when that swipe gesture was successfully received. I would have a ViewController.h and and ViewController.m. I think if you were implementing the View entirely in code, it would be implemented in the ViewController.m rather than having a separate View.m. (If you were using IB, you would have a ViewController.h, ViewController.m and ViewController.xib, with the latter providing the basic setup of the view elements and layers.)</p> <p>You would create a ViewController instance in your AppDelegate.</p> <blockquote> <p>3) Mainly, regarding to MVC pattern and the fact that there would be no IB, how would you organize that app?</p> </blockquote> <p>As above.</p>
    singulars
    1. This table or related slice is empty.
    1. POXcode 4 organization, Views and Controllers
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDuncan Babbage
    1. USDuncan Babbage
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POXcode 4 organization, Views and Controllers
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI don't assume I know better than anyone. What I assume is that if I ask how to prepare sushis, I expect recipes, not evangelist telling me how wrong it is to eat raw fish instead (with quite a pressure!). Is it possible to code without IB? Yes! Even if it's weird, even if it's time consuming, even if I use the keyboard with my feet, why do you care? Are you so worried that a guy you don't know becomes a bad developer? You seem to have some experience here so you should know better than me that opinion debates are not allowed, yet, that's all I got. I'm not better than you, I'm just different.
      singulars
      1. PO
      1. USBaylock
    2. COThis being said, I thank you for your interesting input. It's just the "you know better than..." that annoyed me a little.
      singulars
      1. PO
      1. USBaylock
    3. COIt's more a case of wanting to make sushi and deciding to breed fish instead of using ones from the market. Sometimes to start with, you can go too low level. IB is a powerful tool and building with it to start with helps you understand the concepts better as it guides you to some degree. Then once you understand how to build with it you can riff off those ideas with custom approaches...
      singulars
      1. PO
      1. USKendall Helmstetter Gelner
 

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