Download the PHP package kesty/view without Composer
On this page you can find all versions of the php package kesty/view. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package view
Short Description Laravel View Standalone
License MIT
Homepage https://github.com/olubunmi708/views
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 view
The Lara Blade View | Blade Template Outside Laravel
Laravel Blade Views Standalone
Okay so by now hopefully you have heard of Laravel, the PHP framework that just makes things easy. So first things first full credit goes to Taylor Otwell and Brad Jones for the Blade API.
How to Install
Installation via composer is easy:
composer require kesty/view: dev-masterHow to Use
In your legacy - non Laravel application. You can use the Laravel Blade API like so:
And thats it, now you can use code like the following:
Where the view might look like:
For more info on the View API it's self see: http://laravel.com/docs/responses#views http://laravel.com/docs/templates#blade-templating
View Scope
When you run it checks to see if the class exists globally. If not it use the function to alias it's self in much the same a Laravel Application does.
This enables us to use the API we are familar with.
View Include Path:
You can provide an array of paths, instead of just one path. So in effect you can have a View Include Path. Very handy for setting up a HMVC type system. Here is an example:
So now for the why?
While laravel is so awesomely cool and great. If you want to pull a feature out and use it in another project it can become difficult. Firstly you have to have an innate understanding of the IoC Container.
You then find that this class needs that class which then requires some other config variable that is normally present in the IoC when run inside a normal Laravel App but in your case you haven't defined it and don't really want to define that value because it makes no sense in your lets say legacy application.
Perfect example is when I tried to pull the session API out to use in wordpress. It wanted to know about a method, which I think comes from . At this point in time I already had to add various other things into the IoC to make it happy and it was the last straw that broke the camels back, I chucked a coders tantrum, walked to the fridge, grabbed another Redbull and sat back down with a new approach.
The result is this project.
Original Code by Brad Jones - [email protected] Maintained and Updated by Olubunmi Tosin - [email protected]
All versions of view with dependencies
gears/di Version *
illuminate/view Version 5.5.*
illuminate/events Version 5.5.*