Download the PHP package revelateur/bladerunner without Composer

On this page you can find all versions of the php package revelateur/bladerunner. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package bladerunner

Bladerunner

WordPress plugin for Laravel Blade templating.

To install it to your Composer based WordPress installation:

Activate the plugin inside WordPress and templates with *.blade.php are inspected and active. Your theme still needs an index.php due to WordPress basic functionality. When removed the theme is known as broken.

If you don't use a composer based WordPress development environment you can download the latest distributed plugin at Bladerunner site http://bladerunner.aekab.se and install it the common way with zip upload to WordPress via wp-admin.

Releases to this plugin is listed last in this readme.

Hello World

  1. Install the library with composer
  2. Make sure the cache-folder is writeable in uploads, eg ../wp-content/uploads/.cache
  3. Activate the plugin
  4. Create a view, eg:

  5. In your index.php, add a global call for the view created, eg:

https://laravel.com/docs/5.2/blade

Cache

Directories

Template helper

There is a template helper function named bladerunner, defined globally to use in standard WordPress templates.

Example: You want to create a 404-template and don't want to use the .blade.php extension to the template file.

You can pass any data with the global bladerunner function like so,

or use compact, eg:

Controllers

With version 1.7 controllers are added to Bladerunner. As default Bladerunner will look for extended classes in the theme folder + /controllers. If you would like to add or change the controller paths take a look below at filters!

The controller class has to extend \Bladerunner\Controller to work. It will guess the path to the view but you can override this with protected $view='your.custom.view.path''

The controller files follow the same hierarchy as WordPress. You can view the controller hierarchy by using the Blade directive @debug.

Extend the Controller Class, it is recommended that the class name matches the filename. Create methods within the Controller Class:

Controller example:

The following example will expose $images to views/single.blade.php

controllers/Single.php

views/single.blade.php

Hooks and Filters

Bladerunner continuously implements filters and hooks to modify values and processes.

Hooks

...

Filters

Modify Bladerunners cache folder path, default ../wp-content/uploads/.cache

If you don't want Bladerunner to create the cache folder:

If you wan't to customize the base paths where you have your views stored, use:

If you wan't to customize the controller paths where you have your controllers stored, use:

We will soon add more WordPress extenstions to the Bladerunner engine. Please give us your great examples to implement!

Links

Tests

Test requirements:

Test step by step

Checkout the components for testing via Composer inside the repo:

Using Testrunner (required-dev package) and Docker the test should be exexuted with a single command:


All versions of bladerunner with dependencies

PHP Build Version
Package Version
Requires php Version ^7.3 || ^8.0
illuminate/config Version ^8.6
illuminate/view Version ^8.6
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package revelateur/bladerunner contains the following files

Loading the files please wait ....