Flight is a lightweight, component-based, event-driven JavaScript framework that maps behavior to DOM nodes. It was created at Twitter, and is used by the twitter.com and TweetDeck web applications.
Flight is only ~5K minified and gzipped. It's built upon jQuery, and has first-class support for Asynchronous Module Definition (AMD) and Bower.
Flight components are highly portable and easily testable. This is because a Flight component (and its API) is entirely decoupled from other components. Flight components communicate only by triggering and subscribing to events.
Flight also includes a simple and safe mixin infrastructure, allowing components to be easily extended with minimal boilerplate.
Flight has supporting projects that provide everything you need to setup, write, and test your application.
-
Flight generator Recommended. One-step to setup everything you need to work with Flight.
-
Flight package generator Recommended. One-step to setup everything you need to write and test a standalone Flight component.
-
Jasmine Flight Extensions for the Jasmine test framework.
-
Mocha Flight Extensions for the Mocha test framework.
You can browse all the Flight components available at this time. They can also be found by searching the Bower registry:
bower search flight
The easiest way to write a standalone Flight component is to use the Flight package generator:
yo flight-package foo
If you prefer not to use the Flight generators, it's highly recommended that you install Flight as an AMD package (including all the correct dependencies). This is best done with Bower, a package manager for the web.
npm install -g bower
bower install --save flight
You will have to reference Flight's installed dependencies – ES5-shim and jQuery – and use an AMD module loader like Require.js or Loadrunner.
<script src="bower_components/es5-shim/es5-shim.js"></script>
<script src="bower_components/es5-shim/es5-sham.js"></script>
<script src="bower_components/jquery/dist/jquery.js"></script>
<script data-main="main.js" src="bower_components/requirejs/require.js"></script>
...Alternatively, you can manually install the standalone
version of Flight, also
available on cdnjs. It exposes all of its modules as
properties of a global variable, flight:
...
<script src="flight.js"></script>
<script>
var MyComponent = flight.component(function() {
//...
});
</script>N.B. You will also need to manually install the correct versions of Flight's dependencies: ES5 Shim and jQuery.
Chrome, Firefox, Safari, Opera, IE 7+.
Here's a brief introduction to Flight's key concepts and syntax. Read the API documentation for a comprehensive overview.
A simple example of how to write and use a Flight component.
define(function (require) {
var defineComponent = require('flight/lib/component');
// define the component
return defineComponent(inbox);
function inbox() {
// define custom functions here
this.doSomething = function() {
//...
}
this.doSomethingElse = function() {
//...
}
// now initialize the component
this.after('initialize', function() {
this.on('click', this.doSomething);
this.on('mouseover', this.doSomethingElse);
});
}
});/* attach an inbox component to a node with id 'inbox' */
define(function (require) {
var Inbox = require('inbox');
Inbox.attachTo('#inbox', {
'nextPageSelector': '#nextPage',
'previousPageSelector': '#previousPage',
});
});Components (API)
- A Component is nothing more than a constructor with properties mixed into its prototype.
- Every Component comes with a set of basic functionality such as event handling and component registration. (see Base API)
- Additionally, each Component definition mixes in a set of custom properties which describe its behavior.
- When a component is attached to a DOM node, a new instance of that component is created. Each component
instance references the DOM node via its
nodeproperty. - Component instances cannot be referenced directly; they communicate with other components via events.
Once attached, component instances have direct access to their node object via the node property. (There's
also a jQuery version of the node available via the $node property.)
Events are how Flight components interact. The Component prototype supplies methods for triggering events as well as for subscribing to and unsubscribing from events. These Component event methods are actually just convenient wrappers around regular event methods on DOM nodes.
Mixins (API)
- In Flight, a mixin is a function which assigns properties to a target object (represented by the
thiskeyword). - A typical mixin defines a set of functionality that will be useful to more than one component.
- One mixin can be applied to any number of Component definitions.
- One Component definition can have any number of mixins applied to it.
- Each Component defines a core mixin within its own module.
- A mixin can itself have mixins applied to it.
Advice (API)
In Flight, advice is a mixin ('lib/advice.js') that defines before, after and around methods.
These can be used to modify existing functions by adding custom code. All Components have advice mixed in to
their prototype so that mixins can augment existing functions without requiring knowledge
of the original implementation. Moreover, since Component's are seeded with an empty initialize method,
Component definitions will typically use after to define custom initialize behavior.
Debugging (API)
Flight ships with a debug module which can help you trace the sequence of event triggering and binding. By default
console logging is turned off, but you can you can log trigger, on and off events by means of the following console
commands.
Thanks for assistance and contributions: @sayrer, @shinypb, @kloots, @marcelduran, @tbrd, @necolas, @fat, @mkuklis, @jrburke, @garann, @WebReflection, @coldhead, @paulirish, @nimbupani, @mootcycle.
Special thanks to the rest of the Twitter web team for their abundant contributions and feedback.
Copyright 2013 Twitter, Inc and other contributors.
Licensed under the MIT License