It’s time again for the another installment of YUI: Open Hours!
This week, we’ll be joined by Caridy Patiño, author of the outstanding YUI Bubbling Library for YUI 2. We’ll have a look at some of the work he’s been doing migrating the Bubbling Library components to YUI 3, other modules and features he has in the Gallery already, and what new stuff he’s working on these days.
Thanks again to Eric Ferraiuolo for joining us last time and reviewing his work on the Component Manager utility and talking about some of the more brain melting points of application infrastructure development with YUI 3. A lot of great info about some of the features of YUI’s event system and infrastructure pieces came out of the discussion.
We’ll try to come back up to the surface a bit this week and address more specific problem spaces and UI patterns. But before we dive in with Caridy, we’re going to do a quick run through the YUI.add(...) method and how to create JavaScript classes in a YUI 3 world. Then it will be all Caridy, showing off a whole lot of flashy YUI 3 goodness. The conversation will no doubt touch on some points about migrating code from YUI 2 to 3 and some best practices when creating classes and modules.
The time will be the same as before, 10am – 12pm PDT and the connection details are also the same. Here they are for review:
And as always, you can keep up to date with the upcoming schedule and topics by following @yuilibrary on Twitter or subscribing to the YUI Event Calendar.
Hope to see you there! And don’t be shy about recommending guests or topics or offering suggestions for the OH format in general!
May 13, 2010 at 4:59 pm
When can i attend the Open Hours in Beijing China?
i just google the time difference,
May 13, 2010 at 8:08 pm
10am PDT Fri the 14th is 1am Saturday the 15th in Beijing. If you’re up for it, email me and I can get you a different local number (or just join by Skype).
May 14, 2010 at 2:51 pm
Some of the great takeaways from this week’s Open Hours:
1. Using
YUI_config = { filter: 'raw' /* etc other config */ };
YUI().use('node', function (Y) { ... });
uses the YUI_config as if it were passed as
YUI({ /* config */ }).use(...)2. Return Y.Attribute.INVALID_VALUE from an attribute’s setter to behave like a validator
3. You don’t have to publish simple custom events. You can subscribe regardless and when this.fire(‘theEvent’), it will be published automatically and the subscribers notified.
4. You can use Y.Base.create( name, BaseClass, [], prototype, statics ) to create a class that extends BaseClass.
And lots more. Be sure to join us next week for more great tips and best practices.
May 14, 2010 at 2:56 pm
And here are some code snippet references that came out of the conversation as well. Thanks to Pat Cavit for the Plugin example:
1. Evolution of a class from plain old JavaScript to a YUI 3 Gallery module
2. Example Plugin class template (includes other informative tips)
May 20, 2010 at 9:04 pm
Some of the great takeaways from this week’s Open Hours:
1. Using
YUI_config = { filter: 'raw' /* etc other config */ };
YUI().use('node', function (Y) { ... });
uses the YUI_config as if it were passed as
YUI({ /* config */ }).use(...)2. Return Y.Attribute.INVALID_VALUE from an attribute’s setter to behave like a validator
3. You don’t have to publish simple custom events. You can subscribe regardless and when this.fire(‘theEvent’), it will be published automatically and the subscribers notified.
4. You can use Y.Base.create( name, BaseClass, [], prototype, statics ) to create a class that extends BaseClass.
And lots more. Be sure to join us next week for more great tips and best practices.