On Mon, Mar 20, 2017 at 12:47 PM, Andrea Del Bene <an.delb...@gmail.com>
wrote:
> I see your point Korbinian, but JQuery still wildly used and removing it
> would mean not just a lot of effort, but also to indefinitely postpone the
> release of version 8.
>
I also think it is too early to retire jQuery.
But anyone can replace wicket-ajax-jquery.js with
getJavaScriptLibrarySettings().setWicketAjaxReference(...) !
>
> On Mon, Mar 20, 2017 at 11:33 AM, Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>
> > Hi,
> >
> > while I'm not one of the commiters I still like to respond to this. I'm
> > fine with changing from 1.x to 3.x as IE 10 and lower really has no
> > relevance anymore IMHO.
> > However, the real question that came into my mind:
> >
> > Why not just use plain js / vanilla js?
> >
> > When it was decided to go to jQuery doing pure js at that time was a
> > nightmare - every browser had its quirks (where every is mainly that MS
> > pile of crap called IE), reacted differently etc. - but now in 2017 I
> dont
> > really see so much more difference here. The same basic JS code to find a
> > dom in every browser is just now
> >
> > var matches = document.querySelectorAll('div.foo');
> >
> > while in jQuery its
> >
> > var matches = $.('div.foo');
> >
> > - no real difference here.
> >
> > Ajax? -
> >
> > $.ajax('/user/1')
> > .done(function (data) {
> > var user = data;
> > });
> >
> > vs
> >
> > fetch('/user/1')
> > .then(function (response) {
> > return response.json();
> > })
> > .then(function (data) {
> > var user = data;
> > });
> >
> >
> > ok a small bit more and no IE support - but we just ditch that with
> jquery
> > 3.x anyway....
> > (if IE is needed: ugly XMLHttpRequest)
> >
> > Just my 2c,
> >
> > Best,
> >
> > KB
> >
> >
> >
> >
> > ----- Ursprüngliche Mail -----
> > > Von: "Martin Grigorov" <mgrigo...@apache.org>
> > > An: dev@wicket.apache.org
> > > Gesendet: Montag, 20. März 2017 09:52:17
> > > Betreff: Use jQuery 3.x by default in 8.x
> >
> > > Hi,
> > >
> > > It is 14 months since Microsoft droppped the support for IE 10 and less
> > [0].
> > > Do you agree that it is OK to use jQuery 3.x in Wicket 8.x by default ?
> > >
> > > Applications will still be able to set custom version (like 1.x) if
> they
> > > need so.
> > > Also our JS tests will keep testing against jQuery 1.x, 2.x and 3.x
> [1].
> > >
> > > 0. https://www.microsoft.com/en-us/WindowsForBusiness/End-of-
> IE-support
> > > 1.
> > > https://github.com/apache/wicket/blob/1421ea2dc9207143cdadb735f3c794
> > 21674d924d/testing/wicket-js-tests/Gruntfile.js#L111-L118
> > >
> > > Martin Grigorov
> > > Wicket Training and Consulting
> > > https://twitter.com/mtgrigorov
> >
>
