Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not sure I understand what you're asking for. Isn't it pretty trivial to figure out how many NSTextFields the user wants and then have a little for() loop to create them? You'll probably want to keep track of the textfields, so I would probably do it like this:</p> <pre><code>NSMutableDictionary * interfaceElements = [[NSMutableDictionary alloc] init]; for (NSInteger i = 0; i &lt; numberOfTextFields; ++i) { //this is just to make a frame that's indented 10px //and has 10px between it and the previous NSTextField (or window edge) NSRect frame = NSMakeRect(10, (i*22 + (i+1)*10), 100, 22); NSTextField * newField = [[NSTextField alloc] initWithFrame:frame]; //configure newField appropriately [[myWindow contentView] addSubview:newField]; [interfaceElements setObject:newField forKey:@"someUniqueIdentifier"]; [newField release]; } </code></pre> <p>The dictionary of course would not be local to this method, but I think you get the idea.</p> <p>Alternatively, you might be able to coerce NSMatrix into automating the layout for you.</p> <p>If you're writing a client application for the iPhone, then I would highly recommend looking to the <a href="http://developer.apple.com/IPhone/library/documentation/PreferenceSettings/Conceptual/SettingsApplicationSchemaReference/Introduction/Introduction.html" rel="nofollow noreferrer" title="Settings Application Schema reference">Settings Application Schema reference</a> for inspiration. If you're unfamiliar with this, here's a brief introduction: The iPhone allows developers to move their preferences area from the actual app to the Settings app. This is done by creating a settings bundle and building a plist in a very specific way. Settings.app then discovers that plist, parses it, and builds an interface according to the definition it contains. You can do switches, textfields (even secure ones), sliders, groups, and a couple other kinds of interface elements.</p>
    singulars
    1. This table or related slice is empty.
    1. PODatabase Results in Cocoa
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDave DeLong
    1. USDave DeLong
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODatabase Results in Cocoa
      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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODave: Thanks for your reply. Maybe trivial for you, but I haven't used anything but Interface Builder for my layouts before. I think you are spot on when it comes to my question, "dynamically" show NSTextFields and the like to the screen. Thanks to your comments, I think that I basically get what is going on in the code... But how would you draw that NSMutableDictionary to the screen? Probably a very simple question (which I apologize for), but I am rather new to this whole mindset. This is for the desktop only, right now, but I thank you for your link to the iPhone recourse.
      singulars
      1. PO
      1. USPF1
    2. CO(Continued) And maybe I'm reading your post wrong, but isn't that a pretty automated layout already? Once again, thanks for your help.
      singulars
      1. PO
      1. USPF1
    3. CO@PF1 apologies; I understand that for those coming from IB-only interfaces, making stuff through code can still be a bit of voodoo. =) As for drawing the NSMD to the screen, you don't. That's what the "[[myWindow contentView] addSubview:newField]" line is doing. The NSMD simply serves to maintain a reference to the field (like a collection of IBOutlets) so that you can pull information from the fields later. And yes, this is somewhat automated in layout, in that it stacks NSTextFields on top of each other. But if you have more textfields than fit on the screen, you'll need an NSScrollView
      singulars
      1. PO
      1. USDave DeLong
 

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