I'm going to answer that in a very long and roundabout way.
I'm a college student, and I've been developing applications using the LAMP stack for a very, very long time. I've liked it, but I found that my code was simply unmaintainable. So I strayed. I went into the worlds of Django and Rails, and I saw some things that I liked. Unfortunately, despite the claims of these frameworks, there was not a lot in the way of ease-of-development, despite their claims. I found my biggest problem to be with their assumption that they knew what I needed or, even worse, what my data looked like. I don't have a problem with having to define my database in a certain way, but my clients often did, and one can easily see where the problem arose.
But some of the stuff I saw blew me away. If I wanted to manipulate my data, these frameworks made it really easy to do so provided that I was playing the game their way. When I returned to the familiar and happy world of PHP, I missed that, and while there were things available to help me, they were huge. Additionally, they relied on the same logic that had turned me off to the Ruby and Python counterparts. Namely, this idea of convention over configuration. I'm not so great at getting good ideas, but I saw a problem and decided that I could be the person to solve it.
So I started work on what was then called PHPmySQLmagic or phpmsm, and was generally happy with the fact that I was able to develop a system that assumed nothing about your database and stil lmade it esay to manipulate it. And then, I decided that I could make it smarter, so I did, until eventually it got to the point where phpmsm didn't need convention or configuration. Needless to say, I thought I was pretty awesome.
What I was most excited about was that given only standard credentials to connect to a database, I had automagically created objects that related to entries in my database. But, of course, that's pretty worthless. It saves developers from writing SQL, but it doesn't help out so much. So I've started adding important features like error handling, automatic form generation, and some simple(very simple) full-framework stuff. But I want to keep it all very lightweight, because, and this is the key to the development of my project, I don't know what you need, and I certainly don't know what you want. I know what I want, and that's something that will make it easier to write maintainable code in PHP, but wont define my project for me. I want something that won't overshadow your project because it's fast and lightweight. I want something that, in fact, makes your project smaller overall, not bigger. And with PHPmagicSQL, I'm making it for both of us.
Hope you're as excited as I am