progress...

Jul 19, 2009 21:01

http://www.club.cc.cmu.edu/~mds2/js_play/calculator.html

cool.

Some side comments

1) That whole thing with

return
function foo() {};
being different from

return function foo() {};
is bullshit.

2) Also, if "makeFunctionToMakeAccessorForMyDataMember" has type "Dom Node -> unit -> my data member type"
apparently

f = makeFunctionToMakeAccessorForMyDataMember(node);
data = f();

works but

data = makeFunctionToMakeAccessorForMyDataMember(node)();

doesn't, which is a pain in the ass.


My reccomendation is that someone make a "translator" which can take some sensible language, and convert it into javascript. The language doesn't seem *that* different from python, ruby or R [Okay, I don't know enough "R" to say the last one comfortably] it shouldn't be impossible to make a translator from a subset of one of these to a subset of javascript.

Finally: I'm a graphics programmer at heart. I'm not going to be satisfied with this until I know enough ugly DOM tricks to actually get real sprite-based graphics working. It must be possible, since both "Google Maps" and "Google StreetView" work this way.... ...huh, I wonder if I could cheat and look at these...
Previous post
Up