Page 1 of 1

Incremental Save

PostPosted: Tue Jan 24, 2012 11:38 am
by jsteinfo
This is my first post in these forums, so let me begin with a thank you. I appreciate the work that you have done here and feel fortunate to be able to leverage this code in our application.

It may be my lack of experience with the interface, but would it be interesting/possible to perform an incremental save of a document (in my case a PPTX package)? I notice that there is an internal map to track save status while saving the package. I wonder if we could have something similar to track what we have changed in the package and only save that?

My specific use case involves appending slides with an image to a presentation that eventually gets to around 100 slides in some cases. So as I go, this gets slower and slower as the size of the package gets larger with each incremental slide addition. At this rate, I could create the presentation by hand faster! (ok... maybe not, but it feels awfully slow :-))


Re: Incremental Save

PostPosted: Tue Jan 24, 2012 12:52 pm
by jason
Hi Jesse

There is no incremental save at the moment, i'm afraid. is used to write each part in the pptx (or docx, xlsx) package, when you say so.

It may be that you could incrementally write back to the original zip. If not with, then with TrueZip or one of the other zip implementations. Perhaps you could look into this?

Another optimization which would help - perhaps even more - is rather than unmarshalling each part when the file is opened, and then marshall it, to do so only on demand. This is probably much more important with pptx, where as you say you might have 100 different slide parts, than with docx, where there is just one main document part (irrespective of the number of pages).

cheers .. Jason