Niklas Nebel wrote: > 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.
I don't see a recombination here. The filter will just use different code to load and store the meta.xml. Or did I misunderstand you? Then please explain with some more detail. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
