I’m sitting here wondering if I should go public with the PHP framework I’ve built over the past couple of years. It’s gone through a couple of iterations and is now something that I’m regularly building internal and external websites on top of.
No, it’s not the same thing as my Nifty CMS, but that one is built on top of what I now shall call the Nifty System Library.
It features
- MVC-based mechanisms, including templates, controllers, and database mapping
- A simple, custom built templating class, using pretty much PHP’s own template system with a few enhancements sprinkled in
- Page caching
- Basic application configuration
- Automatic call routing, including friendly URL rewriting, call-to-method dynamic invocation, and parameter filling
- Several wrapper classes for Request, Responses, Sessions etc
- Complete PHP5 OO design
- Minimalistic and intuitive class design, using static calls for shortcut class operations
- Database abstraction, including a simple class-to-table POPO persistence layer
- Simple module layer
- Clean separation between pages requiring authentication and public pages
- Zend-like directory layout (separated system, application and public_html folders for instance)
- Utility classes for…
- Excel/Delphi-style DateTime handling (DateTimeEx)
- Image manipulation (GD)
- HTML and database escaping (database agnostic)
- Password-checking
- TCP/IP connections
- Uploading functions
- ~40 files, 141 kilobytes total.
Once you’ve learned the basics, the system is very efficient, allowing you to build clean, efficient web applications with database integration using a minimal effort.
Is this something that people might be interesting in using, you think?

2 Comments
This looks advanced. I can´t understand much of it. =) But it is always good to protect your inventions in some way. There has to be some of copyright you can get on these kind of things?
Nice.