On Mon, Sep 19, 2011 at 7:11 PM, Igor Vaynberg <[email protected]> wrote: > staged approach is fine, however its step 2 only that will cause > migration headaches, so this is just delaying the inevitable... Matej's work is re-work both of client and server side and I think it will take some time to implement and stabilize. I don't want Wicket.next to take long period as 1.5...
It depends what other new features will be planned for Wicket.next > > -igor > > > On Mon, Sep 19, 2011 at 8:29 AM, Martin Grigorov <[email protected]> wrote: >> Hi, >> >> In the recent ticket changes by Igor I mentioned few comments that >> Ajax will be re-written for Wicket.next (1.6, 3.0, 6.0 - whatever we >> call it). >> >> I want to share my experience with trying to re-vive Matej's work at [1], >> [2]. >> The changes there are a bit drastic (maybe because the task hasn't >> been finished and the API breaks not cleaned) and knowing how Ajax >> heavy are the applications I've worked on I think it will be quite a >> work to migrate the apps from 1.5 to Wicket.next. >> I also tried to introduce wicket-ajax.jar with the new impl and keep >> the old one for transition but that wasn't easy too. >> >> So I want to propose a two step approach: >> 1) introduce some JavaScript library for Wicket.next and improve >> wicket-xyz.js files by using it >> 2) improve/reimplement Wicket Ajax for Wicket.next+1 >> >> >> martin-g >> >> 1. >> http://svn.apache.org/viewvc/wicket/sandbox/knopp/experimental/wicket/src/main/java/org/apache/_wicket/ajax/ >> 2. https://github.com/martin-g/wicket/tree/ajax2 >> > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
