Hi folks! My code is in: https://github.com/rg1024/aiki-ideas To install copy over a /var/www/ dir.
Aiki, imho, have two main problems: code and conceptual errors. This git works around code: - all code (libs) have at test. You can see test suit in /test (i want use PphUnit) - all 3rd code is integrated in aiki. See for example: libs/Db.php. - aiki object:* with autoload (for example $aiki->user loads Users libs). - libs (components) 1) simpler, testable, one clear task, modular. 2) don't re-discover the wheel. For example: Cache must be very very simple because there are other and better libraries. 3) without global var: in constructing phase they will receive a config object or complete aiki object. 4) with a special function, called configure, that describes/stores information about how configure the component. See libs/Cache.php, libs/User.php. Conclusion and planning. - These are first steps. We can apply this to our old aiki, or to aiki2, or slim-mustache. - i will be out one month (holidays!!) .but I will continue thinking about these ideas, and very concerned about Bassel.
_______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
