I have a scenario where users may have spent a considerable time on a print layout and have added many different printerlayer, e.g. for a legend, title box, images and labels and so on. Currently I persist these settings during a session but if the application is closed and reopened then they are, of course, lost.
I was wondering how robust serialising the various PrinterLayers would be?
For example if you (ThinkGeo) modified the PrinterLayers code would deserialising fail?
If so do you have any suggested models / patterns for handling this type of scenario?