Flight is well suited to sites with lots of user interaction and server-based static content, but doesn't hold up well for data-driven sites. It explicitly prevents direct component interaction to force developers to use the event-driven design patterns it was built on. This makes it rather difficult to implement the synchronizable models of Backbone.js, or the data binding of Angular.js. Every component has to manage its own state and can't inspect the state of child components, since all cross-component communication occurs via events. If rendering a static page for search crawlers isn't a concern, as with rich web apps like Gmail, or your application needs robust data synchronization, as with Google Docs, Flight may not be the best choice.
As a final note, Flight is not a framework like AngularJS or Backbone.js. It is a component library that specifically solves the problem of on-page progressive enhancement. It should be used as a part of a larger ecosystem of libraries that, together, solve the specific problems of your app. In this book, we introduce supporting libraries where needed to develop a fully functional app, and aim to highlight Flight's role in the application.
This book introduces each piece of Twitter Flight as necessary to implement a particular aspect of our example application. It aims to provide a complete guide to the various features Flight offers, with enough example code to demonstrate purpose or function when an explanation simply won't do. As I mentioned earlier, this book is aimed at those who learn by getting their hands dirty--so clone the sample application repository, load up the app to get a feel for what we'll be building, and let's get started.
There has been error in communication with Booktype server. Not sure right now where is the problem.
You should refresh this page.