ioctl

Random Javascript rubbish

ioctl.org : jan's home page : random rubbish

jan's junk

Here is a list of the test pages I've concocted to demonstrate bits of random tat.

Something new appears here everytime my office-mate, Dan, asks me an off-the-wall JavaScript question. It may, or may not, be related in some way to what he asked for.

check out those groovy sandals!

A quick testbed for JavaScript patterns. Throw bits and pieces at split and match.
Random sentence generation in JS. The standard 'BNF backwards' toy. And no, the use of the copula without an adjectival phrase is grammatical (it's also a fine example of solipsistic projection and all kinds of groovy pretentiousness).
Converting a string to an object in JS ...for no good reason.
Using a drop-down menu for page selection ...for no good reason. There are probably better ways to do this; it was just a quick-and-dirty example.
Who plays whom? Competition round calculations. ...in which we see netscape's JS implementation once again demonstrate a few holes between platforms.
Prolog Love it or hate it, you just can't program declaritavely in it. This subset does support declarative programming by dint of removing (read: not implementing) every non-logical construct (and a few others besides) from Prolog.
Scope rules and binding in JS Summary: reference-counted environments.
The use of eval() to create self-modifying Javascript programs Summary: javascript is the next Perl.
My entry into the "5k award" competition Self-extracting javascript archives (TM).
Higher-order programming Summary: javascript is the next Haskell.
Cross-frame DOM access This was supposed to be a first stab at accessing the contents of one frame from another; instead it turned into an example of the most consistent cross-browser performance that I've ever come across: ie, it totally crashes IE4+, NN4.6+ on various platforms; on Win32 of course, it'll take the desktop with it :-) I'm not sure why it's so fucked. However, I am certain (although it's only MHO, of course) that under no circumstances should an error in a piece of JavaScript code be able to crash the brower. That's one of the lauded advantages of an interpreted environment, after all.
Compilation of Guha's RDF-QL into jsProlog via a JavaScript pre-processor.
Cross-call of a JS function in one frame by another.

This stuff is hardly wizardly, but who cares?

That's all for now. Are you enlightened/entertained/bored yet?