Enyo and templates

[Ross Gardler <rg...@opendirective.com>]

Last night I committed a simple base widget template that uses the
Enyo [1] framework rather than JQuery Mobile.

Enyo is the framework built for WebOS. In HPs new strategy they have
open sourced it and are rebuilding it to remove its focus on WebOS
tablets. Instead it is being turned into a generic HTML5 application
framework.

It has a couple of significant advantages over JQM. The two that
really jump out at me are a) it is intended to run on any platform,
not just mobile b) it is a component based framework. For these
reasons it looks like it might be a better framework for many widgets.
However, Enyo 2.0 does not yet have any UI components so it is not
really usable. The UI package is due "in about a month" so I've
decided to experiment anyway. It works in the same way as the JQM
templates, in order to convert your existing eidgets you just need to
change the name of the template from "base" to "enyo/base" (no other
templates are implemented at this stage).

I do not recommend that anyone use it at this point, but if you want
to have a play then go ahead. I intend to get all the current
templates implemented as Enyo templates, without UI styling first -
help appreciated.

Ross

[1] http://enyojs.com

-- 
Ross Gardler (@rgardler)
Programme Leader (Open Development)
OpenDirective http://opendirective.com