Time to upgrade jQuery?

[Eduardo Rivas]

Hello everyone! I've started upgrading Mezzanine to the latest version of Bootstrap (v3.3.1) and this would require at least jQuery 1.9.1 [source]. I've encountered this problem before when using third party libraries that don't play along with Mezzanine's three year old version of jQuery (1.7.1, released November 2011). I would like to ask everybody (and Steve specifically) if you are open to upgrading the version of jQuery to at least 1.9.1. Cheers.

[J. Paskaruk]

Hi, I'm a newb who literally wrote his first jquery last week - I coded a leet document ready thing to move a div from one spot to another. So you could say my jquery needs are pretty simple at this point.

Strictly for my benefit, and perhaps in order to bolster your case for a distributed upgrade, could you expand a bit on what the newer jquery would offer over the older one? My understanding is that jquery is kind of a "standard toolbox" for js operations, and the basic Mezzanine interface is fairly simple, so I guess I'm wondering whether this is a case where an upgrade has limited benefit, and a risk of destabilizing the overall infrastructure, maybe? But again, see first paragraph. I'm just trying to stir up conversation. :>

[Stephen McDonald]

Thanks Ed - sounds fine so long as we judiciously test all the third party libraries bundled, I know there have been rough edges around those in the past when upgrading jquery itself. The gallery image lightbox thing, the drag/drop interface within the admin, and there are probably others that don't come to mind.

Thanks again.

On Thu, Dec 25, 2014 at 10:37 AM, Eduardo Rivas <jeriva...@gmail.com> wrote:

Hello everyone! I've started upgrading Mezzanine to the latest version of Bootstrap (v3.3.1) and this would require at least jQuery 1.9.1 [source]. I've encountered this problem before when using third party libraries that don't play along with Mezzanine's three year old version of jQuery (1.7.1, released November 2011). I would like to ask everybody (and Steve specifically) if you are open to upgrading the version of jQuery to at least 1.9.1. Cheers.

--
You received this message because you are subscribed to the Google Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Stephen McDonald
http://jupo.org

[Eduardo Rivas]

Sorry for the delay guys, I left for a short vacation.

J, off the top of my head, the benefits of using newer versions of jQuery are:

• Support for the latest versions of Bootstrap (as mentioned in my first email). On the CSS side, Bootstrap gives Mezzanine a theme, grid, form styles, etc; but on the Javascript / jQuery side it provides a complete UI kit, letting you build interactive interfaces with elements such as tabs, accordions, dropdowns, affixes, modal dialogs, etc. More info here: http://getbootstrap.com/javascript/.
• We can benefit from security fixes (I don't know of any problems with 1.7.1, but they might exist). Also, general bug fixes and enhancements.
  
• If we migrate to even more recent versions, such as the 2.x family, we would get increased speed and reduced size, because these family drops support for legacy browsers, among other things. http://blog.jquery.com/2013/04/18/jquery-2-0-released/ (see "How 2.0 changed").
• On the same link you can see how you could create custom versions of jQuery for the 2.x family to cater to the specific needs of your site due to the new modular approach of building it, further reducing the size of the final file.
  

Steve, I also came up with an alternate approach: Stay with 1.7.1 for the Admin, but ship more recent versions for the public site. Perhaps we can create a couple of new settings to substitute JQUERY_FILENAME: for the admin we could have JQUERY_ADMIN_FILENAME and for the general site JQUERY_PUBLIC_FILENAME. This way frontend developers can experiment with the cutting edge without worries of breaking the Admin interface, and we still get the convenience of managing jQuery versions through settings. What do you think?

--
You received this message because you are subscribed to a topic in the Google Groups "Mezzanine Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mezzanine-users/jlcdcReUwdM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mezzanine-use...@googlegroups.com.

[Stephen McDonald]

I think it'd be better for the project to just ship with a single version if possible.

There shouldn't be anything stopping the developer from using whatever version they like for the public site - if there is, then that's what should be addressed.