Comments on: Look ma, no callbacks!

By: Introducing Path Projection and Arrowlets (and me) « Khoo Yit Phang

Introducing Path Projection and Arrowlets (and me) « Khoo Yit Phang — Thu, 16 Oct 2008 19:57:26 +0000

[...] should thank Chris Eidhof and Adam Turoff for blogging about [...]

By: Chris Eidhof

Chris Eidhof — Thu, 28 Aug 2008 22:22:51 +0000

Reinier, you are completely right ;). It normally just takes some time before these theoretical things get a nice practical application.

movePaddle and moveBall are callbacks, but they’re not really explicit as they are with raw event handling. You don’t have to build all kinds of closures and such, but you’re completely right: in the end, you could definitely call them callbacks. Thanks for keeping us sharp!

By: Reinier Lamers

Reinier Lamers — Thu, 28 Aug 2008 11:52:02 +0000

I always thought of arrows as something for people who write academic papers and not programs.

And in what way are movePaddle and moveBall not callbacks?

By: Artyom Shalkhakov

Artyom Shalkhakov — Tue, 26 Aug 2008 11:36:14 +0000

This is pretty cool.

It surely blows jQuery’s/Ext’s/etc. pants off. :)

By: René Ghosh

René Ghosh — Tue, 26 Aug 2008 08:24:15 +0000

Excellent little introduction to arrows! Nothing makes things understandable like a good example, and this one is succinct and striking.

By: Sjoerd Visscher

Sjoerd Visscher — Mon, 25 Aug 2008 22:51:32 +0000

Cool stuff. Always nice to do Haskell in JS! If I remember correctly Safari reserves the keypress event for text input, just like IE. Simply use the keydown event, it repeats as well. Or, even better from gameplay point of view, use keydown and keyup to move the paddle while a key is down. Then you won't depend on the key repeat settings of the user. Is there something like until?

ElementA(document).next(EventA('keydown'))
.next(movePaddle.repeat)
.until(EventA('keyup'))
.next(Repeat).repeat()
.run();