With our 2.1 release, we announced Tier-1 support for Chrome on Android, and for iOS 6. Today, we’re releasing Enyo 2.1.1, which adds support for IE 10 and Kindle Fire HD.
IE 10
Beginning with Enyo 2.1.1, you can develop Enyo apps that run in IE 10 on Windows 8, Windows RT and Windows Phone 8.
As the first version of IE with touch support, IE 10 introduced a new Pointer Event API to unify the processing of mouse and touch events. While this API may eventually become a widely adopted standard, for now it’s only in IE.
Fortunately, Enyo has its own way of unifying mouse and touch events across all of the platforms we support, so we’ve just extended that mechanism to work with IE 10’s pointer events under the hood. This means that your existing Enyo apps will “just work” in IE 10, once you update to Enyo 2.1.1. On dual-input systems, your users will be able to seamlessly transition between touch and mouse input.
Additional Windows support is coming soon. We are closely following the progress of PhoneGap for Windows Phone 8, and you can expect your Enyo apps to work with it once it’s released. We are also working on support for deploying Enyo apps as Windows Store apps on Win8. Stay tuned!
Kindle Fire HD
The version of the Silk browser that shipped on the Kindle Fire HD introduced a few quirks for Enyo apps. We’ve ironed those out, enabling the Fire HD to join its older sibling in our Tier-1 support table.
What’s Next?
Enyo 2.2 is right around the corner — we’ve been working on it in parallel with 2.1.1. As we mentioned here recently, the headline feature for 2.2 is an optional MVC library. In the next week or so, we’ll be inviting developers to kick the tires on a preview release, so keep your eye on the forums and the enyo-dev mailing list for details.
From November 7th through 9th, Enyo sponsored the QCon International Software Development Conference in San Francisco. The conference featured tracks about everything from “Taming HTML5 & Javascript” to “Cross Platform Mobile.” The highlight was a presentation for Enyo newcomers by Dave Freeman and Peter Helm, which was well-attended and followed by a vigorous Q & A session. At the Enyo Booth, visitors were invited to try Enyo on the brand new iPad mini and in IE 10 on the Microsoft Surface. IE 10 support is in the Enyo nightly builds and will be coming soon to an official release. We look forward to seeing you next on November 30th at MoDevEast in Virginia!
It has been an exciting couple of months on the Enyo team as we have ramped up 4 new team members and worked hard to add some of our most requested features to the framework. Today we are releasing Enyo 2.1, which includes new features, new widgets, new browser support, and the death of over 60 bugs.
- LESS-based theming support: In order to provide easy customization of the Onyx UI library, we have added first-class support for using LESS stylesheets with Enyo. Check out our new UI Theming Guide for details on how easy it is to customize Onyx in your app.
- Globalization/Localization library: One awesome piece of software developed for the HP Touchpad was its globalization library, written fully in JavaScript. Today we’re releasing that g11n code as an Enyo 2-compatible library that you can use to localize your app’s strings, dates, times, phone numbers, and more! Head to the Localization Guide to find out more.
- New Browser Support: Beginning with Enyo 2.1, we’re promoting Chrome for Android and iOS6 to Tier 1 platforms. As always, you can view a full list of the platforms we support on the Enyo site. Additional platform support will be coming soon – IE10 is already looking good in desktop/mouse mode, and we’re targeting support for Win8 touch events, the Win8 HTML5 runtime, and Kindle Fire HD in an upcoming release.
- New Widgets: You’ll find a handful of cool new widgets in the 2.1 release. The Layout library gets an ImageView widget (with zooming and panning support, including pinch-to-zoom on multi-touch platforms) and an ImageCarousel for flipping through multiple ImageViews. The Onyx UI library gets a new RangeSlider, and localizable DatePicker and TimePicker widgets, too. Visit the Enyo Sampler to give the new widgets a spin!
- Sampler Improvements: The Sampler now includes a handy Gesture sample (pun intended), as well as support for opening any sample in jsFiddle.
Check out the Enyo 2.1 Release Notes for details on all changes in this release.
In addition, we’ve done significant work over the past couple months on adding data binding support to Enyo, as well as an optional MVC library to help you structure your Enyo app using the model-view-controller design pattern. While these features aren’t in the 2.1 release, we’re almost ready to have you try them out and give us your feedback. Keep an eye on the Enyo blog for more information, coming soon.
Last, we love hearing from our developers, and want to make sure we’re working on the things you value most. One way you can help is by voting in our JIRA tracker on the bugs or features you want to see addressed most. Happy voting!
Last week Enyo sponsored the HTML5 Developer Conference (@HTML5DevConf) in San Francisco, CA at the beautiful Palace Hotel. The two-day conference focused on connecting with and learning from both developers and experts. The presentations featured a number of varying and expanding approaches, tools, best practices, and advice. The Enyo team also had a booth staffed to answer questions, to demo apps written with Enyo on several different platforms, and to recruit for the best talent to join our team. Dave Freeman presented “A Deeper Look using Enyo” session on Monday Afternoon. On Tuesday, Gray Norton gave a five minute thought leadership interview, while Art Dahm ran a workshop to get hands-on with Enyo and to demonstrate how to modify your code on the fly using jsFiddle.
The Enyo After Dark After Party, hosted by Enyo, was a huge success. The sold-out event was held on Monday night at one of SF’s favorite art galleries, 111 Minna. Between the food, the Enyo Cocktail (pictured below), and the conversation, everyone had a great time. We gave out 8GB Enyo flash drive bottle openers (while they lasted!) and people made a game of creatively tweeting pictures of their new flash drives.
The entire Enyo team would like to thank everyone who attended the HTML5 Developer Conference. Be sure to check out the Events page at enyojs.com for upcoming events.



