Some questions about YUI 3

First of all, congrats on the release! I ve been looking over it and I m impressed with the new framework. I like it quite a bit, especially the dependency

Message 1 of 4
, Sep 30, 2009

0 Attachment

First of all, congrats on the release! I've been looking over it and I'm impressed with the new framework. I like it quite a bit, especially the dependency loading, new Node, DOM selectors, and pluggable infrastructure.

I am trying to make the decision about what JS framework to use for the GrailsUI plugin (http://grails.org/plugins/grails-ui) in its next incarnation. It currently uses YUI 2. If anyone would like to answer a few questions, please feel free.

1. Are there plans to create YUI 3 widgets for all the corresponding YUI 2 widgets? DataTable, AutoComplete, TabView, etc.?2. Can the DataSource be easily refreshed? I've always wanted to be able to call .refresh() on my widgets when the server-side data may have changed, but I've usually found out (esp. with DataTable) that there is no easy way to do this without recreating the widget.3. Have some of the consistency issues been fixed? For example some widgets you added event handlers like this: widget.someEvent.subscribe(callback), and others you did this: widget.subscribe('someEvent', callback).

Maybe some of my questions are ignorant. Because of the pluggable infrastructure, you may be planning on having DataTable, AutoComplete, etc. plugins that use the core YUI 3 codebase.

Thanks for all your hard work, and I am looking forward to using YUI 3!

Matthew -- 1. Most of the Widgets will be ported to 3.x eventually. However the Widget infrastructure needs to be flushed out and finished before we can

Message 2 of 4
, Sep 30, 2009

0 Attachment

Matthew --

1. Most of the Widgets will be ported to 3.x eventually. However the
Widget infrastructure needs to be flushed out and finished before we can
actively start porting widgets.

2. I think that's on the list because I would like to see it too ;)

3. Yes, the goal here was to make everything work and act the same. That
should lead to faster & lighter code.

Dav

On Wed, 30 Sep 2009, Matthew Taylor wrote:

> First of all, congrats on the release! I've been looking over it and I'm
> impressed with the new framework. I like it quite a bit, especially the
> dependency loading, new Node, DOM selectors, and pluggable infrastructure.
>
> I am trying to make the decision about what JS framework to use for the
> GrailsUI plugin (http://grails.org/plugins/grails-ui) in its next
> incarnation. It currently uses YUI 2. If anyone would like to answer a few
> questions, please feel free.
>
> 1. Are there plans to create YUI 3 widgets for all the corresponding YUI 2
> widgets? DataTable, AutoComplete, TabView, etc.?
> 2. Can the DataSource be easily refreshed? I've always wanted to be able to
> call .refresh() on my widgets when the server-side data may have changed,
> but I've usually found out (esp. with DataTable) that there is no easy way
> to do this without recreating the widget.
> 3. Have some of the consistency issues been fixed? For example some widgets
> you added event handlers like this: widget.someEvent.subscribe(callback),
> and others you did this: widget.subscribe('someEvent', callback).
>
> Maybe some of my questions are ignorant. Because of the pluggable
> infrastructure, you may be planning on having DataTable, AutoComplete, etc.
> plugins that use the core YUI 3 codebase.
>
> Thanks for all your hard work, and I am looking forward to using YUI 3!
>
> ---
> Matthew Taylor
> http://dangertree.net

+ Windows: n. - The most successful computer virus, ever. +
+ A computer without a Microsoft operating system is like a dog
without bricks tied to its head +
+ A Microsoft Certified Systems Engineer is to computing what a
McDonalds Certified Food Specialist is to fine cuisine +

jenny

Hi Matthew, 2. The feature you describe is currently tracked here and under consideration for the next DataTable release (in 2.x, which implies it gets ported

As for a DataSource-centric feature, please feel free to file an enhancement at yuilibrary.com if there's something different you'd like to see implemented. It always helps to describe the use case you are trying to support.

Thanks!
Jenny

--- In ydn-javascript@yahoogroups.com, Dav Glass <davglass@...> wrote:
>
>
> Matthew --
>
> 1. Most of the Widgets will be ported to 3.x eventually. However the
> Widget infrastructure needs to be flushed out and finished before we can
> actively start porting widgets.
>
> 2. I think that's on the list because I would like to see it too ;)
>
> 3. Yes, the goal here was to make everything work and act the same. That
> should lead to faster & lighter code.
>
> Dav
>
> On Wed, 30 Sep 2009, Matthew Taylor wrote:
>
> > First of all, congrats on the release! I've been looking over it and I'm
> > impressed with the new framework. I like it quite a bit, especially the
> > dependency loading, new Node, DOM selectors, and pluggable infrastructure.
> >
> > I am trying to make the decision about what JS framework to use for the
> > GrailsUI plugin (http://grails.org/plugins/grails-ui) in its next
> > incarnation. It currently uses YUI 2. If anyone would like to answer a few
> > questions, please feel free.
> >
> > 1. Are there plans to create YUI 3 widgets for all the corresponding YUI 2
> > widgets? DataTable, AutoComplete, TabView, etc.?
> > 2. Can the DataSource be easily refreshed? I've always wanted to be able to
> > call .refresh() on my widgets when the server-side data may have changed,
> > but I've usually found out (esp. with DataTable) that there is no easy way
> > to do this without recreating the widget.
> > 3. Have some of the consistency issues been fixed? For example some widgets
> > you added event handlers like this: widget.someEvent.subscribe(callback),
> > and others you did this: widget.subscribe('someEvent', callback).
> >
> > Maybe some of my questions are ignorant. Because of the pluggable
> > infrastructure, you may be planning on having DataTable, AutoComplete, etc.
> > plugins that use the core YUI 3 codebase.
> >
> > Thanks for all your hard work, and I am looking forward to using YUI 3!
> >
> > ---
> > Matthew Taylor
> > http://dangertree.net
>
> --
> Dav Glass
> davglass@...
> blog.davglass.com
>
>
> + Windows: n. - The most successful computer virus, ever. +
> + A computer without a Microsoft operating system is like a dog
> without bricks tied to its head +
> + A Microsoft Certified Systems Engineer is to computing what a
> McDonalds Certified Food Specialist is to fine cuisine +
>

As for a DataSource-centric feature, please feel free to file an enhancement at yuilibrary.com if there's something different you'd like to see implemented. It always helps to describe the use case you are trying to support.

Thanks!
Jenny

--- In ydn-javascript@yahoogroups.com, Dav Glass <davglass@...> wrote:
>
>
> Matthew --
>
> 1. Most of the Widgets will be ported to 3.x eventually. However the
> Widget infrastructure needs to be flushed out and finished before we can
> actively start porting widgets.
>
> 2. I think that's on the list because I would like to see it too ;)
>
> 3. Yes, the goal here was to make everything work and act the same. That
> should lead to faster & lighter code.
>
> Dav
>
> On Wed, 30 Sep 2009, Matthew Taylor wrote:
>
> > First of all, congrats on the release! I've been looking over it and I'm
> > impressed with the new framework. I like it quite a bit, especially the
> > dependency loading, new Node, DOM selectors, and pluggable infrastructure.
> >
> > I am trying to make the decision about what JS framework to use for the
> > GrailsUI plugin (http://grails.org/plugins/grails-ui) in its next
> > incarnation. It currently uses YUI 2. If anyone would like to answer a few
> > questions, please feel free.
> >
> > 1. Are there plans to create YUI 3 widgets for all the corresponding YUI 2
> > widgets? DataTable, AutoComplete, TabView, etc.?
> > 2. Can the DataSource be easily refreshed? I've always wanted to be able to
> > call .refresh() on my widgets when the server-side data may have changed,
> > but I've usually found out (esp. with DataTable) that there is no easy way
> > to do this without recreating the widget.
> > 3. Have some of the consistency issues been fixed? For example some widgets
> > you added event handlers like this: widget.someEvent.subscribe(callback),
> > and others you did this: widget.subscribe('someEvent', callback).
> >
> > Maybe some of my questions are ignorant. Because of the pluggable
> > infrastructure, you may be planning on having DataTable, AutoComplete, etc.
> > plugins that use the core YUI 3 codebase.
> >
> > Thanks for all your hard work, and I am looking forward to using YUI 3!
> >
> > ---
> > Matthew Taylor
> > http://dangertree.net
>
> --
> Dav Glass

> davglass@...

> blog.davglass.com>
>
> + Windows: n. - The most successful computer virus, ever. +
> + A computer without a Microsoft operating system is like a dog
> without bricks tied to its head +
> + A Microsoft Certified Systems Engineer is to computing what a
> McDonalds Certified Food Specialist is to fine cuisine +
>

Your message has been successfully submitted and would be delivered to recipients shortly.