(FWIW, I bet this is because Enyo was designed for WebOS, a touch-screen interface with no cursor, and is currently being adapted with high-priority to Android/iOS. It is certainly something that I bed they'd want to hear, however.)

This is the very first UI release, only a month after the core framework release, so there are certainly alot of minor areas like this that can be improved. And also core widgets still to be done - Lists, Panes, etc.

Development is now in the open so you can see it progress, and you can easily fork it, make these minor adjustments, and potentially contribute back.

Yeah, IE7 is not going to be supported. As you see IE8 works somewhat, and going forward IE9+ is planned for full support.

As I can see almost all of the buttons/check-boxes/etc are styled div elements, so it relies on JS definitely.

The sample shows mostly cross platform form widgets, but Enyo is larger than that. Its intended to be a javascript application framework oriented toward building apps for mobile devices and the web. Its a great compliment to things like PhoneGap/Cordova. See http://enyojs.com/

Enyo is essentially the application framework webOS 3 applications were written with, and its being re-written for cross platform support and has been made free and developed in the open on github.

If I understand correctly, you can develop locally-installable applications for iOS/Android/webOS/RIM using Enyo JS and these widgets, that will work on all of those platforms (local app, but not native) as well as working via a standard web browser. The aim is a write-once run-anywhere environment for mobile and web. There are already some proof-of-concept webOS apps that haved moved from the webOS app store into Android, iOS, RIM (Playbook), and even the Chrome app store. FlashCards for example started out as a Enyo-based webOS app:

https://chrome.google.com/webstore/detail/diejjofgldkjkhmfja...

Any webOS devs out there, please correct me if I'm wrong ;-)

'cuz jQuery is sooo 2006.

A more serious answer: jQuery normalizes JS quirks across browsers into a unified interface, plus it provides a lot of goodies.

What jQuery isn't good for is organizing code. That's why Backbone and the term MVC have become popular lately. Applications need to be organized into something better than a big sloppy helping of jQuery callbacks.

Enyo allows you to build modular, organized code in a somewhat familiar way. I'd say it's in-between a big mash of jQuery and a full-blown MVC framework. If you want to think of it in an MVC way, it's like combining views into controller code...and I don't know where "models" fit in. And unlike Backbone, it provides its own built-in DOM manipulation and, as of today, a UI framework too.

JQuery isn't designed for building applications, it's main purpose is making cross-browser interaction with the DOM easier. It has some other "utililty" type functions, like making cross-browser AJAX simpler and adding its own "each" looping construct, etc. etc. But the simple answer to your question is that this is not a replacement for jQuery.

I don't know much about Enyo, but it looks to be more of a framework for building applications, and provides things like layout management, controls, and an interesting "Component" model. I know that it was extracted from WebOS, so it may have some overlap with JQuery (i.e. by providing simpler methods of interacting with the DOM) but its goal is different.