personally i find it easy to define them, as you would in a class or struct, since i can then look up to the top and easily see how/what i've defined, and don't forget to assign any variables, but I get what you're saying that it isn't necessary. I know what you mean, sometimes it's more convenient...

First of all, this: myCube = { x = nil, y = nil, width = nil, height = nil } is functionally equivalent to this: myCube = {} ...and all that does is create a table called myCube. It's not a class definition; Lua doesn't have any concept of classes. And that's probably a good thing, because you never...

It could work, but it's likely easier to set up a web page you can just POST the message to. That might be easier if you already have a web server set up, with a domain pointed at it, and a database installed. Then you just need a script to accept the posts and store them, and a script to view them...

As far as I know you'll have to authenticate to any public smtp server if you want it to accept your email. That shouldn't be the case; after all I can send email from my gmail to your uberspace without knowing your password (and without gmail knowing it). It's been a few years since I've looked at...

That's convenient, never noticed that. The tricky part might be finding an email provider that still allows plain old SMTP connections. Some of the major ones only allow connections over TLS or other encryption, but I'm sure you can find one or two if you poke around (or set up your own, but it's a ...

It is kind of nice to see exactly what's in the error report before it's sent, but I suspect you'd get more participation from automatic reports as peterrust suggests. You should be able to send the email programatically, behind the scenes, not with the user's email account but just by connecting to...

Always interesting to see how library authors handle user input. For anyone else interested, the madness starts around line 228. Feels a bit like a game of "which cup is the ball in." Would really be nice if library authors didn't have to go through this insanity (or subject users to it).

After that maybe you can tackle the event delegation system that looks like it was conceived in 1992. I'll gladly pay the $5.

Try doing it in two passes. In the first pass, store the next value for each cell, but don't update the actual value yet. In the second pass, update the actual value from the "next value" you stored on the previous pass.

If your bodies can also rotate, you'll need to calculate torque as well as force for it to feel halfway decent. There are tons of articles on this, just google something like "torque rigid bodies." As for storing the vectors, keep in mind that functions can return multiple values in Lua, s...