Is there a better way to serialize plist-y objects in Objective-C?

Question

I like the plist serialization capability for small collections of objects: it is simple, the storage is XML, etc. But I find setting values in dictionaries cumbersome:

[myDict setObject:keepThis forKey:@"ivar"];

I'd much prefer to use object derived of classes (or even just structs):

myObj.ivar = keepThis

... and then send a message to a collection to get a plist. The classes/structs used for this purpose could be restricted so that they map directly and easily to plist primitives; for example myObj could be mapped to a NSDictionary and a requirement could be placed on ivars such that they are one of the plist primitives.

Has someone already built a facility for this, or should I roll my own?

Answer 1

I'm not sure that this is quite what you're talking about, but Key Value Coding will, among many other things, let you get a dictionary with values from an instance's data, and also set instance data from a dictionary.

There's also a way to ask an instance for a list of its attributes, though it turns out that you have to write some code yourself to make that work. (You, could, though, use the runtime introspection to implement that, if you wanted.)

(The NSCoding protocol is another way of letting your objects store/restore themselves, but the storage is binary, not XML, and you are still responsible for getting/putting each value you care about when asked by the system to do so.)

Answer 2

An interesting project. The Objective-C 2.0 Programming Guide has a section on the runtime functions to dynamically get a list of a class's properties:

objc_property_t *class_copyPropertyList(Class cls, unsigned int *outCount)

With this, it should be quite easy to write a category on NSObject with a method that gets the list of properties and puts them into a dictionary.

Answer 3

You might want to check out this SO question which discusses putting an instance's ivars in a dictionary at runtime.

Answer 4

In order to use properties for this, you would need to have a predefined set of possible keys. You can't use arbitrary names with the dot-syntax — it had to be a known property or accessor of the first operand. So there can't be a generic form of this. But if you do make one of your own, turning into a dictionary is as simple as doing [self dictionaryWithValuesForKeys:listOfProperties].

Answer 5

I saw this posted elsewhere, but it is exactly what I was looking for. The answers above point to the raw ingredients, but here it is, all wrapped-up: http://retaincount.com/blog/?p=7