I mean that only one property (which of course could contain others) could be loaded (or saved) at a time. Not the whole tree. For instance, if my tree corresponds to a windows registry key, it is desirable to load or save a single value without loading or saving all the values in the key.
I am quite sure Serialization lib will allow you to do this. Just apply it to appropriate field.
It requires a lot of work. The serialization library does not provide a model for in-memory property storage, nor does it provide a windows registry archive (the last time I saw). Applying serialization to appropiate fields implies I already have those fields somehow organized. The way I see it, PT is the serialization library plus in-memory property storage. Perhaps it could have used serialization internally and serialization archives for loading and saving. As I said before, the real difference could be the loading and saving of some of the properties in the memory storage, without having to load/save them all. Cheers Jorge