Download the PHP package eftec/bladeone without Composer

BladeOne Blade Template Engine

BladeOne is a standalone version of Blade Template Engine that uses a single PHP file and can be ported and used in different projects. It allows you to use blade template outside Laravel.

[]() []() []() []() []() []()

Dynamic blade components are not supported (reason: performance purpose) and custom features aimed for blade, but everything else is supported.

Comparison with Twig

(spoiler) Twig is slower. 😊

What it was tested?. It was tested two features (that are the most used): It was tested with an array with 1000 elements and tested many times.

Comparison with Twig

NOTE about questions, reports, doubts or suggesting:

✔ If you want to open an inquiry, do you have a doubt, or you find a bug, then you could open an ISSUE.
Please, don't email me (or send me PM) directly for question or reports.
Also, if you want to reopen a report, then you are open to do that.
I will try to answer all and every one of the question (in my limited time).

Some example

ExampleTicketPHP	Example cupcakes	Example Search	Example Editable Grid
Custom control #1	Custom control #2

https://www.southprojects.com

Manual

• BladeOne Manual
• Template tags (views)
  • Template variables
  • Template inheritance
  • Template component
  • Template stack
  • Template asset, relative, base, current and canonical links
  • Template calling methods
  • Template logic
  • Template loop
  • Template Pipes (Filter)
• Custom Control
• Methods of the class
• Injecting logic before the view (composer)
• Extending the class
• Using BladeOne with YAF Yet Another Framework
• Differences between Blade and BladeOne
• Comparision with Twig (May-2020)
• Changelog
• Changes between 2.x and 3.0 and TODO
• Code Protection (Sourceguardian and similars)

PHP 5.x support?

This version does not support PHP 5.x anymore. However, you can use the old version that is 100% functional with PHP 5.6 and higher.

Laravel blade tutorial

You can find some tutorials and example on the folder Examples.

You could also check the Wiki

About this version

By standard, The original Blade library is part of Laravel (Illuminate components) and to use this template library, you require install Laravel and Illuminate-view components. The syntax of Blade is pretty nice and bright. It's based in C# Razor (another template library for C#). It's starting to be considered a de-facto standard template system for many PHP (Smarty has been riding off the sunset since years ago) so, if we can use it without Laravel then it's a big plus for many projects. In fact, in theory, it is even possible to use with Laravel. Exists different versions of Blade Template that runs without Laravel, but most requires 50 or more files, and those templates add a new level of complexity, so they are not removing Laravel but hiding:

• More files to manage.
• Changes to the current project (if you want to integrate the template into an existent one)
• Incompatibilities amongst other projects.
• Slowness (if your server is not using op-cache)
• Most of the code in the original Blade is used for future use, including the chance to use a different template engine.
• Some Laravel legacy code.

This project uses a single file called BladeOne.php and a single class (called BladeOne). If you want to use it then include it, creates the folders and that's it!. Nothing more (not even namespaces)*[]: It is also possible to use Blade even with Laravel or any other framework. After all, BladeOne is native, so it's possible to integrate into almost any project.

Why to use it instead of native PHP?

Separation of concerns

Let’s say that we have the next code

It leads to a mess of a code. For example, let’s say that we oversee changing the visual layout of the page. In this case, we should change all the code, and we could even break part of the programming.
Instead, using a template system works in the next way:

We are separating the visual layer from the code layer. As a plus, we could assign a non-php-programmer in charge to edit the template, and he/she doesn’t need to touch or know our php code.

Security

Let’s say that we have the next exercise (it’s a dummy example)

It could be separates as two files:

Even for this simple example, there is a risk of hacking. How? A user could send malicious code by using the GET variable, such as html or even javascript. The second file should be written as follows:

html_entities should be used in every single part of the visual layer (html) where the user could inject malicious code, and it’s a real tedious work. BladeOne does it automatically.

Easy to use

BladeOne is focused on an easy syntax that it's fast to learn and to write, while it could keep the power of PHP.

Let's consider the next template:

With BladeOne, we could do the same with

And if we use thehtml extension we could even reduce to

Performance

This library works in two stages.

