Download the PHP package gsteel/looker without Composer
On this page you can find all versions of the php package gsteel/looker. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 looker
"Looker" - Another PHP HTML Templating Library
This library is modelled after laminas-view but has less functionality 🙃
It doesn't have any of the legacy associated with the MVC framework, and has a plugin manager that keeps track of stateful plugins so that they can easily be reset for each rendering cycle.
State in plugins is often unavoidable, but it's a pain in the ass in long-running processes such as Swoole and Roadrunner etc. This library attempts to make dealing with that state safer, easier and more obvious.
If you are familiar with laminas-view, then a lot of what's here should be familiar too.
'Looker' is in active development and won't be preserving BC until a 1.0 release.
Configuration
The primary target for this lib is a Mezzio application, that said, it doesn't come with any useful bindings for Laminas/Mezzio apps. For that, have a look at gsteel/looker-mezzio.
With that out of the way, basic configuration can be found in the Config Provider and you'll most likely be interested in setting up template files:
Configuring Templates
As per laminas-view, we have "template resolvers". 3 of them:
MapResolverDirectoryResolverAggregateResolver
Map Resolver
The map resolver requires one-to-one mapping of template name to on-disk file:
Given the above configuration, you would render the template with:
Directory Resolver
The directory resolver iterates over the configured directories in order and attempts to find the template name provided, if necessary, appending the defaultSuffix when no file name extension is provided.
Given the above configuration, the resolver would yield:
Aggregate Resolver
The aggregate resolver composes multiple resolvers and iterates over each in order until it finds the first resolver that can find the given template name.
Each configured resolver must be a \Looker\Template\Resolver instance that can be retrieved from the DI container in use.
With the above configuration, first the Map resolver would be consulted and then the directory resolver.
Documentation
Is lacking - at some point I'll get around to improving it… maybe.
Contributing
Once you cloned the project and made your changes in a branch, please run make qa to ensure that all QA tools run successfully before opening a PR 👍
All versions of looker with dependencies
gsteel/dot Version ^1.7
laminas/laminas-escaper Version ^2.13
psr/container Version ^1.0 || ^2.0
webmozart/assert Version ^1.11