Hi, I'm +1 to improve the fragment's markup identification [1] and Wicket's property expression language [2] before promoting it.
1 - http://wicket-dev.markmail.org/thread/unwdqpxulw7tcd5l 2 - http://wicket-dev.markmail.org/thread/3g4zsqykid3ia6xl Pedro Santos On Mon, Oct 31, 2016 at 11:41 AM, Martin Grigorov <mgrigo...@apache.org> wrote: > Hi, > > What other improvements do we need in 8.x/master before promoting it to > 8.0.0 final ? > > At https://cwiki.apache.org/confluence/display/WICKET/Ideas+for+Wicket+8.0 > we still have: > > - new DateTime APIs for wicket-datetime *WICKET-6105 > <https://issues.apache.org/jira/browse/WICKET-6105>* - I'll give this one > more try but the problem is that I don't believe this is the proper way and > this demotivates me. > If someone else wants to give it a try - please assign it to yourself! > > - Better SEO for stateful pages - the only way I see this is by using > ServiceWorker to add the pageId as a request header to all requests (normal > & Ajax) > > > Recently I wondered whether Redux.js could be in use for Wicket. > I don't have much experience with it, but both React and AngularJs > communities use it to manage the state for their components. > There are some Java impls, even a standard is coming: > https://github.com/jvm-redux/jvm-redux-api > > What else ? > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov >
