Class AbstractFactory

oroboros\core\abstracts\OroborosBaseAbstract implements oroboros\core\interfaces\BaseAbstractInterface uses oroboros\core\traits\BaseTrait

oroboros\core\abstracts\patterns\creational\AbstractFactory

Direct known subclasses

oroboros\core\patterns\creational\AdapterFactory, oroboros\core\patterns\creational\AppFactory, oroboros\core\patterns\creational\ControllerFactory, oroboros\core\patterns\creational\FactoryFactory, oroboros\core\patterns\creational\LibraryFactory, oroboros\core\patterns\creational\ModelFactory, oroboros\core\patterns\creational\ModuleFactory, oroboros\core\patterns\creational\TemplateFactory, oroboros\core\patterns\creational\ViewFactory

Abstract
Namespace: oroboros\core\abstracts\patterns\creational
Author: Brian Dayhoff brian@mopsyd.me
Note: This is not the AbstractFactory design pattern. This is literally an abstraction of the Oroboros Factory.
Located at core/abstracts/patterns/creational/AbstractFactory.php

Methods summary

`public`	# `__construct( array $params = array(), array $flags = array() )` All non-utility classes in the oroboros system use this constructor. Utility classes are considered to be any class that extends from a non-core class. All non-utility classes in the oroboros system use this constructor. Utility classes are considered to be any class that extends from a non-core class. Parameters `$params` `$flags` Since 0.0.2a Overrides `oroboros\core\traits\BaseTrait::__construct`
`public`	# `__destruct( )` No operation. No operation. Since 0.0.1a Overrides `oroboros\core\traits\BaseTrait::__destruct`
`public`	# `initialize( array $params = array(), array $flags = array() )` Provides an unopinionated way to initialize parameters and flags. This class does nothing with the parameters or flags aside from storing them so they can be referenced and checked against. Child classes should implement their own functionality around this, but it can be safely ignored entirely. Provides an unopinionated way to initialize parameters and flags. This class does nothing with the parameters or flags aside from storing them so they can be referenced and checked against. Child classes should implement their own functionality around this, but it can be safely ignored entirely. Parameters `$params` `$flags` Since 0.0.1a Note Parameter and flag initialization can also happen directly in the constructor if they need to be exposed before your class initialization method runs, or may be exposed at both if you need to separate pre-initialization parameters from initialization parameters.
`public`	# `load( $type, array $params = array(), array $flags = array() )`
`public`	# `fetch( $source, $type, array $params = array(), array $flags = array() )`
`public`	# `source( $source )`
`protected`	# `_validSources( array $sources )`
`protected`	# `_getSourceResource( )`
`protected`	# `_checkSource( $source )`
`private`	# `_setSource( $source )`
`private`	# `_setValidSources( array $sources )`