UI.Layout directive 

This directive allows you to split stuff !
Holy grail demo

Requirements

- AngularJS

NOTE : if you use IE<=9, iOS<7 or Android<4 please include the requestAnimationFrame polyfill in your application.

NOTE : version 1.x is only compatible with IE>=10. If you use IE<=9 you need to use version 0.x

Installing

$3

``sh
npm install --save angular-ui-layout
`

module.exports of index.js is the string 'ui.layout' so you can include it as such:

`javascript
angular.module('myApp', [require('angular-ui-layout')]);
`

$3

`sh
bower install angular-ui-layout\#bower


or

bower install angular-ui-layout\#v0.0.0

or

bower install angular-ui-layout\#src0.0.0
`

This will copy the UI.Layout files into a bower_components folder, along with its dependencies. Load the script files in your application:

`html




`

Add the UI.Layout module as a dependency to your application module:

`javascript
var myAppModule = angular.module('MyApp', ['ui.layout']);
`

Usage

Add the directive like so:

`xml



or

`

If using a layout-container with ng-repeat, make sure to include a track by clause to the repeat, typically with $index:

`xml



`

Options

$3

Type: String
Default: 'row'
flow: row | column

A fake flex-direction property. It specifies how the child elements are placed in the layout container, by setting the direction of the flex container's main axis. This determines the direction that child elements are laid out in.

$3

Type: Integer
Default: 10

The size in pixels that you want the divider/splitbar to be. Set to 0 to hide the splitbar, which in turn prevents user resizing the surrounding containers.

$3

Type: Boolean
Default: false

Set to true if you don't want the toggle arrows appearing in the splitbar.

$3

Type: Boolean
Default: false

Like disableToggle above but only removes the arrows on mobile devices (max-device-width: 480px).




Child Attributes

$3

Required on all child elements of the ui-layout element.

`



`

$3

A string value 'central' can be passed to the directive:
`xml

`

The 'central' container takes up all the remaining space during resizing, regardless of previous state, e.g. after splitbar drag.

$3


Type: boolean

`xml



`

Controls collapsed state of the container. Application can store the state of the layout e.g. like so:
`javascript
$scope.layout {
toolbar: true,
leftSidebar: false,
mycontainer: false
}
`

Changing those values will toggle container. See also [ui.layout.toggle][event-toggle].

$3


Type: String

Sets the default placement of the splitbar.

`
pixels


percentage



`

$3

Type: String
Default: '8px'

Specifices the minimum size the child element can be set to. Defaults to the width of the splitbar if no value is provided.

`
pixels


percentage



`

$3

Type: String

Specifices the maxium size the child element can be set to.

`
pixels


percentage



`

Events

Events are broadcast on the scope where ui-layout is attached. This means they are available to any controller inside of a ui-layout container.

$3

Returns: string or null


Dispatched when the layout container finished loading. It returns the value of the attribute, e.g. ui-layout-loaded="my-loaded-message", or null. The null also means that the layout has finished collapsing all the containers that should be collapsed (per application request when setting the [collapsed][collapsed] attribute).

Collapsing container on application load currently goes through these steps:
1. layout is first loaded with all containers uncollapsed (disregarding user set values), then
2. containers are collapsed either:
- _automatically_: application has not set a string return value for the ui.layout.loaded event.
- _manually_: application sets collapsed flags in the callback passed to ui.layout.loaded

All this means that the user will notice a flicker. If the flicker is not desirable, hide the layout behind an overlay, wait for the ui.layout.loaded event. In the "automatic" mode, all is done and the layout should be presentable. In the "manual" mode it is up to the application to count the ui.layout.toggle events.

`xml



`

`javascript
$scope.$on('ui.layout.loaded', function(evt, id) => {
switch (id) {
case 'main-container':
...
break;
case 'child-container':
...
break;
default:
break;
}
});
`

Note: the value of the attribute is not evaluated, so:

`
$scope.layout = {
mySidebar: {someKey: 'some value'}
}


// $scope.$on will receive the string 'layout.mySidebar.someKey'
`

$3

Dispatched when a container is opened or closed. Element can be identified container.id, which is the same as element.id if provided, otherwise it is null.

`javascript
$scope.$on('ui.layout.toggle', function(e, container){
if ( container.size > 0 ){
console.log('container is open!');
}
});
`

Manually toggling (clicking the arrow button on the splitbar) will not update the collapsed attribute.
If the application is using the collapsed attribute of ui-layout-container to programmatically control the collapsed state, the application should update it's state when this event occurs to stay in sync with the UI.

$3

Dispatched as a splitbar is dragged, debounced to occur only every 50ms.

`javascript
$scope.$on('ui.layout.resize', function(e, beforeContainer, afterContainer){});
`




Testing

We use Karma and jshint to ensure the quality of the code. The easiest way to run these checks is to use grunt:

`sh
npm install -g gulp
npm install && bower install
gulp
`

The karma task will try to open Firefox and Chrome as browser in which to run the tests. Make sure this is available or change the configuration in test\karma-jqlite.conf.js and test\karma-jquery.conf.js

Some test tasks :
- gulp karma : Will run _jqlite_ and _jquery_ tests in simple run mode,
- gulp karma:jqlite:unit : Will run _jqlite_ tests in simple run mode,
- gulp karma:jquery:unit : Will run _jquery_ tests in simple run mode,
- gulp karma:jqlite:watch : Will run _jqlite_ tests and watch for changes,
- gulp karma:jquery:watch : Will run _jquery_ tests and watch for changes,

gulp serve` runs and watches all