Lists Home |
Date Index |
Robert Koberg wrote:
> Sjoerd Visscher wrote:
>> You are exactly describing what Xopus does. (http://xopus.com)
>> Although the other suggested editors will work, Xopus is the *only*
>> editor that lets you use your existing publishing xslts for wysiwyg
> How is this possible? What if your transformation is lossy or adds
> things?-- How do you know what to roundtrip?
> Can you have multiple content pieces on a page? How do you know where
> content pieces are as opposed to page structure?
I can't answer for Xopus (and I'd like to hear their answer), but
restricted cases are possible. The basic idea would be: In XSL every
input node and result/output node are uniquely numbered. For any input
text node that is copied directly to output without modification (or
with trivial idiomatic modifications like whitespace normalization), a
transitive 1-to-many correspondence could be established. If the user
modified an output node for which such a correspondence existed, the
input node and all other output nodes in correspondence with it could be
changed, as well.
XSL is a Turing-complete language; you can easily write a stylesheet in
which there is no traceable correspondence between any input and output
nodes. But I guess this line of argument is good for Xopus, because the
arguments might keep others from trying to solve even the simple cases.
The real question, I think, is when you do what you can do along these
lines, do you get a useful result? Don't know. It would depend a lot on
how people write their stylesheets.
> I think it is very wrong to have an XML editor edit an instance document
> based on the result of transforming that instance document.
It's only wrong if it doesn't work. ;-}
> Or perhaps
> roundtripping rules needs to be setup for each transformation??? Or
> perhaps the transformations have to be done in a certain way??
>> Other editors use the limited possibilities of CSS or require you to
>> create a proprietary transformation for wysiwyg editing.