Unobtrusive JavaScript leads to BUILDERS (e.g. drag drop activitybuilder)

[lorlarz]

Unobtrusive JavaScript leads to BUILDERS (e.g. drag drop activity
builder)

Once you totally remove JS from a web page, and learn the shortcuts
and efficiencies
provided by a library like jQuery, one realizes that one can build
generalized builders
of JavaScript applications. One example is:

Universal Automatic Drag-and-Drop Activity Builder (builds the code
and web page)
http://mynichecomputing.com/GuideInfoandPlanner/UniversalDD.htm

Other examples of builders are on mynichecomputing.com
A couple others are:

http://mynichecomputing.com/hierMenu/HierMenuBuilder3.htm
and

http://mynichecomputing.com/linkGuider/:

 

[Henry]

Unobtrusive JavaScript leads to BUILDERS (e.g. drag
drop activity builder)

Once you totally remove JS from a web page, and learn the
shortcuts and efficiencies provided by a library like jQuery, ...

<snip>

LOL

 

[Erwin Moller]

Henry schreef:

<snip>

LOL

wow, this is impressive stupid spam indeed....
They get more ignorant by the day.

Regards,
Erwin Moller

 

[lorlarz]

Obviously what is meant is :
"Once you totally remove JS from the body of a web page ..."

(Otherwise Builders save everyone a lot of work, so all should be
happy.)

While I am at it, a link correction:

http://mynichecomputing.com/linkGuider/

Unobtrusive JavaScript leads to BUILDERS (e.g. drag drop activity
builder)

Once you totally remove JS from a web page, and learn the shortcuts
and efficiencies
provided by a library like jQuery, one realizes that one can build
generalized builders
of JavaScript applications.  One example is:

[snip]

 

[Thomas 'PointedEars' Lahn]

Obviously what is meant is :
"Once you totally remove JS from the body of a web page ..."

You will have a hell of a time debugging the mess that you made. And you
can never be sure if the code was attached, because of different DOMs.

"Unobtrusive JavaScript" as a general concept is an incompetent idiot's idea.

(Otherwise Builders save everyone a lot of work, so all should be
happy.)

While I am at it, a link correction:

[...]

[top post]

No, thanks.


PointedEars

 

[lorlarz]

Regarding the code used in the page which *is* the drag/drop activity
the user of the
Builder makes:

The small bit of code I add (beyond the core jQuery library and
established jQuery plugin library I use) does well in http://www.jslint.com/
-- no
stricter standard than that! And:

jQuery (esp. just the core) is just good JavaScript -- pure
Javascript,
providing utility functions and shortcuts; the prototypes of objects
are not messed with at all , like with prototype.js . Perhaps you
should research
jQuery a bit more.

All jQuery and its extensions or "plugins" are just pure JavaScript,
with NO manipulation
of prototypes.

Obviously what is meant is :
"Once you totally remove JS from the body of a web page ..."

You will have a hell of a time debugging the mess that you made.  And you
can never be sure if the code was attached, because of different DOMs.

"Unobtrusive JavaScript" as a general concept is an incompetent idiot's idea.

(Otherwise Builders save everyone a lot of work, so all should be
happy.)

While I am at it, a link correction:

[...]

[top post]

No, thanks.

PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
  -- Richard Cornford, cljs, <[email protected]>

 

[Thomas 'PointedEars' Lahn]

The small bit of code I add (beyond the core jQuery library and
established jQuery plugin library I use) does well in http://www.jslint.com/
-- no
stricter standard than that!

Code that is syntactically correct does not need to make sense.

And:

jQuery (esp. just the core) is just good JavaScript

It is no doubt written in for ECMAScript implementations, but it is written
in a rather clueless way.

-- pure Javascript,

You don't know what you are talking about. Go away.

[...] Perhaps you should research jQuery a bit more.

No thanks, we have had our share of discussing that and the utter
incompetence regarding Web development of its author already.

All jQuery and its extensions or "plugins" are just pure JavaScript,
with NO manipulation
of prototypes.

[...]

Will you please stop top-posting?


Score adjusted

PointedEars

 

[lorlarz]

Thomas

Let me again try to reply (my first attempt apparently failed). I use
only a small javascript
of my own, mynewtooltip.js , which passes inspection well in JSLint
(http://www.jslint.com/) --
a stringent test.
The rest of the code is pure JavaScript in the sense that it is from
the jQuery library, which is
only pure JavaScript with NO prototypes meddled with EVER. (My
program uses only the jQuery Core ( which
is very well tested and respected) and one of the more established
extensions or "plugins" (also pure
JavaScript with NO prototype meddling).

All the crossplatform checks this code goes through makes it very
likely that any major browsers will
run it. Individual idiosyncratic code is much more suspect.

-- Larz

Obviously what is meant is :
"Once you totally remove JS from the body of a web page ..."

You will have a hell of a time debugging the mess that you made.  And you
can never be sure if the code was attached, because of different DOMs.

"Unobtrusive JavaScript" as a general concept is an incompetent idiot's idea.

(Otherwise Builders save everyone a lot of work, so all should be
happy.)

While I am at it, a link correction:

[...]

[top post]

No, thanks.

PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
  -- Richard Cornford, cljs, <[email protected]>

 

[Gregor Kofler]

lorlarz meinte:

Thomas

Let me again try to reply (my first attempt apparently failed). I use
only a small javascript
of my own, mynewtooltip.js , which passes inspection well in JSLint
(http://www.jslint.com/) --
a stringent test.
The rest of the code is pure JavaScript in the sense that it is from
the jQuery library, which is
only pure JavaScript with NO prototypes meddled with EVER.

What's wrong with augmenting prototypes? Except that one should do it
properly.

(My program uses only the jQuery Core ( which
is very well tested and respected)

There have beeen plenty of threads in this NG proving the opposite. For
a start:

and one of the more established
extensions or "plugins" (also pure
JavaScript with NO prototype meddling).

And that says what about the code quality? IE6 is still the browser with
the largest market share...

Gregor

 

[Krukow]

"Unobtrusive JavaScript" as a general concept is an incompetent idiot's idea.

Hello PointedEars,

Can you elaborate on this comment?


Kind Regards,
- Karl

 

[Thomas 'PointedEars' Lahn]

"Unobtrusive JavaScript" as a general concept is an incompetent idiot's
idea.

[...] Can you elaborate on this comment?

I already have. Suffice it to say that implementations of the concept can
be useful as a last resort to avoid repeated event handler attribute values
for non-bubbling events or to handle proprietary events. But it should not
be used as a general programming approach for the reasons already given.


PointedEars

 

[Henry]

Regarding the code used in the page which *is* the
drag/drop activity the user of the
Builder makes:

The small bit of code I add (beyond the core jQuery library and
established jQuery plugin library I use) does well in
http://www.jslint.com/

JSLint is not a competition, you don't do well or badly; you pass or
fail.

-- no
stricter standard than that!

Standard of what? Passing JSLint means that you have syntactically
correct javascript source code (which you would more or less need to
have if it was going to execute at all) and you have not employed any
constructs/practices that are both machine detectable and disapproved
of by Douglas Crockford. Javascript code can pass that test and still
be objectively and obviously bad, so all JSLint would be doing was
asserting that the code avoided the opportunity to be worse.

And:
jQuery (esp. just the core) is just good JavaScript

LOL. Says who? Presumably they include the individuals who reviewed
John Resig's book and failed to recognise its parroting of
misconceptions, technical fictions, bullshit assertions and
recommendations of unprofessional practices.

-- pure
Javascript,
providing utility functions and shortcuts; the prototypes of
objects are not messed with at all , like with prototype.js .

While not repeating all of the mistakes of other software may be a
step in the right direction the result is not necessarily "good
JavaScript".

Perhaps you should research
jQuery a bit more.

Perhaps _you_ should research jQuery a bit more.

All jQuery and its extensions or "plugins" are just pure
JavaScript, with NO manipulation of prototypes.

<snip>

Your point being? Manipulating prototypes is a completely normal and
sensible part of javascript programming. There may be good reasons for
questioning the manipulation of the prototypes of the built-in
constructors (or at least some of them) but that is as far as it goes.

 

[Henry]

Hello PointedEars,

Can you elaborate on this comment?

In the event that that, and searching the archives, does not elicit a
useful answer you could try reversing the question by enumerating any
points made in favour of "unobtrusive javascript" and so see to what
extent those points are subject to criticism.