TechTrouts.com

Because it requires a few of the upcoming PHP features, naturePhp 0.1′s release is now on standby for PHP 5.3.0′s release. For now i can only say it is my favorite toolkit ever, and we’ve been using and improving it quite a lot on it’s limited PHP 5.2.6 version…

- ok, so it’s a biased opinion… :/

NaturePhp itself is basically a plug-in system for the coolest functionalities around – most of the upcoming functionalities are either gathered from wordpress, joomla!, CodeIgniter and others, as well as a few of our own – *and a few RubyOnRails original ideas implemented in php ;)

The functionalities are organized into classes, and the classes are organized into namespaces, providing a great deal of “space” for future plug-in developments.
It uses __autoload() for all classes, meaning it is just as fast no matter how many plug-ins you have installed.
NaturePhp does not aim being labeled as a framework, but, being a pluggable toolkit itself, it allows future developers to build their own frameworks as plug-ins. – The idea is to provide a stable ground for common development and lot’s of easy to use functionalities for developers – much like Phyton’s libraries.

We are currently using Namespace_Class::method() instead of Namespace::Class::method() and Class::callStatic($func_name, [$arg1, $arg2... $argN]) instead of Class::func_name([$arg1, $arg2... $argN]) to workaround the lack of “Namespaces” and method overloading “__callStatic()” support on PHP 5.2.6, as these two features are required for most of the toolkit functionalities.
It’s ugly, but it keeps the toolkit usable and developed while we wait for PHP 5.3.0.

As soon as PHP 5.3.0 comes out we’ll implement the necessary namespaces and change all the Class::callStatic($func_name, [$arg1, $arg2... $argN]) calls to Class::func_name([$arg1, $arg2... $argN]) – so probably a couple of weeks after PHP 5.3.0′s release we’ll have a NaturePhp 0.1 out ;)

While we wait, we’re also finishing the NaturePhp’s website at http://naturephp.org ;