bfat...@gmail.com
unread,Jun 30, 2011, 10:51:10 AM6/30/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to The Render Engine
Cross-posting this from my blog:
The Render Engine's website is still down. I'm starting to get a bit
frustrated, due to the fact that I really can't release v2.0.0 as a
beta unless I have a site to promote it on. I've spoken with my
server host and he assures me it'll be up "soon" which seems to be
code for "when I get around to it." I guess I shouldn't complain
about it... the site is hosted free and the domain costs me $1.00
annually to renew. But it is frustrating, as I said.
I've gotten the simple physics demo working again. It needs some
tweaking to make it feel right, but it is working. I'll be spending
some time on the rag doll demo to get it working again too. I've also
been working on the 2d Level Editor. I updated the HTML rendering
context to better handle tile maps and tiling in general. It's
working quite nicely, but I have to do some digging as to why sprites
are so darn slow on the iPad.
Additionally, I did some work on the Mouse, Keyboard, and Touch input
components. Rather than writing callbacks into a host object, you use
event binding to handle keystrokes, mouse, and touch interactions.
Gone are the "onSomeCallback()" methods, replaced by
"object.addEvent(name, callback)". This makes it possible for
multiple objects to receive event notifications when an event occurs
on an object. I tried to do the same thing for collision, but that
needs to stay a callback since a game object can (and should) respond
to a collision event. It also fires an event, but the event is fired
after a collision has occurred, rather than to determine if a
collision has occurred.
Another note about events... They are now an inherent part of the
engine. When objects are destroyed, an event is fired. As objects
are added to another object, an event is fired. Things running in the
browser are typically event-based, rather than cycle-based (or loop-
based). I originally tried to keep the engine more like traditional
game programming, but events just feel right.
I've got v2.0.0 all set to go beta, so as soon as I have a website
again I will get a beta version tagged (or however that works in Git)
and you all can get cracking with it. I want bug reports and good
heavy testing of everything the engine has in it. I'll be sure to
include your name in the credits for the engine - see your name in
lights!