Richard, I completely support the dev team in your efforts. This was not an easy decision I'm sure! However, I think most users would completely agree that we'd rather have you guys continuing to do a fantastic job and working hard on moving the project forward than trying to support multiple versions of the API at the same time. In doing so, it would really slow down the project and drain valuable resources.
Lorin, Is there a reason as to why you can't just simply use the 1.6 release instead of the 1.7? The 1.6 will be compatible with the 1.2.6 version of JQuery. You could always do as Richard mentioned and use both the 1.6 and 1.7 and continue to have your backwards compatibility. --Ryan On Thu, Feb 12, 2009 at 1:20 PM, Richard D. Worth <[email protected]> wrote: > > On Thu, Feb 12, 2009 at 2:59 PM, Lorin Larson <[email protected]> wrote: > >> As I noted in another post, Wellman's navAccordion.html program (and >> likely >> several others of his that now have problems with the new release of >> jquery and >> the UI ) worked with the last stable releases of >> both jquery and the UI. Providing some means (addon, "plugin") to allow >> for >> backward compatibility is important. May well not need to be in the >> jquery core, >> but they should exist. >> > > As the blog post mentions, we've done a pretty thorough analysis of what it > would take to support two or maybe more APIs simultaneously (meaning > multiple UI APIs, and multiple jQuery versions). The only thing we feel like > we can commit to and deliver is > > - a 1.6 final that does not break the API in 1.6rc2 (quite similar to > 1.5.3), compatible with jQuery 1.2.6 > - a 1.7 final that is quite a close match to 1.6rc6 (but as a new point > release has API changes), compatible with jQuery 1.3+ > > We understand that there may be people in situations that don't fit cleanly > into one of those setups. We want to be able to help as many as possible to > find success, but we also can't do that at the detriment of our future > plans. As always, we're open to feedback, but the differences between these > two UI releases and the differences between jQuery 1.2.6 and 1.3 (which > effect UI maybe more so than typical plugins) are great enough that a > compatibility plugin does not currently look feasible. That's why we've laid > out our plan, which includes a complete Upgrade Guide for those making the > transition, either now or later. > > Finally, jQuery UI, like jQuery, allows for multiple versions to be loaded > on the page, without conflict. While maybe not an ideal setup, if it turned > out to be a necessity, one could have jQuery UI 1.6 final with jQuery 1.2.6 > for one plugin, and jQuery UI 1.7 final with jQuery 1.3+ for another. > > - Richard > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery UI" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-ui?hl=en -~----------~----~----~----~------~----~------~--~---
