Re: [xsl] wysiwyg xml editing

["Robert Koberg" <rob@xxxxxxxxxx>]

Are you talking about things like parent elements and attributes that would
not be visible in the wysiwig editor?
(using IE5.5+ as the editing tool only - output good in any 4+ browser...)
What I do is have the XSL (server-side) write a bunch of hidden spans/divs
and allow the user to right-click a corresponding visible chunk to edit the
invisible atrributes. What it does is basically is mimic the XML with the
html.  Also, unique id's are created by the XSL for the nodes so
'round-tripping' is made easier.  When you create new nodes client-side you
need to create a suitable id for it's place in the XML tree that will
eventually be output.

Are you talking about a user being able to select a 'title' and a 'para' at
the same time?
If so I would say what Mike is saying, that you should only allow them to
edit/select one chunk.  You will still have to catch things like bold and
italics but these are manageable.



----- Original Message -----
From: "Michael Kay" <mhkay@xxxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, May 08, 2001 6:04 AM
Subject: RE: [xsl] wysiwyg xml editing


> > hmm, I'm tinkering with an editor for xml documents where you
> > should be able
> > to select a piece of text and select a tag that it should be
> > formatted with,
> > the problem I'm running into is translating the text
> > selection into a valid
> > new xml structure since what you selected might overlap
> > different tags
>
> I'd suggest that you insist that the content of a selection is a
> well-balanced XML fragment. Whether you do this by automatically adjusting
> the selection, or whatever, is up to you!
>
> Mike Kay
> Software AG
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list