Here's the plan for module development for the Phritz framework.

Currently, there are only two modules in the source-- the db module that has the DAO interface, the DB instance and the PhritzDbObject class. The other module is just the Test module that's up at dev.fritz-works.com.

I'm currently torn between keeping the DB classes in a module or moving them into the core of the framework. Initially, my thinking was that a database is not absolutely essential to a running application. A calculator application shouldn't really need any kind of database instantiation to run simple calculations. Perhaps the database should be moved to the lib directory, still keeping it seperate from the kernel, but not a seperate module.

Other modules that I want to see implemented at some point in the future are many of the basic parts of an application including User management, Session management and Authorization. Ultimately, I'd like to see a PhritzCMS package that would be kind of a meta-package that loads all of the above-mentioned modules. But that's a long way off.