Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #22118 > unrolled thread

Why Web Page As Word Processor Not Done Years Ago?

Back to article view | Back to comp.lang.javascript

Contents

  Why Web Page As Word Processor Not Done Years Ago? irishhacker@gmail.com - 2013-11-21 19:12 -0800
    Re: Why Web Page As Word Processor Not Done Years Ago? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2013-11-21 19:25 -0800
    Re: Why Web Page As Word Processor Not Done Years Ago? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-22 12:09 +0100

#22118 — Why Web Page As Word Processor Not Done Years Ago?

Javascript APIs such as the KeyDown and KeyEnter events have been around for many years, right? Where for each HTML element, you can detect a mouse click or a key press?
So why, in the year 2013, isn't it standard fare that web pages should be self-editable (like modifying text and fonts in a word processor)? So you can click on any HTML element and make changes in a fairly visual manner?
I mean, reading and writing HTML + CSS is a real hassle, wouldn't you agree? And it's not 2001, it's 2013?
I mean, come on.

Is this one of those problems in applied computer science / software design where private sector programmers don't have an economic incentive to solve a problem, and academic computer scientists also don't have an incentive to solve the problem, so the problem remains unsolved for decades for the simple and stupid reason that nobody has a financial interest in solving it?

Robert Wilkins

[toc] | [next] | [standalone]

#22120

On Thursday, November 21, 2013 9:12:44 PM UTC-6, irish...@gmail.com wrote:
> Javascript APIs such as the KeyDown and KeyEnter events have been around for many years, right? Where for each HTML element, you can detect a mouse click or a key press?

Well, not ALL HTML elements, but quite a few.

> So why, in the year 2013, isn't it standard fare that web pages should be self-editable (like modifying text and fonts in a word processor)? So you can click on any HTML element and make changes in a fairly visual manner?

Have you heard of the contenteditable attribute? What else are you looking for? a full WYSIWYG? that goes beyond visual editing alone. A CMS? Even more so. web pages have been self-editable for many years.

> I mean, reading and writing HTML + CSS is a real hassle, wouldn't you agree? And it's not 2001, it's 2013?

Hence why there are so many tools, abstractions, and frameworks in existence.

> I mean, come on.
> 
> Is this one of those problems in applied computer science / software design where private sector programmers don't have an economic incentive to solve a problem,

Actually, people are already making quite a bit of money in this field. CMS system and mockup tools especially. I am in fact wrapping up a marketable tool in a subset of this field within a week or so.

> and academic computer scientists also don't have an incentive to solve the problem,

Well, generally it would have to be a NEW problem of course, not the same old one in new clothing

> so the problem remains unsolved for decades for the simple and stupid reason that nobody has a financial interest in solving it?

no

[toc] | [prev] | [next] | [standalone]

#22128

irishhacker@gmail.com wrote:

> Javascript APIs such as the KeyDown and KeyEnter events have been around
> for many years, right?

Wrong.

There is no Javascript.
There is no KeyDown event.
There is no KeyEnter event.
None of those are APIs.
DOMs, which specify events (among other features), are language-independent 
APIs.

> Where for each HTML element, you can detect a mouse click or a key press?

No.

> So why, in the year 2013, isn't it standard fare that web pages should be
> self-editable (like modifying text and fonts in a word processor)?

Why do you think it is not?

> So you can click on any HTML element and make changes in
> a fairly visual manner?

Yes, if the user agent supports that.

> I mean, reading and writing HTML + CSS is a real hassle, wouldn't you
> agree?

You are off-topic.

> […]
> Is this one of those problems in applied computer science / software
> design where private sector programmers don't have an economic incentive
> to solve a problem, and academic computer scientists also don't have an
> incentive to solve the problem, so the problem remains unsolved for
> decades for the simple and stupid reason that nobody has a financial
> interest in solving it?

Troll elsewhere.

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web