Changes
- Added love.physics.
- Added love.audio.setMode().
- Added love.audio.setChannels().
- Added love.graphics.polygon().
- Added love.graphics.setScissor() and love.graphics.getScissor() to handle scissoring the graphical area.
- Fixed missing constants related to image optimization.
- Fixed memory leak related to love::File (thanks amnesiasoft!).
The documentation has been redesigned. I'm sure someone will like the old one better, but that's their problem. The way examples are handled has also changed, so all the old examples are GONE I'm afraid. The new idea is that every example should be runnable like a normal .love app. A .love file with all the examples is coming soon (it is done, needs publishing).
As for the documentation of love.physics: only the interface itself with brief desriptions has been added. Much more is needed here, but we chose to release with the minimal amount of documentation and then flesh out later. The alternative would have been delaying the release, so no complaining . Yes, I do understand that software without proper documentation is worthless, so it *will* be improved as quickly as possible. Promise.
Demos
I've added emotics.love and lovalanche.love to http://love2d.org/demos/ which showcase some of the new functionality. More will come as I feel like making them.
A Word of Warning
The love.physics interface has a lot of functionality and has undergone some testing, but:
- This is BETA (Sparta!). You are a TESTER.
- A few (critical?) features are still missing. Especially with respect to collision callbacks.
- I'm a not a GOD of physics. There are I few things I don't understand at all, so documenting that part will be epic.
- The love.physics interface will not solve everything for you. There are things it can and things it can not do.
- The interface is sadly much more complex and harder to use than the other interfaces, but this time there was no way around it without sacrificing important flexibility.
For a simple example, check out lovalanche.love. That code has some comments and should not be too hard to understand. Also, the documentation at http://www.box2d.org/ is very good.
Enjoy!