One reason to upgrade is for performance. See http://docs.jquery.com/Release:jQuery_1.3 and notice the CSS selector performance improvement. As with any upgrade, it may brak things.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have done some testing with IE6 / IE7 and Firefox 3 without any problems with phpgedview 4.1.7. I use jquery 1.3 since about a week also on a productive site because of the performance improvements making it a lot easier for my co-authors.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have reports from polish PGV users, which use Opera browser, that using jquery version 1.3.2 causing forever loading bugs. Especially when using random media block. They downgrade jquery to version 1.3.1. This version doesn't cause this problem.
However when I use Opera browser I don't see the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In relation to Opera not loading the page, I've come to the conclusion that the problem is the Prototype library, not the jQuery library. The latest released version of PGV (4.2.1) has Prototype v1.5.0. I upgraded to Prototype v1.6.0.3 and the loading problems went away. I'm currently using jQuery v1.3.2. However, I'll note there's another thread that indicated upgrading to Prototype v1.6 also requires upgrading script.aculo.us from v1.7 to v1.8, although I haven't done that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any plans to upgrade the jQuery version to the latest?
Do you know if there's any reason to do so, any benefits to the way PGV uses it?
jQuery is used in various places, and in particular by the jquery "autocomplete" and "queue" plugins.
I just had a quick look at the release notes for these plugins, but they don't tell me which version(s) of jquery they work with.
So, if someone wants to test these to make sure they are compatible with the latest jQuery, I'll get it updated for the next release.
Greg
One reason to upgrade is for performance. See http://docs.jquery.com/Release:jQuery_1.3 and notice the CSS selector performance improvement. As with any upgrade, it may brak things.
Another option is to remove jquery.js from PhpGedView package
and to load the framework from Google Code :
http://www.tvidesign.co.uk/blog/improve-your-jquery-25-excellent-tips.aspx#tip1
However we should not forget people who are using PhpGedView on a standalone computer or private network with no permanent internet connection.
Christophe
I have done some testing with IE6 / IE7 and Firefox 3 without any problems with phpgedview 4.1.7. I use jquery 1.3 since about a week also on a productive site because of the performance improvements making it a lot easier for my co-authors.
I have reports from polish PGV users, which use Opera browser, that using jquery version 1.3.2 causing forever loading bugs. Especially when using random media block. They downgrade jquery to version 1.3.1. This version doesn't cause this problem.
However when I use Opera browser I don't see the problem.
In relation to Opera not loading the page, I've come to the conclusion that the problem is the Prototype library, not the jQuery library. The latest released version of PGV (4.2.1) has Prototype v1.5.0. I upgraded to Prototype v1.6.0.3 and the loading problems went away. I'm currently using jQuery v1.3.2. However, I'll note there's another thread that indicated upgrading to Prototype v1.6 also requires upgrading script.aculo.us from v1.7 to v1.8, although I haven't done that.
FYI, PGV was updated to use the latest stable releases of the third-party javascript libraries a couple of months ago.
The current development version (and hence the upcoming release 4.2.2) uses:
scriptaculous 1.8.2
prototype 1.6.0.3
jquery 1.3.2