Indeed. Pretty much every game in existence has update and draw functions, in one form or another.

Framebuffers/canvases will stay in VRAM all the time until they're gone, taking up space even when they aren't used, I think.

You can redefine the game loop if you want.

tentus wrote:Seriously, why do we even have Box2D in Love if everyone hates it so much?

People often misunderstand its uses (or how to use it) because it's essentially a whole new API on top of regular LÖVE. I personally love it, but I also know when to use it and when to stick with my own solution.

This is really cool.

Jasoco wrote:Are there any nightly Mac builds? I still have one I got a month ago.

Here's one built from the latest tip and using LuaJIT (with an additional 1-line quickfix to prevent luajit crashing with 0.8.0): http://dl.dropbox.com/u/4214717/love-0.8.0.zip

Intel only.

For systems which can't display non-PO2 images, it will be all good as long as the final image (the texture atlas) is PO2. Quads and the source images don't need to be PO2.

There are a few resources on the 'nets about packing textures efficiently into a texture atlas.

Wow that's really cool.

I believe love.graphics.setIcon takes an image object rather than a string path to an image, so something like this:
Also, the wiki says that setIcon might not work on windows. :/

Quick proof-of-concept using Stencils in LÖVE 0.8.0 (it will give an error without the latest 0.8.0, because stencils aren't in 0.7.2): http://dl.dropbox.com/u/4214717/love/te ... lygon.love

I'm not sure if stencils would be the best way for terrain stuff though.