moai/moai-dev — pull request #934 by patrickmeehan (2014-06-02 10:15:04+00:00)
Title: Rebase from community 140602

Wow! Amazing job moving Moai forward, everyone! Wasn't sure what was going to happen when I went dark last fall but... you're still here! And have made huge progress! This is awesome. :)

I'm not sure I understand the moai-dev branches these days. So I created a new develop branch to collect breaky, broken stuff. The first batch of which is this massive rebase from my own moai-dev/develop.

Some notes:

1 - This is going to be broken. I just did the rebase and sent this pull request right away. I wanted to get this out there ASAP so people can start picking on it. It would be a big help if someone could grab this and tell me what needs fixing and/or fix it, especially on Android.

2 - I need to go over every prior commit and restore anything that got clobbered. MOAITextBox and MOAIShader got refactored (among others) so I'm guessing some stuff fell on the floor. If you can see right away that I missed something obvious, please let me know. I didn't intentionally remove anything.

3 - The IDE projects are back. Cmake is great but it doesn't meet my personal development needs. I will maintain the Xcode and VS projects myself, but they will break. A lot. You can (a) fix them or (b) wait for me to do it. If someone decides we need a release, just kick me and I'll make a point to get them working again. They are super easy to maintain, I just rarely touch both environments in the same day (or week).

4 - The Android stuff is missing the Java files that work with my new .cpp bindings. I need to grok the new build system then I will submit those. I dearly want to find a way to keep them under src/ with all the other source. Not a fan of the way they are buried under ant. So if you are using Android, know that this rebase clobbers it.

5 - The 3rd party stuff on iOS and Android is being used in my own projects right now. I'll be looking at each and checking them against the community version. I think I have the latest of each, but will make sure. I did change some of the APIs to bring them a bit closer to what I want to use. Sorry if that wrecks anyone.

6 - The vector drawing stuff was all funded by Point Inside. If you are wondering, yes, it's being used to render SVG. I decided to write the parser in Lua and will ask them if I can contribute a simplified version of it.

7 - The overlap stuff is nascent. The intent is to have a simple package for overlap detection and arcade-style games where using a full physics package is overkill. I just did the bare minimum for my current client project. It's already starting to push at how I want to think about MOAIProp and making it more extensible. I'll solicit your feedback Soon(tm). Just know that, for now, the overlap stuff is very preliminary and the facet pattern is just one idea I'm playing with.

That's it. I'll follow up with more fixes on this branch in the next few days.