( originally filed at: http://bugzilla.openedhand.com/show_bug.cgi?id=1860 )

Currently json-glib simply serializes everything that is readable.

In my own use cases, its only important to serialize what is also writable, since I happen to plan on using that same output to deserialize.

There is also the possibility you dont want or need to serialize properties that are at a default value.

While I doubt all this know-how belongs in json-glib, perhaps some kind of a general signal on the json parser in use could allow a more general control on what properties are getting serialized.

would allow for a construct like:

 - parser = create_parser ( file );
 - connect_signal (parser);
 - root = obtain_root ( parser );
 - json_gobject_new (root);

Anyway, maybe that's a lot of indirection/overhead to call a signal to get each property serialized - just a thought.