Ha! I was considering doing this exact same thing.
I'm working on a vanilla js version that I was considering porting to cljs.
It might be interesting to compare implementations:
https://github.com/harto/pacman
Thanks for sharing,
Stuart
On 18 August 2011 08:00, Matthew Gilliard wrote:
> I've b
Excellent - cheered me up no end whilst migrating (read re-installing) the
60-odd virtual machines from VMware ESXi to XenServer (it is currently
1.05AM in the UK so desperately needed a cheer)
Thanks for sharing the source - I fully expect to learn a lot after reading
it - keep up the good work :
> Very cool! Now the logic of pacman is in a form I can easily read :-)
I assume you are referring to the gameinternals post not my code !
I do not know why it only works in Chrome. The error "too much
recursion" is confusing. It happens before the game is rendered so I
suspect it's in the cod
Very cool! Now the logic of pacman is in a form I can easily read :-)
Out of interest, do you know why it only works in Chrome? Doesn't the closure
library do any work to shield you from from the browser differences, or is it
simply a performance issue with the Chrome js engine the only one oper
Hi Matthew,
Have you tried console.log() as
(.log js/console "is anybody out there?")
That works for me currently.
When I first started in ClojureScript I had trouble calling
console.log() because it was a native code function and it couldn't be
called with JavaScript's .call(this, args) for
I've been playing around writing a fun little ClojureScript project -
it's a bit different, so I thought you might like to see it:
http://mjg123.github.com/pacman/pacman.html
As I was feeling my way quite blindly through ClojureScript and
gClosure I have let the code get into a bit of a mess an
