I'm approaching the end of the alpha phase of my framework, and the fateful day that I bottle it up and push to GIT or similar repository and let the world marvel at my stupidity
Well, hopefully it won't bomb, but I did choose a dev name that is taken by another project. So I'm looking for a name again. I've always been partial to acronym names, but with those each letter has to reflect what the framework is trying to accomplish.
Remember BASIC - Beginner's All-purpose Symbolic Instruction Code? Well, that's somewhat what I'm trying with this. Here are some tags, features and goals of this thing.
Beginners - this framework is designed for people with little or no PHP experience. Code is fairly heavily commented and the comments themselves are being checked for clarity because I expect them to be read and referenced.
All-Web-Purpose Like the BASIC programming language before it, this framework is not focused on any particular web purpose over another - but it does expect to be deployed on the web.
Apache/MySQL PHP will work with other servers and databases, but for the initial version of the framework they've been eschewed in favor of supporting this extremely common setup. Later versions may support other web servers and databases - the framework is modular to allow for this - but initial support for a wide range of services would make the framework harder to grasp.
Event Based MVC The framework is MVC with the twist that controllers exit in the system as events. The super-controller (the framework itself) is an event dispatcher and maps events to their listeners in a clean fashion where events don't need to know what is listening to them.
Low Level ORM The system has a low level ORM system that can handle common SQL usage scenarios. It's not as robust or feature rich as Doctrine as that isn't it's purpose. Instead it exists as an example of ORM theory in general. It is capable of standing out of the way to allow the user to deploy their own model solution.
PHP Templating Templating is accomplished in PHP itself. It's possible to use smarty and other templating engines with it.
Accessibility The code is written to be easily read, largely self documenting, but clarity is the goal at all times. This is the overarching goal - someone can work with this framework with a few small projects, get their feet wet, and then move to more specialized and robust frameworks. That doesn't mean the framework won't be capable of production level deployment - it will. But I've already sacrificed optimization in some cases just to make the code easier to follow.
DRY philosophy - Don't repeat yourself. Items and methods are in one place only in the code.
So I need a name that can capture all that. And I'm sorta stumped at the moment. I understand that most, maybe all the regulars here, will have no need of this thing. I don't think I'm so smart as to be able to trumph the brilliant teams that work on Symphony, Zend and Cake. But I don't think a good bridge from echo "hello world"; to what their frameworks do exists, and I want to provide that bridge.