Honestly, you've developed a bad coding habit already. I am not trying to be negative here, but the way I see it, you will have a hard time correcting them. Also, I second the moderator's comments above in regards to your excessive used of static methods. The way I see it, you are not using a framework.
If your only reason to use static method and properties is due to the namespacing, then you must find a way of creating a general config page.
So instead of doing this
class Filter
{
protected static $do;
/* or */
public static $do;
}
why not put $do in the bootstrap file or in the config file..
If you are using static to mimic a Framework, then frameworks uses static methods to serve immediate response to user's requests. However, there are underlying processes behind those static methods.
for example if you see
ParseController::getController();
On the view side, the above appears to be static. However, the getController() method can be returning an instantiated object + method setting a controller.
so, it can be something like this
class ParseController
{
public $controller;
public function __construct()
{
}
public function setController()
{
return $this->controller;
}
public static function getController()
{
$object = new ParseController;
return $object->setController();
}
}
Things can be very tricky ...