to 2. toukok. 2019 klo 6.16 Andrew Kondratev ([email protected]) kirjoitti:
> I meant refactoring of wicket core. There's actually not a lot of JS code > apart from the wicket-ajax-jquery.js, however the wicket-ajax-jquery.js > itself is quite long and could be better if it's split into separate, more > readible, code parts, such as TC classes which will be transpiled into > single or multiple JS files during a build file. > > Getting rid from jQuery dependency in wicket-core from my point of view is > also a good option, it's mostly used for selectors (which now work in all > supported browsers), for jQuery.extend and for ajax, which I think all can > be done without jQuery when we don't need to support IE9 and other legacy > browsers. > > Not sure about React, added just as an example. Maybe could be used to pair > with Components, which I think could work without any changes to the core. > Other changes sounded ok, my question was only about React. Why add a new unnecessary dependency when dropping jquery. ** Martin > чт, 2 мая 2019 г. в 14:18, Martin Terra <[email protected] > >: > > > to 2. toukok. 2019 klo 3.04 [email protected] ([email protected]) kirjoitti: > > > > > Hi Colleagues! > > > > > > Are there any plans about refactoring / modernisation of wicket's > > > front-end code? > > > > > > What comes to my mind: > > > Start using TypeScript for a new code, so we can have type safety on > the > > > front end side as well. TypeScript is also released under apache > license, > > > so I think there should be no licensing issue with this. Potentially, > as > > a > > > crazy idea Kotlin could also work, but I think TypeScript suits better > > and > > > requires less effort and learning; > > > Potentially get rid of jQuery, it's not that useful in 2019 (wicket has > > > recently dropped legacy IE support); > > > > Potentially introduce some modern lightweight front-end framework such as > > > ReactJS; > > > > > > > Could ReactJS remain pluggable as per each project (as it is now) or what > > do you see it doing as a built in component? > > > > > > > Sorry if it was already discussed, I searched on > issues.apache.org/jira > > > and lists.apache.org/[email protected] and didn't find > > > anything relevant. Just wanted to discuss if something like this is > > > possible for distant future release. Potentially I can devote a few > > hours a > > > week to this. > > > > > > Have a nice day, > > > Andrew > > > > > >
