Response title
This is preview!
Move this topic
Migration Issue?
in Using jQuery
•
2 years ago
For me, one of the most important feature of a framework is retro-compatibility and the migration process.
In this case i had to migrate from version 1.2.6 to 1.6.x, but I found a lot of difficult with plugins compatibility.
How can we avoid this in future? What do you think?
Tips are welcome.
Thanks
1
Replies(5)
Re: Migration Issue?
1 years ago
Any time you upgrade your base jQuery code you should also update all of your plugins.
Leave a comment on jay.blanchard's reply
Re: Migration Issue?
1 years ago
Yeah I know, but not all the plugins I use are compatible with newer versions of jQuery.
We can not pretend that all plugins update the code to new versions, but one thing you could do is to ensure backward compatibility of new versions.
This guarantee has contributed to the success of Java and could do so for jQuery which I consider still a very good library.
Would be interesting to hear the developer's opinions..
Leave a comment on fede309's reply
Re: Migration Issue?
1 years ago
the differences between versions of jquery as far as syntax changes ever so slightly.
For example, between 1.2.6 and 1.6.1, the primary differences from a syntax/backwards compatibility point of view is the attribute selector now matches the css 3 specifications, meaning the "@" symbol is invalid, and the functionality of .attr() has changed. All other differences are backwards compatible, such as allowing namespaced events, the added .live .die .delegate and .undelegate methods, allowing a data object on .bind, etc.
The only time the syntax changes is when it really does need to change to help the library progress.
the plugins that run into the most trouble are plugins like jQuery Validate that overwrite core methods. That isn't something the jQuery core can prevent or fix when the method that is being overwritten by the plugin gets re-built with upgraded functionality, or when things that the method relies on within the core library get changed.
If you rather keep using stale code that runs slower than the newer version just so that your older plugins will keep working, power to you. It worked then, it'l work now. The only problems you'll run into is when a new browser is released, such as IE9.
-- Kevin
-- Kevin
Leave a comment on Kevin B's reply
Re: Migration Issue?
1 years ago
the [attribute=@value] syntax changed when sizzle was introduced in 1.3 (http://docs.jquery.com/Release:jQuery_1.3), and the .attr() change happened in 1.6 for reasons explained here http://blog.jquery.com/2011/05/12/jquery-1-6-1-released/ and http://blog.jquery.com/2011/05/03/jquery-16-released/
-- Kevin
the ajax method was overhauled in 1.5 which broke the jquery validate plugin, however it was updated later to be compatible with 1.5+
-- Kevin
Leave a comment on Kevin B's reply
Re: Migration Issue?
1 years ago
Thank you so much, I'll try to update the plugins.
Perhaps it would be useful to have a sort of "migration checklist"of these changes in the official documentation.
Regards.
Perhaps it would be useful to have a sort of "migration checklist"of these changes in the official documentation.
Regards.
Leave a comment on fede309's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic
Reply to fede309's question
Statistics
- 5 Replies
- 905 Views
- 0 Followers
