Bill Fenner wrote: > > I don't want to undermine your business model. My biggest concern is > that you've developed the difference between Standard and Pro in order > to get a certain class of people to buy Pro, and then I come along and > make it so that those people don't have to buy Pro. On the other > hand, you've had a long history of supporting open source and related > projects, and there's a certain parallel with writing RFCs.
Thank you very much for your concern. > > My current plan is to release an update that uses > PlatformUtil.shellExec to replace the process command, and then > investigate doing XSL conversions in my Java code. > I would wait for 3.6. XXE v3.6 (even Standard Edition) should have a "transform" command. May be you'll find it useful. Here's a short description of this command: --- Like a number of other commands, the "transform" command is only useful for writing macros. Using the XSLT style sheet passed as a parameter, the "transform" command transforms part or all of the document being edited (explicit selection, implicit selection, whole document, depending on a parameter) to an output stream (XML, HTML, plain text). This output stream is ``loaded as a string'' and returned as the result of the "transform" command. If this result is the string representation of an XML tree, it could be directly used by a subsequent "paste" command. If this result is a plain text list of items, it could be directly used by a subsequent "pick" command. The parameters of the "transform" command are: * The URL of the XSLT style sheet. (The "%c" variable will be made available in order to resolve URLs relative to the configuration containing the macro invoking the transform command.) * Optional parameters for this XSLT style sheet. * What is to be transformed (explicit selection, implicit selection, whole document; default: explicit selection). * The encoding of the output stream (default: UTF-8). The "transform" command should be much more efficient than a process command, even when the XSLT style sheet of the process command is cached and when there is no user feedback during the execution of the process command. Note that: [1] The "transform" command is not a replacement for process commands. [2] The "transform" command has no extra features compared to process commands. The "transform" command is more or less equivalent to this process command: <copyDocument/> <transform/> <read/> Except that the ``<copyDocument/> step'' does not copy any document but instead *SAX* *traverses* part or all of the document being edited. ---
