Namespace Core

Extensible auto-loader used by Medusa Core with support for user-defined callbacks to support arbitrary file architectures.

Provides a cache for arbitrary data and driver-based storage. Cache entries are identified by a class and key that together form a unique hash. Additionally, a timestamp is stored with each entry and optionally a maximum age, after which entries are deleted.

Provides support for handling different kinds of characters sets: A basic set of string functions, conversion methods and character constants.

Interface to PHP native Closure instances. Embeds a Closure instance (aka lambda function) and provides an extended user interface including code and parameter retrieval and serialisation.

Provides access to core the configuration and application settings with support for drivers.

A controller implements application logic based on models and feeds data to views for rendering a corresponding output.

A Converter takes a constant data source and returns a transformed value. The interface is very similar to an Encoder or Decoder, but a Converter is not designed to work on streaming data sources. Additionally, the performed transformation is in general not reversible.

Data decoder interface to decode arbitrary data previously encoded with a corresponding encoder and optional support for data sources to provide transparent data decoding.

A delegate is a collection of callbacks that are invoked sequentially when the delegate itself is invoked.

A Dispatcher is responsible for delegating control to the controller action as specified by the request.

Provides encoding of arbitrary data. Encoders are commonly used to enable transparent data processing, such as escaping of HTML CDATA, password hashing, conversion of data streams. Additionally, encoder instances can be chained together to provide complex data conversion schemes.

A Field is a proxy object to an immutable (dynamic) data storage. Data storage access is available via array access or the Core\Field::getDataForKey() method. Field properties are separated from the data core, accessible through properties and KVC access inherited by Core\Set, and contain object specific values.

A Formatter transforms arbitrary data sources into a generally readable format according to a chained data output interface (e.g. a view).

Module resolver and loader. Also used by the auto-loader. Keeps track of loaded modules and automatically records time and memory states for modules if enabled in Core configuration.

Data node for parsed LDML locale data. Attributes are accessible via KDC field access, value and children via the corresponding KVC properties.

Represents the concept of a source file that is managed by the framework loader mechanisms and compatible with the auto-load system.

Object is the root class for most core class hierarchies. Object provides key-value coding support methods and generic helpers for all derived classes. Also, all Core\Object derived classes inherit a default implementation to the Core\Chainable interface.

A plugin provides means to extend an application with new functionality without requiring changes to the application itself.

A server offers services via a single connection method. If multiple connection methods (such as multiple ports) are offered, each is represented by an own server instance.

Provides translation of arbitrary data identified by keys with support for fallback locales.

Base class for views with integrated support for data encoders, a shared proxy view, automated renderer delegation and chained translator instance.

Interface to provide read access on (dynamic) properties. A class that implements this interface enables PHP-syntax property access to properties, which may not necessarily have been defined as class members. Additionally, checking the existence of properties via the library function isset() is possible.

Comparable conform classes implement a comparator method to compare two objects to determine an ordering for a set of objects. Implementations may decide to allow comparison to any type of value.

Equality conform classes implement an equality test between two objects. Implementations may decide to allow equality tests with any type of value.

Identity conform classes implement an identity test between two objects. This extends standard equality comparison to include more strict rules, e.g. the type of the compared objects must match.

Interface to provide read access to data fields. A class that implements this interface also implements standard PHP array access on its data fields, including support for isset() calls.

Interface to provide write access on (dynamic) properties. A class that implements this interface enables PHP-syntax property assignments for attributes that are not restricted to class members. Additionally, un-setting properties via the library function unset() is possible.

Interface for improved storage support. Storable instances implement data encoder and decoder methods to enable compact data storage, primarily used with Core Storage.

Base exception for all Core exceptions. Equals the default SPL exception but enables enhanced Core\Fault report functionality.

Core version string for display purposes. Includes major, minor and release version plus revision.