I went down much the same route (though by the looks of it you've done a better job) and recently have decided to scrap the whole thing in favor of Yii, which I really hope is a good long term decision (always dicey).
What are your long term plans, is this a fire-and-forget thing or are you going to continue to maintain it and accept patches and so on ?
Is there a roadmap where you want to go with this ?
It's definitely not fire and forget. I've been using it for over 4 years so I don't have any plans on ditching it. The main point of documenting it was so others would use it and I can improve on the library.
If you look at another one of my libraries on github (https://github.com/jmathai/twitter-async/issues) you'll see that there have been over 90 issues raised by others which I've resolved. It's what's made that library so solid - hoping for the same here.
Funny, you're jmathai, I'm jmattheij !
I have a lot of respect for the authors considering the other work they've done. Thanks for the lead on Yii, and OP: your stuff looks pretty good too!
The same could be said prior to Yii regarding building from the ground up. Yii shouldn't exist based on your own argument :).
If you prefer than then I do think the larger frameworks are a good fit. What I'm saying is that I don't prefer that :).
If I need to do a SELECT on a specific field(s) then I write that statement. It's usually a 4 line function in a class that deals primarily with that table (but not necessarily as it may make sense in a different class).
I use static functions for that as well.
class User {
public static function getByEmail($email) {
return getDatabase()->one('SELECT * FROM user WHERE email=:email',
array(':email' => $email));
}
}
I don't typically end up with so many of those that it's unmanageable and writing it takes about 30 seconds.That's my approach. What's your thought on that coming from the mindset that a lot of that is taken care of by the framework? I'm curious since that's not a mindset I've had yet.
I'm not a fan of large frameworks that do all sorts of voodoo on my behalf. This framework is less than 1300 lines of code and includes
I've used it on publicitweet.com (sold), textbookrevolt.com and thescholarapp.com. It's got some good usage but I'd like to iron out bugs I haven't come across and let others use it if they'd like.