Databases
StackOverflow2013
Postsdbo
POBetter alternative for "data-only" Objective-C objects?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBetter alternative for "data-only" Objective-C objects?
    primarykey
    data
    text
    <p>I run into design choices like this often and struggle a bit; I'm looking for some other perspectives.</p> <p>I often want to keep lists of, or pass around chunks of state that are basically just sets of values. The values tend to be primitive types: floats, NSTimeIntervals, CGPoints, etc.</p> <p>My first inclination is often to create C structures for these sets of properties, e.g.</p> <pre><code>typedef struct _STATE { float foo; NSTimeInterval elapsed; CGPoint point; } STATE; </code></pre> <p>etc.</p> <p>But C structures don't play nicely with the native Cocoa collection classes (<code>NSArray</code>, <code>NSSet</code>, <code>NSDictionary</code>), and using overmany of them to track lots of state feels like it runs against the grain of rest of my Cocoa-friendly code-- I end up having and directly managing arrays of structs, and passing struct pointers around in messages, etc.</p> <p>On the other hand, since raw performance isn't necessarily critical, I could encode these values into a NSDictionary, wrapping them all in <code>NSValue</code> or <code>NSNumber</code>, but the resulting syntax is hardly terse, and a little fragile, requiring type and name correctness at runtime for both the insert and the lookup:</p> <pre><code>[stateDict setObject:[NSNumber numberWithFloat:foo] forKey:@"bar"]; ... float something = [[stateDict objectForKey:@"bar"] floatValue]; </code></pre> <p>and some types, like NSTimeInterval, are only able to be used with some (arguable) hackery (typecast to double in that case).</p> <p>Finally, I could create data-only container objects, with private member data and only getters/setters. (These would be called "beans" in Java.) These are more terse to access than dictionaries, more Cocoa than structs, but feel like overkill to me, especially if I only need them as "inner classes" that are used for state management internal to a single object type.</p> <p>How do you, great Cocoa programming public, do this?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBen Zotto
    1. USBen Zotto
    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
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBetter alternative for "data-only" Objective-C objects?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBetter alternative for "data-only" Objective-C objects?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBetter alternative for "data-only" Objective-C objects?
      1. This table or related slice is empty.
      1. VTUpMod
    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