EnyoJS A Scalable Code Base

EnyoJS is DRY, and can give you the ability to write reusable components and UI widgets for web pages.

Transcript

1. a scalable codebase
2. WHO AM I • Webaholic - I’ve been helping destroy build the web since ‘98 • LG:Electronics Enyo Framework Developer • Supported 100s of websites, variations of a single codebase (django backend), millions of hits a day for Cox Media Group. • Former Silicon Prairie Resident, now residing in Silicon Valley (US Bank, Nestlé Foods, Alliant Tek Systems, Davisco Foods, EV3, Synovis Life Systems, ATM Network) • I have really tall hair
3. ENYO’S HISTORY • Mojo for Handhelds needed a better way to work on multiple screens.
4. BRIEF ENYO TIMELINE • 9 February 2011 version 1.0 with HP • January, 2012 1.0 (Open Source) HP open sources Enyo under the Apache 2.0 license • July 18, 2012 2.0 Enyo 2 production version • February 5, 2014 2.4.0-pre.1 - Focus for the cross- platform Enyo community (more than 2.3).
5. ENYO’S HISTORY • HP Touchpad • Enyo 1 • designed to be platform agnostic but tied to webOS implementation • Enyo 2 • Open Source • IE8-10, Webkit, Firefox • Desktop, Mobile, Television
11. WHAT EXACTLY IS ENYO? • JavaScript Framework for Application Developers • Big Hairy Audacious Goal : Native Quality Applications, Made with Web Technologies. • Contains many moving parts • Core Library • DOM Interaction • OOP support • Helpers: AJAX, Utility methods • Data Handling: Models, Collections, Routing • Globalization • UI Libraries for Mobile, Desktop and 10ft (Television) • Most of Enyo’s components, are written in Enyo.
12. DEMO TIME
13. http://enyojs.com/sampler/2.4.0/ Enyo Sampler
14. “The best code, is no code at all.”
15. DEVELOPERS LOVE DECISIONS… • Brevity of the Code Written • Feature Complete • Performance and Speed • Time Invested into Coding • Flexibility and Adaptability • Robust Execution (Multiple Targets / Devices)
16. CODE: HARDER TO READ, THAN WRITE • Code reuse is hard • Preferences of developers • Documentation and APIs • Just plain ugly code
17. DEVELOPERS LOVE TO WRITE CODE • Code quantity increases naturally over time • Developers love to solve problems • Code we write today, we don’t love tomorrow, refactor, refactor, refactor
18. IS LOC A GOOD METRIC? • We can write more with less today • Different languages have grossly different LOC outcomes for the same applications.
19. WHAT HAPPENS WITH LOTS OF LOC? • Code Rots, APIs change and morph over time • Requires more maintenance hours • Requires longer exposure and more Debugging knowledge of the platform
20. • Encapsulation • Component logic and Component presentation should be able to live alone. • Reusability • Components should be “infinitely reusable” • Portability • Logic and Presentation should be able to travel easily to a new destination ENYO PRINCIPLES ENYO is D.R.Y.
21. DEMO TIME
22. RESOURCES • http://enyojs.com/ • http://enyojs.com/sampler/2.4.0/ • http://enyojs.com/gallery/ • https://github.com/enyojs • http://forums.enyojs.com/ • #enyojs on freenode • @enyojs on twitter
23. SUMMARY • Think small, program small • Write reusable components to build complexity • Enyo can help you do these things, and is cross browser / platform!
24. THANKS! @dmikeyanderson on twitter
 https://github.com/dmikey