LÖVE

Santos wrote: I'm probably totally confused, but should't it be...

if math.abs(circleA.x - circleB.x) > circleA.radius + circleB.radius and math.abs(circleA.y - circleB.y) > circleA.radius + circleB.radius then

because the circles could only be colliding if the centers on both axes are in range?

    if math.abs(circleA.x - circleB.x) > circleA.radius + circleB.radius or
       math.abs(circleA.y - circleB.y) > circleA.radius + circleB.radius then

2vek wrote:* please provide full length rss feeds. It will be easier to follow the blog with google reader.

2vek wrote:* syntax highlighting would be nice too.

2vek wrote:Awesome work, by the way :)

monsieur_h wrote:Congratulation to our writers ! Both articles are amazing and very instructive. However, I advice to use more images. This helps comprehension, especially when dealing with 2d math.

• Essentially rewrite the PiL chapters on object-orientation, which may delve into areas that the beginner Lua audience might get scared away by. Additionally, this is a very large topic, and would probably need to be stretched out over several posts to cover everything pertinent to classes (i.e., inheritance, polymorphism, metamethods, the colon syntactic sugar, privacy, etc.);
• Just pimp out one of the many great object-orientation libraries for Lua, which doesn't really teach anyone anything specific to LOVE and/or Lua.

• - Tutorials where you make some game. I think tutorials like this could be good, because I think it gets people psyched, because they want to make games but they're really not sure how to go about it, and you can kind of take them through the process. I think tutorials like this might good if they were structured in a way which didn't confuse the reader, maybe starting off by defining the rules of the game they're making, how the necessary data is stored, how the logic will work, and then going into the actual code which needs to be written to make it work. Or maybe it could be done completely "naturally", maybe even in a screencast format, going through the real process of how you'd actually go about turning the game which you can see in your imagination into something which you can play, through thinking of different ways to structure things, debugging, etc.
  
  - LÖVE from/to *insert something else here*. There are other things which are kinda similar-ish to LÖVE that I wouldn't mind exploring, like FlashPunk, NME, SDL, Flixel, Unity, libgdx, etc., but I already have Lua and LÖVE in my head, and I think that maybe it would be a lot quicker and easier for me to learn how something works by seeing how it is similar or different to LÖVE, "so, this engine uses callbacks like LÖVE, except it has this other convention for naming functions, and it can't do these things LÖVE can, but it can do these other things easily, and in this language you use these two other things instead of tables, etc."
  
  And of course this works the other way too, introducing people to LÖVE in the context of a framework they already understand.
  
  Or, it could help someone choose which framework/language they'd like to use for whatever they want to do.
  
  - A look at how LÖVE works internally, an introduction to what powers the modules and a brief overview of how they work, what was chosen to power LÖVE and why, what tradeoffs were consciously made in the development of LÖVE, how the infrastructure LÖVE is built on top of affects its design, maybe even some history about how things have changed and why, etc!
  
  - How to do things which are found in some games which might not be so obvious, like replays, splitscreen, I saw a blog post on screen shaking recently.
  
  - Some sort of glossary? I don't really know how this would work, but maybe there are a lot of words and concepts which are used a lot which people who are new might not know? I dunno.
  
  - Debugging?
  
  - An overview of the IDEs avaiable for use with LÖVE (ZeroBrane Studio, Decoda, Love Studio) including what features they have and how to use them while making games.
  
  - An indepth look into love.audio, including distance attenuation model, velocity, etc.
  
  - love.physics
  
  - If Maurice Guégan or Kyle Conroy were interested in interviews, maybe that might be interesting? Or the developers! How do they make the magic happen?
  
  - Videos because everyone loves videos! Maybe a "HEY! You just downloaded LÖVE! Here are the answers to all of the questions you have on your mind right now!", like a quick-start video introduction.