I started to notice a pattern evolving when I begin writing an application... the last few have almost always had the same base layout so I figured it's time to write a little framework (just for me... not something I'll release -- at least not any time soon). Last night I made a start and because I've done it a fair few times I got pretty far just in the space of an hour or so.
I'm just wondering what you'd include in a lite framework? I don't want something really feature-packed because clunky things bug me.....
So far I've put the things in that I *know* I'll use.
I always start with a config class (yeah, don't ask but I like keeping configuration directives in a class called config).
I then have a db wrapper class (just MySQL... hmm... I should add PgSQL too), a core engine (not a lot in this in the main framework because I fill that specific to the app in question), a template engine that ties in nicely with the framework, a function to load in classes & modules (easier in PHP5 of course), some very small example modules and some skeleton controller classes and templates just to serve as a mini-documentation.
One thing I don't like is things that do everything for you. For example... a db class that you don't actually have to write queries for... that's just silly and makes it less obvious what's going on... I like to write my queries by hand.
I'm in two minds as to whether to include a list/pagination class too. If you were writing a "lite" OOP/MVC framework what would you like to see in there?