Tuesday, July 27th, 2010

YUI 3.2.0 preview release 1 – touch events support, transitions and browser-specific loading

Category: Browsers, CSS, JavaScript, Library, YUI

Over at the the YUI blog the team just announced the preview release of YUI 3.2.0. YUI3 now has some interesting new features that the team wants you to try and tell them if they work out for you. The changes to the already very powerful library are quite ambitious:

  • Touch event support for mobile interfaces including flick and move gestures
  • Browser capability loading – which means that every browser gets the least amount of code necessary to make it work
  • Transition support for the animation module – meaning only browsers that don’t support CSS3 transitions get the JavaScript animation fallback
  • An update to the CSS grids to allow for more flexible layouts
  • A ScrollView widget similar to the one in Apple iOS
  • The uploader has been transitioned over from YUI2 to YUI3

So check out what is on offer and give the YUI team feedback on what would be nice to have and what is broken. In their own words:

The goal of a preview release is to make it as easy as possible for all of us in the community to evaluate progress of the upcoming release and provide feedback. Please take some time to test 3.2.0pr1 and let us know what you find by filing tickets in the YUI 3 bug database marked as “Observed in version” 3.2.0pr1. We’ll do our best to address preview-release questions on the YUI 3 Forums, too.

There are three ways to get started with the preview release: YUI 3.2.0pr1 is available on the CDN via the 3.2.0pr1 version tag — so you can reference preview-release files like http://yui.yahooapis.com/combo?3.2.0pr1/build/yui/yui-min.js. If you switch to this seed file for the preview release, all subsequent use() statements will continue to load YUI 3.2.0pr1. Or You can download the full YUI 3.2.0pr1 from YUILibrary.com, including source code and examples for all components. Or you can simply explore the functioning examples roster.

Posted by Chris Heilmann at 1:34 pm

3.6 rating from 7 votes


Comments feed TrackBack URI

“Browser capability loading – which means that every browser gets the least amount of code necessary to make it work”
So, browser sniffing vs object detection? The rest of the framework looks great but this sounds like a step backward.

Comment by kissmyawesome — July 28, 2010

I believe ‘browser capability loading’ involves ‘feature detection’, not browser sniffing. Not sure how you conclude they fell back to browser sniffing.

For example, addEventListener is not present/native and attachEvent IS present/native, it loads the attachEvent pack. Not that hard ;)

Comment by BenGerrissen — July 28, 2010

@kissmyawesome – the point is that unlike a library that loads all the code and doeas a feature check to see what code to use, YUI has separately prepared bits of code that assume certain features are in place and then at runtime, the feature check is performed and the appropriate code is loaded. That kind of thing is especially important for mobile development, which seems to be a theme for this release.

Comment by genericallyloud — July 28, 2010

@Ben / @genericallyloud – you’re both right of course – I was speed-reading over the blog article and the various mentions of “IE-specific code” made me jump to conclusions. My bad.

Comment by kissmyawesome — July 29, 2010

Great Update?

Comment by KKFC — July 31, 2010

Can someone know where the specific place in the YUI code that uses the browsers specific loading?

Either I’m just not looking hard enough or I spent all my free time staring at the cool waterfall in the last entry…

Comment by dhtmlkitchen — August 8, 2010

Ah, damn gibberish again…

Comment by dhtmlkitchen — August 8, 2010

Leave a comment

You must be logged in to post a comment.