Kevin Flynn wrote: > Some questions/wishes: > > Is there a simple way to ensure that an XSL transformation is run each time > a file is opened or saved? I know it's possible to use the DocumentHook > class, but I'm not a Java programmer, so if I can avoid having to become > one...
For now, you need to code a DocumentHook in Java. > When a process command is run, a dialog containing progress information and > a cancel button pops up. Is it possible to suppress this in any way? It can > be a little distracting for operations that are very fast. Currently no, but this should be easy to implement. Anyone else interested? By the way, if you use highly interactive process commands, do you know that it is now possible to cache the small XSLT style sheets typically used in such highly interactive process commands. See http://www.xmlmind.com/xmleditor/_distrib/docs/commands/ch05s01.html > Some way of assigning a "no-edit" attribute to element subtrees via CSS > would be useful. My documents contain a lot of generated content that it > would be useful to see when editing, but which it is pointless to edit. The > CSS generated content functionality is not powerful enough to generate this > content, but I could do it by running a transformation each time a file is > opened for editing; it would then, however, be nice to be able to "protect" > this generated content: to specify that "all this element's children may not > be edited". Clicking anywhere in the protected area would then select the > parent element (which could itself be edited). This could be achieved by a DocumentHook coded in Java. After generating content during the File|Open, mark this content (necessarily elements) as being read-only by using method setReadOnly(). See http://www.xmlmind.com/xmleditor/_distrib/docs/api/com/xmlmind/xmledit/doc/Tree.html#setReadOnly(boolean)
