Christian Stocker
2002-10-09 16:07:00 UTC
-----Forwarded Message-----
From: Christian Stocker <***@bitflux.ch>
To: holger krekel <***@devel.trillke.net>
Subject: Re: [bx-editor-dev] some points
Date: 09 Oct 2002 17:49:08 +0200
at least not like the browser would. But you're right, it will be quite
hard to get the editor working like any other text-processor is expected
to behave... But at least the Mozilla/Netscape Developer know now, that
we are around and I think they have an open ear for us :)
how much time to get a *stable* user-friendly basic WYSIWYG-editor? I don't
want to press on you at all because i know you are doing good work. But it'
s important to have a *realistic* time schedule. Both of us need a reasonable
plan for our customers.
puuh, hard question. and i can't really answer it. I will certainly put
a lot of effort in the next few days in improving cursor and other
stuff..
look at. And the simple example (XHTML) is still very needed...
chregu
From: Christian Stocker <***@bitflux.ch>
To: holger krekel <***@devel.trillke.net>
Subject: Re: [bx-editor-dev] some points
Date: 09 Oct 2002 17:49:08 +0200
hello Christian,
welcome back to europe.
it's too cold here :)welcome back to europe.
In the meantime i also analyzed the situation with a (javascript-)
friend and he stated that working XML/DOM-based with current
brwosers forces one to hack around lots of bugs. And some things like
cursors are *hard* to do at all. And we are not even talking about
cross-browser here. There is no stable javascript-editor currently
which doesn't mean we shouldn't aim for one. The only solutions so
far seem to involve java.
java is no solutions here for our goal. java does not render HTML/CSS orfriend and he stated that working XML/DOM-based with current
brwosers forces one to hack around lots of bugs. And some things like
cursors are *hard* to do at all. And we are not even talking about
cross-browser here. There is no stable javascript-editor currently
which doesn't mean we shouldn't aim for one. The only solutions so
far seem to involve java.
at least not like the browser would. But you're right, it will be quite
hard to get the editor working like any other text-processor is expected
to behave... But at least the Mozilla/Netscape Developer know now, that
we are around and I think they have an open ear for us :)
Buuut, my Netscape visit last week revealed that they are really hard
working on ContentEditable support. It won't be in 1.2 (IIRC), but 1.3
would be a viable target. I hope, this will resolve some issues with the
cursor, but I'll try to improve it nevertheless.
Good news. So taking everything into account, the main question probably isworking on ContentEditable support. It won't be in 1.2 (IIRC), but 1.3
would be a viable target. I hope, this will resolve some issues with the
cursor, but I'll try to improve it nevertheless.
how much time to get a *stable* user-friendly basic WYSIWYG-editor? I don't
want to press on you at all because i know you are doing good work. But it'
s important to have a *realistic* time schedule. Both of us need a reasonable
plan for our customers.
a lot of effort in the next few days in improving cursor and other
stuff..
Probably you know that having simple clean code also has a lot more
chance to attract more developers.
haha, nice hint :) I hope with going OO the code is getting nicer tochance to attract more developers.
look at. And the simple example (XHTML) is still very needed...
ASFAIK we will meet on the 16th
in Zuerich so we can discuss this in depth :-)
yep, we should take some time then for that.in Zuerich so we can discuss this in depth :-)
chregu
--
bx-editor-dev mailing list
bx-editor-***@lists.bitflux.ch
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev
bx-editor-dev mailing list
bx-editor-***@lists.bitflux.ch
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev