Comments on: Automating JS Behavior Registration

By: Jesse Kuhnert

Jesse Kuhnert — Fri, 18 May 2007 23:26:31 +0000

Sorry for all the pooh pooh Gabe. I thought it looked interesting and so submitted it without your consent. ..Err next time maybe I’ll just let you do it. :/

(but hey at least you got some more hits – even if they were angry pooh pooh hits ;) )

By: Gabriel Handford

Gabriel Handford — Fri, 18 May 2007 23:11:00 +0000

This was just a proof of concept (and not even entirely functional). The idea was to parse the DOM all in one shot, so if you have a ton of behaviors, you don’t have to deal with alot of selector rules. You could add other naming conventions to automate common tasks, do binding, etc.

It is verbose, inefficient, not original or entirely unobstrusive, and probably not worthy of a spotlight on ajaxian :O

By: Warren Konkel

Warren Konkel — Fri, 18 May 2007 17:37:30 +0000

The power of behaviors is that it attaches javascript to DOM elements… not just onClick behaviors, but anything. Behaviors can do anything at init time (move stuff around in the DOM, anything), attach to multiple keyboard/mouse events, etc. And behaviors can be object oriented so you can have a mouseover event and a mouseout event tied to the same object that that also does loading stuff at init time.

By: Jeffrey Robbins

Jeffrey Robbins — Fri, 18 May 2007 16:57:38 +0000

Hmm, not something I would use in an application, I try to stay away from using the class attribute for anything except styles.

By: Andreas Kalsch

Andreas Kalsch — Fri, 18 May 2007 10:25:30 +0000

Is this really worth a headline on Ajaxian?

[Yes] [No]

I click on yes, hoping that the click handler is listening to me.

By: Country

Country — Fri, 18 May 2007 08:55:39 +0000

Haha, this is ridiculous.

Next step :

HTML :
Hello

JS :
eval(document.getElementById(‘foo’).className);

By: digitarald

digitarald — Fri, 18 May 2007 08:42:38 +0000

Funny pattern, maybe he should think a bit more about it. Behaviours should not be inline, since its the idea behind behaviours is to split view and controller. Also selectors that only work with classname w/o tag are slower than both tag and classname combined.

By: Jelle

Jelle — Fri, 18 May 2007 08:29:17 +0000

And how about stopping the observer? May be difficult, since prototype only unregisters observers when passing the same function reference.

No thanks, I’ll take care of events myself.

By: Anonymous

Anonymous — Fri, 18 May 2007 08:11:51 +0000

just think about perfomance, when that automation script needs to parse all your DOM to find all event handlers

By: Greg

Greg — Fri, 18 May 2007 07:45:34 +0000

That isn’t unobtrusive.

By: Alex

Alex — Fri, 18 May 2007 07:36:47 +0000

it’s sounds like reinventing the wheel ..

By: Bertrand Le Roy

Bertrand Le Roy — Fri, 18 May 2007 06:11:46 +0000

Yes, exactly, is it April 1st?

By: Anonymous

Anonymous — Fri, 18 May 2007 05:57:15 +0000

It’s amusing that standards freaks actually believe [a class="bvr-observe-click-xhrTheFunction"] is somehow better than [a onclick="xhrTheFunction"].