[Christian Stocker Fri, Oct 11, 2002 at 07:43:15PM +0200]
> > > - Why the XML/XHTML mix?
> > >
> > > The first reason was speed. With this approach, we don't have to do an
> > > XSLT Transformation everytime we change/append/delete a node, but let
> > > the browser do it with it's DOM-tools. This also makes navigation and
> > > inline-xml-stuff much easier to handle. Furthermore, if you just want
> > > to edit your xml and give a shit about html-output, you can take a very
> > > simple xslt, provide a proper CSS and can start editing it.
> >
> > Sorry for repeating stuff from other mails, but ... why does it matter
> > so much if transformations take place on the server or client side?
>
> Don't know, what you exactly mean with that question.
You could transform the XML on the server side to, say, HTML
and the client works with it and then sends back the HTML
to be transform back to the "content"-XML on the server side.
It's more or less a way of transporting data. It's not so
much the data format i worry about but the display/interaction
techniques.
> > The main work seems not to be the "transport" but a decent interactive
> > editor on the frontend. If that is really achievable with XML/XSLT/CSS
> > and the mozilla API than it's a good idea (at least for Mozilla:-)
>
> I think, this is really achievable :)
I am not convinced as long as there is no decent cursor and stable
bold/italics/... markup :-) IMO having wordpad-alike behaviour is
the goal. As usual, your mileage may vary.
regards,
holger
--
bx-editor-dev mailing list
bx-editor-dev@xxxxxxxxxxxxxxxx
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev
|
| 
