Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not familiar with this programming language, but in general the point of modularization is to hide complex implementation and expose a simple interface. This is good, because you typically don't need all your data and all your functionality to do every task. This is done by keeping data close to where they are used (e.g. same class), and using few public methods. </p> <p>However, there are situations where you need to support sharing lots of data and functionality between modules easily, which sounds like what you want to do. E.g. in GUI programming the model-view-controller design pattern does just that. The key is to group your data and functions some other way, but it's much less easy to do well.</p> <p>Questions to ask yourself: Rather than having the controller separate from the data, is it possible to refactor so that each part of data is with a corresponding part of the controller? For example, if you have two types of data, can you refactor into two classes, each having methods to calculate and to print that type of data? Maybe you will also find that some of the "data" is really state of the controller, and this definitely belongs with the controller code.</p>
    singulars
    1. This table or related slice is empty.
    1. POSegmenting code into multiple source files
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USabc
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAlthough I never found a webpage showing *how* to modularize, while looking for samples on Costique's recommendation, as well as 'category' examples I also found Apple's (trivial) "SimpleCocoaApp" demo where it uses a main controller plus two other separate NSObject objects that are handed separate tasks by the principal controller object. Is this what you mean? Is having several separate custom objects considered wasteful of resources? No? (I'm asking out of newbie ignorance here). Hmmm... it now seems there are *several* solutions to my question! Thanks, abc. Appreciate your help :-)
      singulars
      1. PO
      1. USBender
    2. COHaving looked up cocoa, I understand it recommends/enforces the MVC design pattern. 1) Yes, the controller can be split up into a kind of hierarchy if it's unweildy. 2) You can have many custom objects, if each represents one unique concept (understand "concept" as you wish). Finally, the point of MVC is to modularize data, while allowing a controller to cross-reference different type of data easily. My view is that *only* code that does this should go in the controller. Code that does something with only one type of data (one model class) should be in that model class. Hope that helps.
      singulars
      1. PO
      1. USabc
    3. COIt sure does help, and thanks for all your input. I guess I painted myself into a corner by rushing to add code without giving priority to a properly planned structure *first* (you know how it is :-)). I've now got a (test) NSObject model up and running alongside my AppController and it's working perfectly -- though I see what you mean by: "... group your data and functions some other way, but it's much less easy to do well." There are certain common objects (like a main array) that need to be passed to different model controllers, but generally speaking I've got the basics now. Thanks again!
      singulars
      1. PO
      1. USBender
 

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