Mathias Bauer wrote:
For loading and saving document based DocumentInfo objects the XML filter currently hands over the document model to the importer/exporter. They ask the model for its DocumentInfo and import or export everything using the DocumentInfo API.
From my understanding, that's also how it's supposed to be.
We also could create a "documentinfo object" and call methods to load itself from the document storage or store itself into it. The standalone case would be supported by providing methods to load and store from a MediaDescriptor.
Everyone keeps asking us to separate load/store code from the core implementation in Calc, so it seems wrong to re-combine them now for DocumentInfo.
Niklas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
