Download the PHP package mouf/html.renderer without Composer
On this page you can find all versions of the php package mouf/html.renderer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mouf/html.renderer
More information about mouf/html.renderer
Files in mouf/html.renderer
Package html.renderer
Short Description This package contains the rendering mechanism of the Mouf framework. It is a mechanism allowing packages/templates/developers to overload a default template for various HTML objects.
License MIT
Homepage http://mouf-php.com/packages/mouf/html.renderer
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package html.renderer
What is this package?
This package contains a rendering mechanism to render objects in HTML.
For application developers
You are an application developer? Learn how to use the rendering system with PHP files or Twig templates to render your objects or overload renderers provided by packages.
See the video!
For package developers
You are a package developer? Learn how to use the rendering system to allow other users to overload your renderers easily.
Installation
The easiest way to use this package is through a dependency injection container compatible with container-interop/service-providers.
Once installed, you need to register the Mouf\Html\Renderer\RendererServiceProvider into your container.
If your container supports thecodingmachine/discovery integration, you have nothing to do. Otherwise, refer to your framework or container's documentation to learn how to register service providers.
Provided services
This service provider provides the following services:
| Service name | Description |
|---|---|
RendererInterface::class |
The default renderer. An alias to ChainRenderer::class |
ChainRenderer::class |
A composite renderer asking all other renderers in turn if they can render an object. |
customRenderers |
A list of RendererInterface objects at the "custom" level (top most level). This list is consumed by the ChainRenderer |
customRenderer |
A default custom renderer is provided by this package. Out of the box, template files are expected to be in the src/templates directory. |
packageRenderers |
A list of RendererInterface objects at the "package" level (bottom level). This list is consumed by the ChainRenderer. When a package you install has a renderer, it will add the renderer to this list (most of the time using the AbstractPackageRendererServiceProvider |
InitRendererFacadeMiddleware::class |
A PSR-15 middleware that is used to initialize global access to the default renderer. This is needed for the Renderable trait to work. |
Extended services
This service provider extends those services:
| Name | Compulsory | Description |
|---|---|---|
MiddlewareListServiceProvider::MIDDLEWARES_QUEUE |
yes | The InitRendererFacadeMiddleware::class registers itself in the list of PSR-15 middlewares. |
Mouf package
This package was originally part of Mouf (http://mouf-php.com), an effort to ensure good developing practices by providing a graphical dependency injection framework.
V2 makes the package framework-agnostic, so it can be used in any framework.
Basically, you will find in this package some Renderers. These are classes in charge of rendering other objects. They usually rely on template files, that contain the HTML to be rendered. Renderers can be chained, and the first renderer that knows how to render an object will be in charge of the rendering.
Troubleshooting
Your template or a custom template is not applied.
- Purge the cache with the red button in mouf.
- You use Ajax and you return html with echo (for example BCE).
- By default an echo don't apply the template to make it
- add the defaultRenderer (a class of Mouf\Html\Renderer\AutoChainRenderer) in your class
- add your templateRenderer (a class of Mouf\Html\Renderer\FileBasedRenderer) in Bootstrap this is bootstrapRenderer
- add the code before your call to the function toHTML: $this->defaultRenderer->setTemplateRenderer($this->templateRenderer);
- By default an echo don't apply the template to make it
All versions of html.renderer with dependencies
mouf/utils.cache.apc-cache Version ~2.0
twig/twig Version ^1 || ^2
mouf/html.htmlelement Version ~2.0
mouf/html.renderer.twig-extensions Version ^3
psr/simple-cache Version ^1
psr/container Version ^1
container-interop/service-provider Version ^0.4
thecodingmachine/funky Version ^1
mindplay/composer-locator Version ^2.1.3
psr/http-message Version ^1
psr/http-server-middleware Version ^1
psr/http-server-handler Version ^1
thecodingmachine/middleware-list-universal-module Version ^1.1.1