Download the PHP package dmlogic/assets without Composer

Assets

ANOTHER static Asset manager package for PHP 5.3+

This one is designed to support the following workflow:

• Assets are defined as Containers of one or more stylesheets or scripts
• Container contents can vary between environments
• Your app controllers or endpoints can render Containers ready for views via a very simple interface
• The package does NOT currently compile or combine assets - you would do that using your build/deploy process and reflect the differing Container contents in your environments
• Very extensible. More StaticAssets could be added such as SASS, LESS or Coffeescript. Or maybe even an Image class that outputs the Picture element. See comments in the Classes for more info

Installation

Install via Composer (dmlogic/assets) or

include 'Assets/Assets.php';
include 'Assets/StaticAsset.php';
include 'Assets/Script.php';
include 'Assets/Style.php';

use Dmlogic\Assets\Assets as Assets;

Installing to Laravel 4

Add the following to the 'require' section of your composer.json file.

"dmlogic/assets": "*"

Now run composer update.

You can then use the package immediately via the namespace e.g.

$myContainer = Dmlogic\Assets\Assets::container();

However, for easier usage, complete the following steps.

Add an Alias

Open the file app/config/app.php and add a line to the 'aliases' array:

'Assets' => 'Dmlogic\Assets\Assets'

You can now access the main class using

$myContainer = Assets::container();

Utilise cascading config files

Create an assets.php file in your app/config folder and add an array as described in the 'Generate Containers from text arrays' section below.

Then duplicate and adjust this file for your different environment folders.

Usage

The interface is a simplified form of the Laravel 3 Asset class. Create one or more containers, add assets to them and then render within a view.

Create new containers

This one will be called 'default'

$myContainer = Assets::container();

This one will be called 'home'

$homeContainer = Assets::container('home');

Add an asset

$myAsset = new Dmlogic\Assets\Style(array(
                                        'path'  => '/assets/css/bootstrap.css',
                                        'media' => 'screen'
                                     ))
$myContainer->add($myAsset);

Render the Container

<?= $myContainer->styles() ?>

and

<?= $myContainer->scripts() ?>

Create named container and add multiple assets in one command

$myAssets = array(

    new Dmlogic\Assets\Style(array(
                                'path'  => '/assets/css/bootstrap.css',
                                'media' => 'screen'
                             )),

    new Dmlogic\Assets\Style(array(
                                'path'  => '/assets/css/print.css',
                                'media' => 'print'
                             )),

    new Dmlogic\Assets\Script(array(
                                'path' => '/assets/js/bootstrap.js',
                              ))

    new Dmlogic\Assets\Script(array(
                                'inline' => 'console.log("useful, huh?")'
                              ))
);

Assets::container('home')->add($myAssets);

Render assets from named Container

echo Assets::container('home')->styles();

echo Assets::container('home')->scripts();

Generate Containers from text arrays

One of the most likely uses of this package is to define your containers in config files that vary per environment. A method createContainer() is available to make this a simple process. It accepts two parameters, a config array in the format described here and the name of the container.

$containers = include '/config/packages/[your_environment]/assets.php';

$defaultAssets = Assets::createContainer( $containers['default'] );

$homeAssets = Assets::createContainer( $containers['home'], 'home' );

Roadmap

• Decent Exception handling
• Picture Element Asset type perhaps?
• Sizable image Asset type perhaps?
• SVG with PNG fallback for old IE perhaps?