I had hoped to be able to share by now the video from YUI's 2nd Birthday where we laid out, in broad strokes, where the project is headed. It looks like it will be a while longer before that video is ready, so here is a high-level summary:
2.x development: YUI 2.x will go through at least one more top-level release (2.6.0; not yet scheduled), at which time we hope to add the Carousel Control that was dropped from 2.5.0. We are also working on addressing bugs in the 2.x family -- 2.5.1 will be out this week with a batch of bug fixes, and there will certainly be several more bug fixes releases as we continue to support this release through 2009.
3.x development: We have been working hard planning the next revision to the YUI platform. Our central concerns here are making YUI 3.x faster, lighter, easier to use, easier to extend, and more powerful. There will be some API changes associated with this transition, but one of our focuses also is ensuring that the transition from 2.x to 3.x is as painless as possible. This project is now receiving the lion's share of our focus. We said at the party that we hope to have a 3.0.0 preview for you to check out before the and of Q2, a beta in Q3, and GA in latter third of 2008. We're far enough along to be very excited about the improvements the 3.x changes will bring. We'll be sharing much more detail about the project in the coming months as we prepare the preview release.
2-way open source: The other significant announcement at the birthday party was that YUI will open for external contributions this year. We'll lay out in more detail how that will happen in Q2, but you'll also probably see invitations to participate here on YDN-JavaScript as we start putting the necessary pieces in place for that transition.
When 2.6.0 is well-defined, you'll see a preview here, and of course much communication about the 3.0 release and the contributor model as those projects progress.
Regards,
Eric
______________________________________________
Eric Miraglia
Yahoo! User Interface Library
On Mar 10, 2008, at 10:29 AM, gregg_fowler wrote:
Hi,
Any updates on getting a new roadmap? It would be great to know where the product is going beyond what has been mentioned for 2.5.1.
Hi, Any updates on getting a new roadmap? It would be great to know where the product is going beyond what has been mentioned for 2.5.1. Thanks, Gregg...
Gregg, I had hoped to be able to share by now the video from YUI's 2nd Birthday where we laid out, in broad strokes, where the project is headed. It looks...
We've mentioned a couple of times here that we'd be shipping YUI 2.5.1 this week. Regrettably, this bug-fix release did not stabilize as quickly as we had...
Eric, This is very decent of you and demonstrates the professionalism and humbleness of the YUI team. I know of one big company also with an Ajax framework...
Francis Amanfo
famanfo@...
Mar 13, 2008 9:09 am
Thanks for the update -- great to hear that the process is going to open up a bit, and that you have significant plans going forward. -- Gregg...
TRY STREETS & TRIPS, IT IS A WONDERFUL PROGRAM MY PARENTS TRAVEL ALL OVER THE WORLD AND THAT IS WHAT MY DAD KEEPS IN HIS COMPUTER THAT HE HAS ON A MOUNTED...
I was thinking about 3.x and 3rd party involvment and started wondering if we could have a YAHOO.widget abstract class (or whatever passes for such in...
Satyam, Indeed, we're doing just as you suggest here for v3 with respect to the Widget class and the unification of lifecycle and rendering idioms across the...
And please - change the YAHOO namespace... YUI would be much more relevant and shorter. YUI certainly suffers from too much diversity in the architecture - so...
Yes, I agree with that and no real coding standard either. ... rethinking the core. This is not always a bad thing. Since you mentioned ExtJS, take their form...
... mechanisms. A lot if is predicated on the use of the FormPanel and not all web applications (or web sites) necessarily want to display data in a panel...
Yes, yes and yes... that's why I switched to YUI myself too. ... better to create forms in HTML and add JS handling to them instead of creating literally ...