While trying to use YUI 3.0, I was attracted to try out the YUI Node feature with the following code
$ele = Y.get('foo');
I was working out some race condition problems, and was hoping the waiting feature (where YUI will wait for the element to be in a ready state) would solve some problems for me.
What I had forgot was that Y.get is not the standard dollar function ( $('foo'), $('#foo'), etc ). This poses some real problems for me. I didn't really used the Dom.get methods, and probably for the same reasons, as I use both YUI and prototype together mostly.
But now I want to integrate the really nice features of YUI 3 into my code, and try and break away from my prototype "crutch". However, since I do use other 3rd party libraries for various things, most of them rely on straight up Dom elements being passed to them.
I hate to say it, but I have found something in YUI that just does not sit well with me.
The code still seemed to work with
Y.get('foo');
$ele = $('foo');
But I can't say for sure, and this seems pretty hacky?
Friday, July 24, 2009
Sunday, July 19, 2009
YUI 3.0.0 beta 1
YUI 3.0.0 beta 1 is now available for download from YUILibrary.com.
From the Yahoo! User Interface Blog:
"This release takes YUI 3 out of its preview phase and brings its APIs to a near-final state. For those intending to implement YUI 3, the 3.0.0 beta 1 release is a good place to begin the transition. If you’ve been working with the latest preview release, George Puckett has provided a comprehensive 3.0.0 beta 1 changelog to guide you. We look forward to hearing your feedback as you begin working with 3.0.0 beta 1, and we’ll work hard to address that feedback as we prepare for a GA release in the coming months."
Some very interesting things made this release
"StyleSheet: StyleSheet makes it easy to create and modify CSS rules on the fly, allowing you to dynamically style page elements with fewer repaints."
Add stylesheets dynamically!
"ImageLoader: ImageLoader allows you to defer the loading of images that aren’t in the viewport when the page paints, throttling bandwidth usage and improving performance"
Images won't load until they enter the viewport, for longer pages, or hidden elements this is pretty huge. The bandwidth savings could be worth it.
From the Yahoo! User Interface Blog:
"This release takes YUI 3 out of its preview phase and brings its APIs to a near-final state. For those intending to implement YUI 3, the 3.0.0 beta 1 release is a good place to begin the transition. If you’ve been working with the latest preview release, George Puckett has provided a comprehensive 3.0.0 beta 1 changelog to guide you. We look forward to hearing your feedback as you begin working with 3.0.0 beta 1, and we’ll work hard to address that feedback as we prepare for a GA release in the coming months."
Some very interesting things made this release
"StyleSheet: StyleSheet makes it easy to create and modify CSS rules on the fly, allowing you to dynamically style page elements with fewer repaints."
Add stylesheets dynamically!
"ImageLoader: ImageLoader allows you to defer the loading of images that aren’t in the viewport when the page paints, throttling bandwidth usage and improving performance"
Images won't load until they enter the viewport, for longer pages, or hidden elements this is pretty huge. The bandwidth savings could be worth it.
Thursday, July 9, 2009
Sunday, February 22, 2009
YUI 3 Preview Release 2 - IO
Today I will go over the new IO Utility in the YUI 3 Preview Release 2
What does this mean really? This means we have a single, consistent, interface to various data sources we may point our UI at. This data may be from our site, or another data provider on a different site. When the data resides on our site IO will use XHR (XMLHttpRequest ) to request the data, standard "AJax". When we are making our request cross-domain, the IO utility will use a flash swf to make the call, along with a crossdomain.xml (to let the flash know which sites it has access to). The crossdomain.xml is fairly important on a https: site as IE will complain to no end that you are trying to access non secure data, or mixing secure with non-secure. The crossdomain.xml resides in your document root.
So, let's see what the YUI 3 team has given us. The basic example provided at the IO Utility page sets up the use of io-base, defines a completed function, and subscribes to the event. The key here seems to be subscribing to the event :
When the Y.io(uri) event "complete" finishes, we want to run "complete" function with "this" as the context of execution, and pass also an array
This may be quite different and confusing to just about every other Framework out there. But so much better! There are a few posts on nabble where people are asking why the IO isn't "seperate" for each request, and the answer lies above. IO is a presistant connection, and it has a context that it runs in. If you are specifying IO in the global context, then all your requests are going to be in the global context, which is specified by "this".
In other words, Event handlers run in thier own context, so you could have multiple listeners on the io:complete event, but only some would run depending on context: Therefore, you could register a GlobalEvents object and set that context, just as in the examples and this would run for every IO request. If however, you have objects with different scopes, the global would fire as well as the callbacks in different scopes that are set to listen for io:complete.
The new IO utility also offers a "queue" which you can start, stop, promote, purge, and set the size. This is a big step in ajax frameworks as most like prototype do not come with these capabilities built in. With a queue you can send transactions and gracefully monitor and manage them with the io events and queue commands.
One way I can see this being very useful is if you had created a queue on page onload to load various items not immediatly visible to the user. But say the user then clicks on one of the items, we can immediatly stop the queue, and promote that request to the top of the queue, and when that completes, continue with the loading of the rest of the items! This is, to say the lease, very useful.
"IO is an HTTP utility that enables HTTP requests while maintaining a persistent client UI, for the purpose of data retrieval and content update. IO uses the XMLHttpRequest object for making "same-domain" requests. IO can make "cross-domain" requests, when instructed to do so, using an alternate HTTP transport."
What does this mean really? This means we have a single, consistent, interface to various data sources we may point our UI at. This data may be from our site, or another data provider on a different site. When the data resides on our site IO will use XHR (XMLHttpRequest ) to request the data, standard "AJax". When we are making our request cross-domain, the IO utility will use a flash swf to make the call, along with a crossdomain.xml (to let the flash know which sites it has access to). The crossdomain.xml is fairly important on a https: site as IE will complain to no end that you are trying to access non secure data, or mixing secure with non-secure. The crossdomain.xml resides in your document root.
So, let's see what the YUI 3 team has given us. The basic example provided at the IO Utility page sets up the use of io-base, defines a completed function, and subscribes to the event. The key here seems to be subscribing to the event :
// Subscribe to event "io:complete", and pass an array
// as an argument to the event handler "complete". Since
// "complete" is global.
// At this point in the transaction lifecycle, success or
// failure is not yet know.
Y.on('io:complete', complete, this, ['lorem', 'ipsum']);
When the Y.io(uri) event "complete" finishes, we want to run "complete" function with "this" as the context of execution, and pass also an array
['lorem', 'ipsum'] This may be quite different and confusing to just about every other Framework out there. But so much better! There are a few posts on nabble where people are asking why the IO isn't "seperate" for each request, and the answer lies above. IO is a presistant connection, and it has a context that it runs in. If you are specifying IO in the global context, then all your requests are going to be in the global context, which is specified by "this".
In other words, Event handlers run in thier own context, so you could have multiple listeners on the io:complete event, but only some would run depending on context: Therefore, you could register a GlobalEvents object and set that context, just as in the examples and this would run for every IO request. If however, you have objects with different scopes, the global would fire as well as the callbacks in different scopes that are set to listen for io:complete.
The new IO utility also offers a "queue" which you can start, stop, promote, purge, and set the size. This is a big step in ajax frameworks as most like prototype do not come with these capabilities built in. With a queue you can send transactions and gracefully monitor and manage them with the io events and queue commands.
One way I can see this being very useful is if you had created a queue on page onload to load various items not immediatly visible to the user. But say the user then clicks on one of the items, we can immediatly stop the queue, and promote that request to the top of the queue, and when that completes, continue with the loading of the rest of the items! This is, to say the lease, very useful.
Thursday, February 19, 2009
YUI 3 Preview Release 2 - Get Utility
Yahoo's User Interface Get Utility is one of my favorites. I use this constantly to load secondary scripts on the page, or when some event requires additional scripts. For example, while putting together a RIA with dialogs, you may not need the "container" library to load when the page loads, you may want to delay this till the user actually performs and action the requires the container to show.
This is much unchanged from YUI 2.6, and if your upgrading from 2.6 you would find this an easy "fix" to port to YUI 3. Most likely you will also have your own alias variable and namespace you can integrate this into.
In the above code we are using $Y.Get.script to get a single script and load it. Usually with these files I will use the (function(){ ... })(); convention. This makes it a little more clear what the code will do. If I have created namespaces, I will give each file it's own namespace and use it throughout the file.
This does a couple things. If used on page load, the scripts will be retrieved in a non-blocking manner. In other words, your images and CSS will not be in contention with the loading of these scripts. You will also be able to delay the loading of some scripts until they are actually needed.
Some practical applications you could use this for possibly is loading the validation logic on form submit, loading dialogs, calendars, and any of the heavier widgets that are not visible on first load.
Up Next : IO
// Code in main page
(function(){
var $Y = YUI();
ele.on('click', function(){
$getScripts = $Y.Get.script('/js/myDialog.js', {
onSuccess: function(){
// I ran myDialog.js .. assume here that it render()s the dialog
dialog.show();
// Do other things
}});
}
})();
This is much unchanged from YUI 2.6, and if your upgrading from 2.6 you would find this an easy "fix" to port to YUI 3. Most likely you will also have your own alias variable and namespace you can integrate this into.
In the above code we are using $Y.Get.script to get a single script and load it. Usually with these files I will use the (function(){ ... })(); convention. This makes it a little more clear what the code will do. If I have created namespaces, I will give each file it's own namespace and use it throughout the file.
This does a couple things. If used on page load, the scripts will be retrieved in a non-blocking manner. In other words, your images and CSS will not be in contention with the loading of these scripts. You will also be able to delay the loading of some scripts until they are actually needed.
Some practical applications you could use this for possibly is loading the validation logic on form submit, loading dialogs, calendars, and any of the heavier widgets that are not visible on first load.
Up Next : IO
YUI Shed Presents - YUI 3.x Preview Release 2
YUI 3.x has been brewing for some time now under the radar. I personally have kept peeking in to see if they had any of the widgets from YUI 2 working in this latest releases. As of YUI 3.x Preview Release 2 We have the first widgets, Overlay, Slider, and Console, along with MenuNav Nodes. This is a pretty big step forward, and gives me incentive to give each new component a test run, and provide a bit of practical use code. Over the next few days I will dive into each of the new components and give some use case code.
"Stay Tuned!"
"Stay Tuned!"
Wednesday, February 11, 2009
Nicole Sullivan on YUI Theater
This was a very good installment of YUI theater, that all web developers should take a look at. Her talk goes into image sprites, things already recommended by YSlow!, and some very interesting points to consider when designing a website. Sometimes, a few bad requirements will make things difficult to maintain, as well as make for bad markup and or bad javascript.
If you have never visited YUI Theater, your in for a treat. I highly recommend *ALL* of the videos there. Crockford is "the man".
If you have never visited YUI Theater, your in for a treat. I highly recommend *ALL* of the videos there. Crockford is "the man".
Subscribe to:
Posts (Atom)