My saving process is quite complex requiring modifications on s sub-
tree. Because of this I should write a custom Save implementation
to take care of navigation through that sub-tree.
Hint: you can make a subclass of the dialoghandler and register it
with a 'class' nodedata under the dialog definition.
I used this in the DMS instead of the save control.
However, part of the functionality inside Save is common, and can
be reused by subclasses, so I would like to suggest that all the 4
methods processBinary, processCommon, processMultiple and
processSaveInfo to become protected, so that somebody needing a
custom Save to be able to use the existing logic.
If you agree with this, I can immediately submit the changes.
I agree to this flexibility those methods should not be private: just
commit!
Philipp Bracher
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
