Enyo: A JS Framework for Mobile Devices
summary
Enyo claims a mobile app framework that shifts HTML generation into JavaScript, uses WebKit plus V8 and a Node runtime for background services, and replaces Mojo/Aries bloat that added a few extra 100K of JavaScript. It provides a virtual DOM that emits one big HTML string, a virtual repeater for huge lists, flexbox layouts, precompiled framework assets for faster startup, and running demos on the TouchPad show the components and carousel working as intended.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:38HP webOS Architecture
- 3:01Enyo Begins with Ares
- 5:20Enyo Applications
- 6:16Anatomy of a Enyo Application
- 7:29depends.js
- 10:19Applications Are the Target
- 10:56Code Reuse Through Components
- 13:24Support Flexible Layouts
- 14:36Favor Code Generation and Layout Tools
- 15:33Example of Application Structure
- 16:44JS Will Get Faster Quicker Than WebKit
- 17:33Cache DOM in Local JavaScript Objects
- 18:33Support Device and Desktop
- 23:13The Enyo API
related talks
03minterviewed – Peter Helm
48mMobile Apps with JavaScript - There's More Than Web
26mnative.js: JavaScript in your native mobile apps
23mThe Next Wave of Web Frameworks is BYOJS
51mWrite once, run everywhere: ambitious cross-device web apps
32mWhat's Happening in the JavaScript Ecosystem?
37mEffective mobile applications prototyping with JavaScript
46mJavascript's comeback story on Mobile