xterm wroteWelcome aboard, enjoy your stay.
What kind of framework? Would be nice to know what features you plan on adding and how it differentiates from the 10989384 frameworks available out there.
Kassem wroteI am also into PHP and I just love what this easy language is capable of doing :)
The problem with php is that it promotes bad design if you're using it in it plain self. Unless you use a framework that focuses on a certain design pattern, you're bound to fall into the common problems everyone face. Take a day off from your usual daily efforts and try to read a little bit about the available web frameworks out there and see what they provide you (not just php).
I do agree that PHP at first encourages bad coding habits specially with mixing output with code, and just with how it is designed and the dynamic __get__set when used wrongly and
As for the framework, I did scan the CakePHP manual and worked a bit on Zend. It doesn't matter what differentiate my framework from the res, working on my framework helps me understand how frameworks work, so the experience gained regardless of whether it is unique or useful is useful as I am doing it just so I would learn.
Now my framework is pretty much centered around using Aspect Oriented Programming implemented in PHP at runtime (without extra apache/php modules) and that is mostly achieved by the Databus pattern. Mainly what m trying to do is separate the logic of persistence and such from the actual model and such so I could just enable disable them, currently I have a cache and database persistence layer for simple models which acts totally transparently on the model by using the AOP feature of the framework. Also m trying to create new designs that are simple and very easy to modify, mainly the framework supports swapping of the Router, Dispatcher, Config and View by custom classes [based on interface] in the application so these are easily swapped through an XML loader file. Also in the model perspective m trying to compose a model from a set of Roles that can be assigned dynamically (think about it like Dynamic Multiple Classification) I still havent documented thoroughly the framework though, but I do have internal phpdoc documentation and basically most of the API is documented.
It's mainly about using whatever I learned across the last 3 years related to PHP and try to make something clean, and VERY simple yet flexible design wise. Cake and Zend are too conventional and do not exploit the PHP dynamic features in certain areas, I use for instance alot of __call coupled with the ReflectionAPI of php to acheive very flexible patterns thing like importing class within a class and such
For those of you interested the repository is found at:
http://repos.codealife.com:82/requiem/rdk/