I have recently started new php project. It is my own php engine/framework.
I have tried couple frameworks and all of them have been pretty nice. I especially like cakephp.
But the problem with these sometimes is that they force too much where what code should be placed. Example the Model View Controller stuff. The idea is great idea and I have nothing againgst it, on some small project cakephp/any most of the frameworks are way too massive. (in my opinion of course)
But if I code from scratch and place all if my code where it feels good to place it… Usually something is somehow in wrong place. This is when I get the idea for my own framework.
Napalm engine framework (or NeF in short) is a php framework that doesn’t make creating code any faster. It just helps to keep code where it should be. It should help managing code base on small/medium project.
This framework also won’t force user to place some code on some place. It only offers way to manage code in standart way. If user doesn’t want to use all of the elements, rest of the system won’t break.
NeF will also be simple to learn, because there isn’t any kind of complex API.
The idea of application workflow is following:
Actions are things that gets users input, does querys to database, handle data, etc.
Render segment is in 2 parts:
- View is a HTML document with php links to blocks
- Blocks is a piece on a view. Example a content area/navigation.
Then there is 4 different helpers. Helpers are small code snippets that should be executed, but really aren’t part of actions/views
- Pre-action helpers – stuff that is executed before actions
- Pre-render helpers – before render
- Post-render helpers – and after render
- Normal helpers – can be used anywhere in code, called by specific function.
And if I will ever get this done, I will publish this under open source license.




