On 8/27/07, James McLaughlin <[EMAIL PROTECTED]> wrote:
> Yes there is. I haven't had much time to see what the impact of the
> change would be, but I set up YuiHeaderContributor to be able to
> select versions. If you have the time and inclination, you can setup
> the 2.3.0 library under org/wicketstuff/yui/inc, and include the
> library with something like this:
>
> YuiHeaderContributor.forModule("menu", null, false, "2.3.0")
>
> then let us know what works and what doesn't. Ultimately, the
> yuiloader in 2.3.0 will eliminate most of the work that
> YuiHeaderContributer does (resolving deps), so if you want to take a
> stab at porting it the headercontributor to yuiloader, that would be
> great too.Also note that we did something similar in wicket-datetime. Maybe, in some future, it would be great to have all the YUI components together. For now, we could look whether the projects can at least be used together without having them bite. A thread of two weeks ago discussed this. The conclusion was that we probably would like something like a separate YUI project with all the js dependencies in it, so that projects using them can access it in a consistent fashion. If someone is up to it, please dig up that discussion and create a feature request linking to that discussion (nabble). Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
