I am in favor of keeping the file named jquery.js and just alerting theme and plugin developer when we update.
Sent from my iPhone On Apr 25, 2009, at 9:27 AM, "[email protected]" <[email protected]> wrote: > > In http://trac.habariproject.org/habari/changeset/3488 jquery got > updated and renamed. From what I understand this will break themes and > plugins currently using jquery.js since that file is now replaced with > jquery-1.3.2.min.js. > > From a quick search in -extras around 10 plugins and 15 themes use > jquery.js and probably a lot more themes and plugins not in -extras. > > Since jquery isn't always backward compatible it might be good to have > some version names. But imo this shouldn't break current themes and > plugins. That doesn't send a good signal to the community. > > I see a couple of different solutions for this, non of them perfect :) > > 1. When upgrading jquery still keep it named jquery.js and update > themes/plugins if needed. > 2. Keep the latest version of jquery as jquery.js but also include > jquery-1.3.2.min.js, jquery-1.2.2.min.js, ... and so on so that the > theme/plugin can use whatever the author wish. > 3. Only include jquery-1.3.2.min.js, jquery-1.4.2.min.js, ... and so > on demanding themes/plugins to be updated now but not in the future. > > There's more solutions but I'm to lazy to write them all down. But we > should decide something so that ppl writing plugins/themes knows what > to do. > > > > --~--~---------~--~----~------------~-------~--~----~ 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/habari-dev -~----------~----~----~----~------~----~------~--~---
