Agile Core is a collection of PHP Traits for designing object-oriented frameworks

Run-Time Tree (containers)

When you want your framework to look after relationships between objects by implementing containers, you can use ContainerTrait.

You will be able to use ContainerTrait::getElement() to access elements inside container:

$object->add(new AnoterObject(), 'test');
$another_object = $object->getElement('test');

If you additionally use TrackableTrait then your objects also receive unique “name”. From example above:

  • $object->name == “app_object_4”
  • $another_object->name == “app_object_4_test”


When object is created, the constructor is executed. Sometimes your object needs to be aware of it’s environment, and that’s why initializer will allow your developers to extend init() method, that will be called after your new object is integrated into the environment, if you use InitializerTrait:

class MyClass {
    use InitializerTrait;

    function init()

        // some variables are available here
        // echo $this->owner;
        // echo $this->name;
        // echo $this->app;


Normally you can only add existing objects into your run-time tree. FactoryTrait will allow you to specify the class name:


This will also enable similar features for Modelable objects:

// same as
$object->setModel(new Model_MyModel);

You can specify namespaces with backslash or regular slash:

// same as
$object->setModel(new data\Model_MyModel);

Dynamic Methods

DynamicMethodTrait adds ability to add methods into objects dynamically. That’s like a “trait” feature of a PHP, but implemented in run-time:

$object->addMethod('test', function($o, $args){ echo 'hello, '.$args[0]; } );
// outputs: hello, world

There are also methods for removing and checking if methods exists, so:

method_exists($object, 'test');
// now should use

// and this way you can remove method


HookTrait adds and trigger hooks for objects:

$object->addHook('test', function($o){ echo 'hello'; }
$object->addHook('test', function($o){ echo 'world'; }

// outputs: helloworld

Modelable Objects

In an MVP concept you have 3 types of objects - Models, Views and Presenter. The Presenter is responsible for creating and linking View and Model together.

Views are generic presentation widgets that can gain some insight into your data through the Model declaration.

ModelableTrait allows you to associate object with a Model:


// or

$grid->setModel($order->ref('Items'), ['name', 'qty', 'price']);

Quick Exception

When you are throwing exception somewhere in your logic, you have to collect enough information about the context. Sometimes it’s easier to let your framework do it for you. Add QuickExceptionTrait and you can throw exceptions like this:

throw $object->exception(['Incorrect foo value', 'foo'=>$bar]);

This is similar to the regular exception, however in addition to back-trace this will capture information about $object. This object will also be able to add more information into your query:

throw $db->exception('Bad Query', 'QueryException');

class QueryException extends Exception {
    protected $query;

    function __construct($object){
        $this->query = $object->getDebugQuery();

App Scope

Typical software design will create the application scope. Most frameworks relies on “static” properties, methods and classes. This puts some limitations on your implementation (you can’t have multiple applications).

AppScopeTrait will pass the ‘app’ property into all objects that you’re adding, so that you know for sure which application you work with:


class Object2 {
    use AppScopeTrait;
    use InitializerTrait;

    function init() {


        echo 'app is = '.$this->app;


When application is executed in environment, some objects of the applications may want to “record their state” in session scope. Technically this could be routed through the data source in the application that handles the session, but PHP has a wonderful support for $_SESSION already.

SessionTrait makes it possible for objects to have unique data-store inside a session.

This feature can be used by Views / Widgets that needs session info.


$this->setField('search', $this->recall('search', null));

// on submit

$this->memorize('search', $_POST['search']);

The session store is unique for each object identified by their “name” property.


DebugTrait allows your objects to execute:

$object->log('something happened');
$object->warn('bad things happen');

The debug will only be collected if the debug mode is turned on, otherwise calls to log() and warn() will be ignored.