Hi Lon,
[Lon Boonen Fri, Oct 11, 2002 at 10:04:52AM +0200]
> I want to make one assumption: we are talking about editing XML
> documents that will most likely be published on the internet to be
> viewed inside of a browser.
>
> > Let's presume that javascript-based technology is the way to
> > go if you want to connect to other free software projects.
>
> JavaScript technology is the way to go if you want to build a WYSIWYG
> editor.
In Java-land there are quite satisfying solutions for browser-side editors.
> Not because you want to connect to other free software.
It's an interesting coincendence that in the Java-world there isn't
a strong free software community. While python/perl/PHP/C/C++ all
have large communities and strong applications, many good java
applications are ClosedSource.
> How else would you render HTML or XML/CSS to get a WYSIWYG view? Only
> inside a browser you will get true WYSIWYG. You cannot let Java render
> the display of you XML/CSS or DHTML. It can't. The same goes for C++ and
> so on.
Having basic Wordpad-behaviour is more important than the *exact*
WYSIWYG-representation. But you know this oppinion :-)
> > Now should we work with XML structures on the client side
> > or with HTML structures? You argue that HTML is better because
> > there is widespread quasi-standard support for it. But the
>
> HTML is the logical choice because HTML is what will ultimately be
> published to your viewers.
That depends on the viewers.
People want Word-documents out of a CMS or put StarOffice-Documents
into a CMS. They want to make print-editions of their stuff, too.
It's not all about HTML, y'know. The whole point of having
XML-structures in CMSes is to be View-independent. In almost any
environment you can manipulate XML-structures.
But HTML might still be the "logical choice" for other reasons :-)
> > E.g. how do you handle events, how much access do you have to
> > the screen
> > (selections, cursors) how *could* you do a file dialog (inserting an
> > image etc.)? Questions like these are to be answered if you want
>
> All of this stuff can be done using modern browsers. I don't see the
> problem.
I'd like to see the proof. Do you have a life demo running Xopus
somewhere on your web site? Preferably not on IE/Windows.
thanks & regards,
holger
--
bx-editor-dev mailing list
bx-editor-dev@xxxxxxxxxxxxxxxx
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev
|