The first is when the template calls the first time. In this case, the template compiles and store in a folder.
The second time the template calls then, it uses the compiled file. The compiled file consist mainly in native PHP, so the performance is equals than native code. since the compiled version IS PHP.

Scalable

You could add and use your own function by adding a new method (or extending) to the BladeOne class. NOTE: The function should start with the name "compile"

Where the function could be used in a template as follows

Alternatively, BladeOne allows running arbitrary code from any class or method if its defined.

Install (pick one of the next one)

1) Download the file manually then unzip (using WinRAR,7zip or any other program) https://github.com/EFTEC/BladeOne/archive/master.zip 2) git clone https://github.com/EFTEC/BladeOne (it doesn't include the examples) 3) Composer. See usage 4) wget https://github.com/EFTEC/BladeOne/archive/master.zip unzip master.zip

Usage

If you use composer, then you could add the library using the next command (command line)

If you don't use it, then you could download the library and include it manually.

Explicit definition

Where $views is the folder where the views (templates not compiled) will be stored. $cache is the folder where the compiled files will be stored.

In this example, the BladeOne opens the template hello. So in the views-folder it should exist a file called hello.blade.php

views/hello.blade.php:

Implicit definition

In this mode, it uses the folders and , also it uses the mode as MODE_AUTO.

Injection

You can inject the Bladeone using an existing instance of it. If there is no instance, then it will create a new one using the default folders.

Fluent

Filter (Pipes)

It is possible to modify the result by adding filters to the result.

Let's say we have the next value $name='Jack Sparrow'

Our view could look like:

What if we want to show the name in uppercase?.

We could do in our code $name=strtoupper('Jack Sparrow'). With Pipes, we could do the same as follows:

We could also add arguments and chain methods.

You can find more information on https://github.com/EFTEC/BladeOne/wiki/Template-Pipes-(Filter)

Security (optional)

If you log in using blade then you could use the tags @auth/@endauth/@guest/@endguest

or

Custom controls.

There are multiples ways to create a new control (tag)

Extensions Libraries (optional)

BladeOneCache Documentation

https://github.com/eftec/BladeOneHtml

Calling a static methods inside the template.

Since 3.34, BladeOne allows to call a static method inside a class.

Let's say we have a class with namespace \namespace1\namespace2

Method 1 PHP Style

We could add a "use" in the template. Example:

Add the next line to the template

and the next lines to the template (different methods)

All those methods are executed at runtime

Method 2 Alias

Or we could define alias for each class.

php code:

Template:

We won't need alias or use for global classes.

Named argument (since 3.38)

BladeOne allows named arguments. This feature must be implemented per function.

Let's say the next problem:

It is the old library BladeOneHtml:

And it is the new library:

The old method select only allows a limited number of arguments. And the order of the arguments is important.

The new method select allows adding different types of arguments

Command Line (CLI)

BladeOne (since the version v4.2) allows to run some operations via command line (CLI)

How to run it?

• Go to your home path and call the PHP script as follows:

Or change you folder according to your installation.

And you can set the syntax as follows:

• -templatepath (optional) the template-path (view paths).
  • Example: '/folder/views' or 'views' (relative)
• -compilepath (optional) the compile-path.
  • Example: '/folder/compiles or 'compiles' (relative)
• -clearcompile It deletes the content of the compile-path
• -createfolder It creates the "compile" and "template" folders
• -check It checks the library

Clear the compile-folder

Check the folders, if the folder exists, if it has the right permissions, etc.

Example to clear the compile-folder using a custom compile path

BladeOneHtml

It is a new extension to BladeOne. It allows creating HTML components easily and with near-to-native performance.

It uses a new feature of BladeOne: named arguments

Example to create a select:

https://github.com/eftec/BladeOneHtml

You could download it or add it via Composer

composer require eftec/bladeonehtml

Collaboration

You are welcome to use it, share it, ask for changes and whatever you want to. Just keeps the copyright notice in the file.

Future

• Blade locator/container

License

MIT License. BladeOne (c) 2016-2024 Jorge Patricio Castro Castillo Blade (c) 2012 Laravel Team (This code is based and inspired in the work of the team of Laravel, however BladeOne is mostly an original work)