On Friday, June 10, 2011 08:43:58 AM Pierre wrote: > That is a really interesting solution. The biggest trick would be not to > forget to delete the objects at the right time if the endElement stays in > the destructor. > But I'm not sure how it would interact with the change tracking code, > unless you can integrate change tracking in these classes, then it's just > great...
The change tracking is a touch nut to crack indeed. I cannot oversee the implications there. In my opinion, change tracking logic should be separate from normal serialization. TC code would need to write fragments. So the change tracking writer can also be a friend of the classes it needs to write. Would that be enough or are there more problems? Can you give an example? Cheers, Jos -- Jos van den Oever, software architect +49 391 25 19 15 53 074 3491911 http://kogmbh.com/legal/ _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
