In-browser Javascript Editor ala FCKeditor

[madtom1999]

I've been playing with some javascript code and have produced a very
rough proof of concept source code editor written in javascript (a bit
like FCKeditor). Its not ready for release ((L)GPL>2 when it is) but I
thought I'd ask for any guidance and tips.
The intention is to provide a language nuetral source code editor
writen purely in html and javascript so that it can provide code
highlighting/completion etc, eventually as part of an ajax(ish) IDE so
with fckeditor you can manage web sites completely remotely.
There is a temptation to try and use mozilla/venkman but I'd like it to
run on small handhelds too so I will stick to writing it in pure
Javascript/Html.
The intial plan is to produce a javascript editor and then a stylesheet
editor (using the CSS editor on Firefox may make this a low priority)
but I'd like it to be configurable for any language so almost any
coding can be done over the web.
Anybody know any examples of similar that I could plagiarise to get the
basic architecture right?
Tom

[Peter Michaux]

ma********@yahoo.com wrote:

I've been playing with some javascript code and have produced a very
rough proof of concept source code editor written in javascript (a bit
like FCKeditor). Its not ready for release ((L)GPL>2 when it is)

BSD or MIT license will make it easier for people to use.

The intention is to provide a language nuetral source code editor
writen purely in html and javascript so that it can provide code
highlighting/completion etc, eventually as part of an ajax(ish) IDE so
with fckeditor you can manage web sites completely remotely.
There is a temptation to try and use mozilla/venkman

Venkman is a debugger, yes? What does that have to do with an editor
running in a web page?

I think that not all browsers support the features that a WYSIWYG
editor needs.

Peter

[madtom1999]

I think that not all browsers support the features that a WYSIWYG
editor needs.

If it runs javascript it will work!

[Randy Webb]

ma********@yahoo.com said the following on 11/23/2006 4:25 AM:

>I think that not all browsers support the features that a WYSIWYG
editor needs.

If it runs javascript it will work!

If you make that claim, then you won't ever write an in-browser editor
that is worth having.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[madtom1999]

Randy,
I'll clarify - by javascript I mean javascript that can access and
modify the DOM and intercept keystrokes.
Remember that a textarea can be used at the very worst - its a text
editor though not very useful - but the computing world was built on
bits and bytes and coding productivity is often slowed by having
editors that 'think for you'.
So, other than lack of vision, commitment, a desire to protect your own
investment, or fantasy patents that wont apply in most of the world,
have you any proof it can't be done?
Otherwise thanks for your help!
Tom

[Randy Webb]

ma********@yahoo.com said the following on 11/25/2006 4:37 AM:

Randy,
I'll clarify - by javascript I mean javascript that can access and
modify the DOM and intercept keystrokes.

NN4 can do either but you can't very well create a decent text editor in
NN4 using it. Your claim was that "If it runs javascript it will work! "
and that is a bogus claim at best.

Remember that a textarea can be used at the very worst - its a text
editor though not very useful - but the computing world was built on
bits and bytes and coding productivity is often slowed by having
editors that 'think for you'.

::yawn::

So, other than lack of vision, commitment, a desire to protect your own
investment, or fantasy patents that wont apply in most of the world,
have you any proof it can't be done?

You mean other than almost a year fighting the different implementations
on the web that won't support a rich text editor yet?

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[madtom1999]

So , since some code wont work on a few % of PC's nothing should be
written - is that what your trying to say?

[Randy Webb]

ma********@yahoo.com said the following on 11/25/2006 5:49 AM:

So , since some code wont work on a few % of PC's nothing should be
written - is that what your trying to say?

What are you babbling about now? I never said that. I said that your
statement was blatantly false. I never did say you couldn't satisfy 95%
or so of your visitors.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Peter Michaux]

Hi Randy,

Randy Webb wrote:

>
You mean other than almost a year fighting the different implementations
on the web that won't support a rich text editor yet?

What did you learn about the Rich Text Editors and their
implementations and browser support?

I saw that Hard Core Text Editor supports IE, FF, and Safari2. The
FCKeditor supports IE, FF and Opera, I think. So is there an editor
that covers the four big browsers?

I haven't bothered much learning about RTEs because the web doesn't
seem ready yet but I think they are likely to be future work for any
JavaScript programmer.

Thanks,
Peter

[Randy Webb]

Peter Michaux said the following on 11/25/2006 12:45 PM:

Hi Randy,

Randy Webb wrote:

>You mean other than almost a year fighting the different implementations
on the web that won't support a rich text editor yet?

What did you learn about the Rich Text Editors and their
implementations and browser support?

At the time that I would never get it to work on a MAC. But, at the time
Safari2 wasn't out yet.

I saw that Hard Core Text Editor supports IE, FF, and Safari2. The
FCKeditor supports IE, FF and Opera, I think. So is there an editor
that covers the four big browsers?

If one can support 3 and another can support the 4th then an educated
guess would be that there could be one written to support those 4 browsers.

I haven't bothered much learning about RTEs because the web doesn't
seem ready yet but I think they are likely to be future work for any
JavaScript programmer.

That is the reason I stopped working on mine. It was part of a larger
message board type project and I wanted the RTE for creating posts.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[madtom1999]

I think you'll find the babbling started when YOU decided I was going
to write a rich text editor.