Zoetrope, a starter kit for LOVE

[josefnpat]

It's Fancy to see I'm `internet famous`. I always knew I'd be famous for my

Code: Select all

cowsay -f stegosaurus

.

I'm glad to finally see this out in the "open"!

[klembot]

Here's version 1.0.1, which should solve the arrow key bug along with a couple extra ones I noticed while testing on a Mac tonight. Updated demo is here, too!

[coffee]

Here's version 1.0.1, which should solve the arrow key bug along with a couple extra ones I noticed while testing on a Mac tonight. Updated demo is here, too!

Thanks, arrow keys no longer failing. I also have the tilde problem. I have it in keyboard but pressing it does nothing. Tried to find it elsewhere but I haven't Nixola luck. Even that configurable another key choice for the demo could be more safe.

[opticq]

Could you post a snippet that will successfully show a static sprite on screen? For some reason, just a static sprite isn't working for me but the tiles and animated sprites are.

[klembot]

See the first source code example on this page. Guessing without any information, you haven't set one of the needed properties. The bare minimum properties you need for a fill are: x, y, width, height, and either a fill or border. I should add some checks for this in strict mode...

[Kingdaro]

Isn't there a way to use "__index" so that you don't have to put "self" as an argument in almost every function?

Also, when a fill is missing a property of acceleration, it should just default to 0.

[Xgoff]

Isn't there a way to use "__index" so that you don't have to put "self" as an argument in almost every function?

Code: Select all

local methods = { }
function methods:foo ()
    return self.bar
end

o = setmetatable({ bar = "wat" }, { __index = methods })

however, that definition syntax isn't available inside table constructors so you have to use an explicit self inside those

[klembot]

Wanted to let you know I just put out version 1.1, which fixes a lot of annoyances (e.g. you no longer need to specify a x, y, and rotation velocity if you just want one) and also adds much more efficient collision detection. I went with a grid based method similar to bump.lua in favor of quadtrees. btw, if you make something with Zoetrope, please let me know! I am happy to link to it from the project page.

I like the idea of getting rid of self in method definitions a lot, but I also really want people to be able to specify methods in an object right as they extend a class. e.g.

Code: Select all

myObject = Sprite:extend{ bounce = function (self) print('bounce!') end }

[klembot]

Resuscitating this thread to let everybody know I've posted version 1.2, which brings:

• Pixel effects per group, e.g. apply a pixel effect to a specific layer of sprites, or the entire screen
• A new Subview class to handle temporary views like pause overlays and inventory screens
• Views have a panTo() method that scrolls the view so that a certain point is centered onscreen
• You no longer need to write a love.load() function; you only have to create the.app in main.lua and Zoetrope sets it running for you
• Some debugging niceties, e.g. you can write =2 + 2 instead of print(2 + 2), and objects now print their useful properties instead of just Table <xxxxx>

[Compost]

Thanks for putting this together. I'm just learning LOVE and Lua, and finding this quite helpful to get things up and running quickly. It's appreciated.

(e.g. you no longer need to specify a x, y, and rotation velocity if you just want one

This is true for "drag", but for "acceleration", I get errors if I don't include all three.