- Basic macro support(prevent the user from editing
macro generated
html)
It looks like you'd be recoding what is currently existing in the
wysiwyg editor. While this is nice to have it in word, I'm wondering
what it's going to cost to maintain the 2 features.
I'm only referring to making macro generated content read-only. IMO,
this is not nice to have, it's mandatory, as without it, the user will
damage every page that contains a macro.
Marius: is this implemented on the server or on the client for the
WYSIWYG? If it's on the server then it would be great to reuse it for
XWord. :)
It's done on the client-side. At most you can try to use the same
technique I use, but I doubt it's going to work in Word. Let's talk
about this Monday.