Download the PHP package locomotivemtl/charcoal-view without Composer

Charcoal View

The Charcoal\View module (locomotivemtl/charcoal-view) provides everything needed to render templates and add renderer to objects.

It is a thin layer on top of various rendering engines, such as mustache or twig that can be used either as a View component with any frameworks, as PSR-7 renderer for such frameworks (such as Slim)

It is the default view layer for charcoal-app projects.

Table of content

• How to install
  • Dependencies
• Basic Usage
  • Using the Renderer, with Slim
• Module components
  • Views
    • Generic View
  • View Engines
    • Mustache Helpers
  • Loaders
    • Templates
  • Viewable Interface and Trait
  • View Service Provider
• Development
  • Development dependencies
  • Coding Style
  • Authors

How to install

The preferred (and only supported) way of installing charcoal-view is with composer:

To install a full Charcoal project, which includes charcoal-view:

Dependencies

• PHP 7.1+
  • Older versions of PHP are deprecated, therefore not supported.
• psr/http-message
  • Charcoal View provides a PSR7 renderer.
• locomotivemtl/charcoal-config
  • The view objects are configurable with \Charcoal\View\ViewConfig. locomotivemtl/charcoal-translator
  • The translator service
• erusev/parsedown
  • A markdown parser, which is provided to engines or could be used as a service.

Optional dependencies

• mustache/mustache
  • The default rendering engine is mustache, so it should be included in most cases.
  • All default charcoal modules use mustache templates.
• twig/twig
  • Twig can also be used as a rendering engine for the view.
• pimple/pimple
  • Dependencies management can be done with a Pimple ServiceProvider(\Charcoal\View\ViewServiceProvider)
  • It is actually required by default in charcoal-app.

👉 Development dependencies are described in the Development section of this README file.

Basic Usage

A View can be used to render any template (which can be loaded from the engine) with any object (or array, for twig) as context.

Basic Usage, with service provider

All this bootstrapping code can be avoided by using the ViewServiceProvider. This provider expects a config object

👉 The default view engine, used in those examples, would be mustache.

Using the Renderer, with Slim

A view can also be implicitely used as a rendering service. Using the provided view/renderer, with a PSR7 framework (in this example, Slim 3):

Just like the view, it is possible to simply register all dependencies on a Pimple container (with the ViewServiceProvider) to avoid all this bootstrapping code. The renderer is available as $container['view/renderer'].

Module components

The basic components in charcoal-view are:

• View, which provide the basic interface to all components.
• Engine, to actually render the templates.
• Loader, to load template files.
• Viewable, which allow any object to be rendered with a View.
• Renderer, an extra helper to use a view to render into PSR-7 request/response objects.

Views

The Charcoal\View\ViewInterface defines all that is needed to render templates via a view engine:

• render($templateIdent = null, $context = null)
• renderTemplate($templateString, $context = null)

The abstract class Charcoal\View\AbstractView fully implements the ViewInterface and adds the methods:

Generic view

As convenience, the \Charcoal\View\GenericView class implements the full interface by extending the AbstractView base class.

View Engines

Charcoal views support different templating Engines_, which are responsible for loading the appropriate template (through a loader) and render a template with a given context according to its internal rules. Every view engines should implement \Charcoal\View\EngineInterface.

There are 3 engines available by default:

• mustache (default)
• php
• twig

Mustache Helpers

Mustache can be extended with the help of helpers. Those helpers can be set by extending view/mustache/helpers in the container:

Provided helpers:

• Assets helpers:
  • purgeJs
  • addJs
  • js
  • addJsRequirement
  • jsRequirements
  • addCss
  • purgeCss
  • css
  • addCssRequirement
  • cssRequirements
  • purgeAssets
• Translator helpers:
  • _t Translate a string with {{#_t}}String to translate{{/_t}}
• Markdown helpers:
  • markdown Parse markdown to HTML with {{#markdown}}# this is a H1{{/markdown}}

Loaders

A Loader service is attached to every engine. Its function is to load a given template content

Templates

Templates are simply files, stored on the filesystem, containing the main view (typically, HTML code + templating tags, but can be kind of text data).

• For the mustache engine, they are .mustache files.
• For the php engine, they are .php files.

Templates are loaded with template loaders. Loaders implement the Charcoal\View\LoaderInterface and simply tries to match an identifier (passed as argument to the load() method) to a file on the filesystem.

Calling $view->render($templateIdent, $context) will automatically use the engine's Loader object to find the template $templateIdent.

Otherwise, calling $view->renderTemplate($templateString, $context) expects an already-loaded template string as parameter.

Viewable Interface and Trait

Any objects can be made renderable (viewable) by implementing the Charcoal\View\ViewableInterface by using the Charcoal\View\ViewableTrait.

The interface adds the following methods to their implementing objects:

• setTemplateIdent($ident)
• templateIdent()
• setView($view)
• view()
• render($templateIdent = null)
• renderTemplate($templateString)

Examples

Given the following classes:

The following code:

would output: "Hello world!"

View Service Provider

As seen in the various examples above, it is recommended to use the ViewServiceProvider to set up the various dependencies, according to a config, on a Pimple container.

The Service Provider adds the following service to a container:

• view The base view instance.
• view/renderer A PSR-7 view renderer.
• view/parsedown A parsedown service, to render markdown into HTML.

Other services / options are:

• view/config View configuration options.
• view/engine Currently used view engine.
• view/loader Currently used template loader.

The ViewServiceProvider expects the following services / keys to be set on the container:

• config Application configuration. Should contain a "view" key to build the ViewConfig obejct.

The View Config

Most service options can be set dynamically from a configuration object (available in $container['view/config']).

Example:

Development

To install the development environment:

Run tests with

API documentation

• The auto-generated phpDocumentor API documentation is available at https://locomotivemtl.github.io/charcoal-view/docs/master/
• The auto-generated apigen API documentation is available at https://codedoc.pub/locomotivemtl/charcoal-view/master/

Development dependencies

• phpunit/phpunit
• squizlabs/php_codesniffer
• satooshi/php-coveralls
• pimple/pimple
• mustache/mustache
• twig/twig

Continuous Integration

Service	Badge	Description
Travis		Runs code sniff check and unit tests. Auto-generates API documentation.
Scrutinizer		Code quality checker. Also validates API documentation quality.
Coveralls		Unit Tests code coverage.
Sensiolabs		Another code quality checker, focused on PHP.

Coding Style

The Charcoal-View module follows the Charcoal coding-style:

• PSR-1
• PSR-2
• PSR-4, autoloading is therefore provided by Composer.
• phpDocumentor comments.
• Read the phpcs.xml file for all the details on code style.

Coding style validation / enforcement can be performed with composer phpcs. An auto-fixer is also available with composer phpcbf.

Authors

• Mathieu Ducharme [email protected]
• Locomotive

License

Charcoal is licensed under the MIT license. See LICENSE for details.