Smart-Art in Writer - Correct 'Import' approach ?

Hi Community,

We are doing some work on implementing 'Smart-Art *Preservation*' in Writer.

Meaning – if the user does    WordèLOèWord    round-trip we plan that they
won't lose their Smart-Art object.

Currently Smart-Art is being imported into *simple shapes* in Writer (which
don't exactly look the same), and most of the actual data and binding
between shapes is lost (not to mention it doesn't look the same).

In order to preserve the original Smart-Art object – we would plan on
loading the entire XML nodes and attributes of Smart-Art to property maps
(e.g. Miklos's great 'InteropGrabBag').

In addition, instead of showing to the user simple shapes (that he can
currently edit and move around) –

we would like to change this and show the user a *locked* bitmap of the
smart-art, that the user cannot manipulate (so that he can at least
preserve the original Smart-Art).



Is the approach we are taking good (changing the current malfunctioning
behavior that converts Smart-Art to shapes).

Should we take a different approach that maybe pops a message when loading
a DOCX with Smart-Art asking the user:

*"We noticed you are importing a DOCX with Smart-Art. Would you like to
preserve it and keep it un-editable or convert it to simple shapes ?"*

And then act according to the user's choice? (choosing simple shapes will
lose the 'Smart-Art' functionality, while choosing 'preserve' will not let
the user edit the smart-art, only see it).



Best,

*Adam Fyne*

*Office:* +972-77-517-5008

Twitter <http://www.twitter.com/cloudoninc> |
LinkedIn<http://www.linkedin.com/company/cloudon>
 | Facebook <http://www.facebook.com/cloudoninc> | Blog<http://www.cloudon.com/>