While I was in San Francisco for the HTML5 Developer Conference, I was clued into this fantastic effort done by Lionel Laské (president and co-founder of OLPC France) for the One Laptop per Child (OLPC) project. If you’re not familiar with OLPC, it is an effort to provide low-cost laptop computers to children all over the world to enhance their educational opportunities and connect them to the broader global digital world we take for granted. A noble goal, I’m sure most would agree.
The OLPC laptop is named XO and its user interface is Sugar. Sugar presents Activities for children to participate in instead of applications to run (check that link for a better description). A good number of Sugar Activities are developed using Python, but other languages can be used. This is where Enyo comes in. Aiming to attract JavaScript developers, Lionel has worked out a method whereby Enyo developers can easily create a Sugar Activity to run on the XO laptop. His two-part article describing his method (and the mini-framework he wrote to enable this) can be found here and here.
According to Lionel, Enyo was chosen over the Flask framework (Python) because the paradigm for developing with Flask is very complex and:
Enyo is very simple, elegant, component-oriented and, portable. “Portable” means that an application developed with Enyo could work easily on lot of different devices (smartphones, tablets, …). So a developer could write an application not only for Sugar but at the same time for other systems. It’s very important for developer which could else view Sugar as a “limited market”.
Lionel’s solution does use a bit of Python to kick off an initial Web browser to load the Enyo application. He provides a template to get you running quickly. You can get more information about using the template in the second part of his post. In addition to the Activity template, Lionel has also written a small framework that allows bi-directional communication directly between an Enyo application and the Sugar interface without the need for an embedded web server in the Activity. Great stuff!
We are excited that Lionel chose Enyo for its ease of use after attempting to do the same with at least one other framework. We also would like to applaud him for his work, in general, for the OLPC project! We encourage developers to create educational Sugar Activities for use on the XO. Your efforts may help ignite sparks that will fire the imaginations of the next generation of global citizens and beyond!
- Dave Freeman, Enyo Developer Relations Team

Openbravo, a leading provider of open-source ERP software, has chosen to use Enyo for both its web point-of-sale solution (Openbravo Web POS) and its mobile solution (Openbravo Mobile).
“Enyo is the right framework for Openbravo Mobile, as it provides the building blocks for developing modular, extensible, thin, and fast mobile applications.”
Check out the video that Rob Goris recently posted to the Openbravo blog, showcasing the power of Openbravo Mobile — and highlighting a very handsome Enyo-based UI, if we do say so ourselves.
Rob’s post was followed by one from Iván Perdomo, which discusses why Openbravo chose Enyo, delves into the Openbravo Mobile architecture and explains how they’ve paired Enyo with Backbone.js.
Last week Enyo co-sponsored the Breaking Development conference (@bdconf) in Dallas, Texas, which focuses on new, emerging techniques for web development and design for mobile devices. We had a booth where we answered questions and demoed apps written with Enyo running on several devices. On Monday evening we hosted an “Anti-social Social” event and closed out the conference on Wednesday afternoon with an Enyo Bootcamp. Of course we also had plenty of Enyo T-shirts, stickers and USB drives to give away.
The Anti-social Social, hosted by Enyo, took place on Monday night and was a huge success. Between the food and drinks, the games of pool and the conversation, everyone had a great time. We gave out 8GB Enyo flash drive bottle openers (while they lasted!) and people made a game of creatively tweeting pictures of their new flash drives. On Wednesday afternoon Ben Combee ran an Enyo bootcamp with his trusty sidekick, Dave Freeman. Ben went through the basics of Enyo and then created a demo app to pull Twitter feeds live on stage.
The entire Enyo team would like to thank everyone who attended the Breaking Development conference. It was a pleasure to meet and talk with you about Enyo and how it relates to the present and future of web and mobile development. Be sure to check out the Events page at enyojs.com for upcoming events.

Dave Freeman multitasks at the Enyo table

The Anti-social Social, hosted by Enyo

Ben Combee giving an overview of Enyo at the Enyo Bootcamp

One of the Enyo USB flash drives at the Anti-social Social event
Today we’re releasing Enyo 2.0.1, our first release since we exited beta last month.
Enyo 2.0.1 is a maintenance release, driven by feedback and bug reports from the Enyo community. We’ve resolved a number of issues related to Panels, Drawers, and Pickers, but you’ll find fixes and minor enhancements across the board — check the release notes for a full list.
With 2.0.1 out the door, we’re hard at work now on localization, theming, and data-binding options for Enyo apps, and we’ll have more to share with you soon!
Have a feature or idea we should be looking into? Let us know on the forums, or submit a feature request on the tracker. We’d love to hear from you.
Also, don’t miss the chance to meet the Enyo team at upcoming events we’ll be attending! Full details available on the Enyo Events page.
We just launched http://nightly.enyojs.com, where you can find nightly snapshots of Enyo core and official libraries, as well as the API viewer, Bootplate, and Sampler code. Use this to test your app against the bleeding edge or just see what we’re up to, without needing to pull from GitHub. We plan to keep about 2 weeks of archived snapshots available there as well. Head to the forums to let us know if you have other suggestions for making Enyo development easier!