Coupling

This page contains information on coupling between components of the library. The framework as a whole aims to be as de-coupled as possible – so that components can be used separately and where required. If you’re interested in using a component singularly in your app (without installing the entire framework) then you should consult this page first.

As a general rule, you should install the components from a sub-namespace if you are using a component stored in the library root. For example, if you want to use Config you should include the Config directory. While you may have components you’re not using in this directory (e.g. you only use Ini config files, not Xml) – more notably with Db – you’ll likely only need one adapter – these shouldn’t impact on the performance of your application since they are not loaded at runtime, until called by an autoloader.

Component	Dependencies (library components)
Config	None
Config\Ini	Config, Exception
Controller	Optionally, Registry and Router can be set in the controller
Db	Exception, Db\Adapter
Db\Adapter	Db, Exception
Db\Table	Db
Db\Adapter\Mysqli	Exception
Exception	If logging is enabled, Log, Log\Adapter and the Log\Adapter of choice
Loader	Exception
Log\Adapter	None
Log\Adapter\File	Exception, Log\Entry\File
Log\Entry	None
Log\Entry\Filter	None
Model	Exception
MVC	None
Pagination	None
Registry	None
Router	MVC, Router\DefaultRoute, Router\Route (if adding routes)
Router\DefaultRoute	None
Router\Route	None
User	Db
User\Session	Db, User
View	Exception