Re: some points

Hi

I'm currently in the middle of Silicon Valley and the hotels here have
of course Internet access :) The reason, why I'm here is, that I will
meet the Netscape developers tomorrow and I hope, I can bring some
issues up, which you just mentioned. If you have more stuff, you still
have a few hours time to send me them (approx. 10am PDT = 19:00 CEST).
 
> The cursor is important, but I think there is little choice but to see
> what the browsers bring us.   I'd like to see more docs and examples 
> first!   The readme really does get one off to a good start though.

I also really think, we can't do much about the cursor. The
"space/return" issue can certainly be solved on the javascript level,
but I think, it's time for "Content Editable" on Mozilla and I will
again bring this topic up tomorrow in the meeting.

Doing the cursor in another way is more or less a "no go area" for me.
We had a selfmade-cursor before and believe you me, the old one was
really nothing you would call a well-behaving cursor in todays gui-world
:) But this does certainly not mean, the way it is know couldn't be
better and it will get better and we're always open to new ideas

Concerning docu. I think for wider acceptance/adoptions of BXE,
documentation and simpler examples are very important. I started with a
very simple XHTML based example and I hope, I will have it finished soon
after being at home.

On Tue, 2002-10-01 at 04:07, holger krekel wrote:
>
> How did you try to do the cursor, then? 

Completetly in JS, moving span nodes... was terrible, you couldn't move
up/down for example, doubleclicking on words for marking them would have
needed a lot of code, etc... maybe there are better ideas, but some
things are just not doable in JS.

But I will discuss that with the Netscape guys tomorrow. Howeever we
won't have something directly in Netscape/Mozilla in short time, not
before 1.3 certainly.

> I think we *have* to find a better cursor implementation.  It's very
> confusing for the end-user to not get feedback on e.g. "space" and
> "return".

yep, the space/return issue should be solvable, the "no cursor outside
of editable fields" issue with some effort, too. Are there any other
issues, which you guys don't like about the current cursor? If these are
the only problems you have with it, we should be able to solve it even
without the help of Netscape Engineers (but it would certainly make it
easier with them). If there are other, more difficult problems, it would
be great, if you could post them here very soon, so I can discuss them
with the Netscape-people

> I know it looks like a lot of effort for a minor feature. 

No no, I agree with you. The cursor is a very, maybe even the most
important feature of an editor.

> And do the other browsers have Caret browsing too, by the way?

The only other browser BXE will ever work on (in the foreseeable future)
is MSIE 6 and this one has the contentEditable feature and therefore we
won't need Caret Browsing.

chregu

-- 
bx-editor-dev mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev