Enyo (http://enyojs.com) started as an web application framework, focusing on the problem of effectively building reusable UI components. However, many app developers view problems through a Model-View-Controller (MVC) point-of-view where the UI is seen as a templating problem. This talk looks at how the Enyo framework evolved in late 2012 to take on aspects of MVC, integrating support for Backbone models and data binding into our component & message passing architecture. In doing so, it reveals what these two worlds can learn from each other, and how they both play into future work on the “web platform”.
A new way of thinking
How do you keep application state?
Templates are not enough. Interactive controls are hard to put into templates.