Originally Posted by
Initiostar
Acorn, your second point, I think, is more a concern. We have jQuery 3.6 thereabouts now. In orders of magnitude, how difficult would it be for Xara to come into this century?
Gary
Well Gary, I have been asking since 2014: https://www.talkgraphics.com/showthr...-use-of-jQuery.
One possible approach would be to wrap Xara's old code and use this:
Code:
<script>
console.log("Xara has loaded " + $().jquery);
var jQ1dot11dot1 = jQuery.noConflict(true);
console.log("We have aliased it to jQ1dot11dot1 (" + jQ1dot11dot1().jquery + ")");
</script>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js"></script>
<script>
console.log("The latest jQuery is now: " +$().jquery);
</script>
Elsewhere:
<script>
(function ($) {
jQ1dot11dot1(document).ready(function () {
console.log("Stale Xara jQuery files content ... will still run.");
});
}(jQ1dot11dot1));
</script>
Console:
Xara has loaded 1.11.1
We have aliased it to jQ1dot11dot1 (1.11.1)
The latest jQuery is now: 3.6.0
Stale Xara jQuery files content ... will still run.
Xara only have to do this if you have used the old Xara sliders that use legacy code/jQuery v1.11.1. Luckily if you avoid them and just use improved versions then almost everything I have tested will run, even ani.css for animations.
If you avoid these then all you need add to the Website Code (head) is: <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js"></script>
I am sure the use of jQuery Migrate would also work.
Acorn
Bookmarks