README

Envision is a framework extension for Laravel 4.2.

The goal of using Envision is speeding up development. It does a few things to help with that:

Generate and autoload classes that Envision recognises on-the-fly.
Uses the Ardent package automatically.
Uses the Presenter package automatically.

Installation

Envision depends on the Ardent and the Presenter packages in your Laravel framework. So please add those packages as well. Add shincode/envision, Ardent and Presenter to composer.json.

"require": {
  "laravel/framework": "4.2.*",
  "shincode/envision": "dev-master",
  "laravelbook/ardent": "2.5.*",
  "robclancy/presenter": "1.3.*"
}

Update with composer:

composer update

Add the serviceproviders in app/config/app.php:

'Shincode\Envision\EnvisionServiceProvider',
'Robbo\Presenter\PresenterServiceProvider',

Copy the config file:

php artisan config:publish shincode/envision

In app/config/packages/shincode/envision/settings.php, set autoload and create to true to enable speed development

'autoload' => true,
'create' => true,

Example

Here's a mini tutorial. Let's create a table called phones for our database. Run the follow artisan command:

php artisan migrate:make create_phones_table

Let's edit that file (keeping it simple)

public function up() {
	Schema::create('phones', function(Illuminate\Database\Schema\Blueprint $table) {
		$table->increments('id');
		$table->string('name');
		$table->timestamps();
	});
}

Run the migration

php artisan migrate

Now add this to app/routes.php

Route::controller('phone', 'PhoneController');

Notice how you haven't created any files yet, but instantly refer to the PhoneController. Run the application.You'll see that a PhoneController.php has appeared in your app/controllers structure.

Let's open this controller and add a function

public function getIndex() {
	PhoneResource::insert(array('name' => 'Sunkia'));
	PhoneResource::insert(array('name' => 'Nosy'));
	PhoneResource::insert(array('name' => 'Namnung'));
}

See where it's going? You never actually made the classes, you're just writing what you want to do. First we created generic routing method. Now we populate the database a little bit so we have something to work with. Since we created a controller route to 'phone', all we have to do now is to go URL /phone and the function will be executed. Of course we normally use a seed for this, but this way you understand how easy it is to create new entries.

The next step is to display them. Let's see how that works. Change the getIndex to something else:

public function getIndex() {
    $phones = PhoneResource::all();
    return View::make('phone')->with('phones', $phones);
}

Let's make a view file as well and save it as view/phone.blade.php

@foreach($phones as $phone)
	<h1>{{ $phone->name }}</h1>
@endforeach

Now open the URL to /phone and you'll notice it just works!

By now you should see there are a few new files created. We've been using the Resource class, the Ardent class and the Presenter class.

Let's try using the Presenter class. There should be a new folder in your app folder called 'presenters'. Open PhonePresenter.php and add the following function

public function presentFoo() {
	return 'bar';
}

Now let's edit view/phone.blade.php to

@foreach($phones as $phone)
	<h1>{{ $phone->name }}</h1>
	<span>{{ $phone->foo }}</span>
@endforeach

And there it is. Additional view logic right at your fingertips. For more information about the presenter, check here: https://github.com/robclancy/presenter

Ardent example will be added later, for now you can read about ardent here: https://github.com/laravelbook/ardent

Deployment

For development, having Envision is really nice. But when deploying, it's highly recommended to turn off auto-generation. In app/config/packages/shincode/envision/settings.php (if you have published the config) you can change the following:

autoload = Automatically tries to find classes used by Envision. Can be left on but it has some impact on performance. For a final deployment, it's recommended to actually autoload all the files and create aliases in app.php.
create = Automatically generate classes when not found. Highly recommended to disable when deploying for obvious reasons.
log = Not doing anything at the moment.

I recommend using environments. For example, I use the local environment to develop and have a copy of settings.php in app/config/packages/shincode/envision/local/settings.php. By default, I have both options on disabled by default in the package, so the package is essentially 'off' on install, for safety reasons.

Contributing To Envision

All issues and pull requests should be filed on the shincode/envision repository.

License

Envision is open-sourced software licensed under the MIT license

shincode / envision

Maintainers

Details